Forums

Hi Wes,

In order to run this applications in Vala you need to install the compiler package on your host machine

 sudo apt-get install valac

The error you're getting is happening because the SDK wasn't able to identify the package name for Ubuntu distributions. I just solved it and commited it to the repository. Please run the following commands while being on the devdir root directory (....../leopardboarddm365/sdk/trunk in most of the cases)

 cd bsp/oscheck

 svn up

 cd ../../

 make

 

 

Regards,

Pablo

Hi Pablo,

 

I follow your instruction above but I still obtain the error below. I read on the web that missing 'glib-2.0' and 'gobject-2.0' can be solved using the command this command (sudo apt-get install build-essential libglib2.0 libglib2.0-dev libgtk2.0 libgtk2.0-dev)

 

I have a question on the version of vala-0.7.9, base on the link (sourceforge.net/.../index.php) it says that the vala version should be vala-0.12.1.

 

Thanks for you help.

 

make[1]: Entering directory `/home/student/work/leo365/fs'

# Building Apps.defs

/bin/bash /home/student/work/leo365/bsp/scripts/build_apps_defs.sh host-apps apps /home/student/work/leo365/toolchain rrapps arch mach proprietary_src myapps > /home/student/work/leo365/fs/Apps.defs

# Checking for new host packages requirements

rm -f /home/student/work/leo365/fs/hostreqs

/bin/bash /home/student/work/leo365/bsp/oscheck/pkg -o

   Checking for host packages required by the SDK target applications...

   Checking dependencies for vala-0.7.9

   Building internal SDK version of vala-0.7.9...

make[2]: Entering directory `/home/student/work/leo365/fs/host-apps/vala-0.7.9'

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... no

checking for mawk... mawk

checking whether make sets $(MAKE)... yes

checking whether to enable maintainer-specific portions of Makefiles... no

checking for gcc... gcc

checking whether the C compiler works... yes

checking for C compiler default output file name... a.out

checking for suffix of executables...

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ISO C89... none needed

checking for style of include used by make... GNU

checking dependency style of gcc... gcc3

checking whether gcc and cc understand -c and -o together... yes

checking build system type... x86_64-unknown-linux-gnu

checking host system type... x86_64-unknown-linux-gnu

checking for a sed that does not truncate output... /bin/sed

checking for grep that handles long lines and -e... /bin/grep

checking for egrep... /bin/grep -E

checking for fgrep... /bin/grep -F

checking for ld used by gcc... /usr/bin/ld

checking if the linker (/usr/bin/ld) is GNU ld... yes

checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B

checking the name lister (/usr/bin/nm -B) interface... BSD nm

checking whether ln -s works... yes

checking the maximum length of command line arguments... 3458764513820540925

checking whether the shell understands some XSI constructs... yes

checking whether the shell understands "+="... yes

checking for /usr/bin/ld option to reload object files... -r

checking for objdump... objdump

checking how to recognize dependent libraries... pass_all

checking for ar... ar

checking for strip... strip

checking for ranlib... ranlib

checking command to parse /usr/bin/nm -B output from gcc object... ok

checking how to run the C preprocessor... gcc -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking for dlfcn.h... yes

checking for objdir... .libs

checking if gcc supports -fno-rtti -fno-exceptions... no

checking for gcc option to produce PIC... -fPIC -DPIC

checking if gcc PIC flag -fPIC -DPIC works... yes

checking if gcc static flag -static works... yes

checking if gcc supports -c -o file.o... yes

checking if gcc supports -c -o file.o... (cached) yes

checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes

checking whether -lc should be explicitly linked in... no

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

checking whether stripping libraries is possible... yes

checking if libtool supports shared libraries... yes

checking whether to build shared libraries... yes

checking whether to build static libraries... no

checking for flex... flex

checking lex output file root... lex.yy

checking lex library... -lfl

checking whether yytext is a pointer... yes

checking for bison... bison -y

checking for valac... /usr/bin/valac

checking for pkg-config... /usr/bin/pkg-config

checking pkg-config is at least version 0.9.0... yes

checking for GLIB... configure: error: Package requirements (glib-2.0 >= 2.12.0 gobject-2.0 >= 2.12.0) were not met:

No package 'glib-2.0' found

No package 'gobject-2.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you

installed software in a non-standard prefix.

Alternatively, you may set the environment variables GLIB_CFLAGS

and GLIB_LIBS to avoid the need to call pkg-config.

See the pkg-config man page for more details.

make[2]: *** [configured] Error 1

make[2]: Leaving directory `/home/student/work/leo365/fs/host-apps/vala-0.7.9'

  Failed to build vala-0.7.9... aborting

   Please build with VERBOSE=1 to see the error

make[1]: *** [host_packages] Error 255

make[1]: Leaving directory `/home/student/work/leo365/fs'

make: *** [fs_build] Error 2

Regards,

Irwin Liew