3330 2012-10-24 11:50:06 +0000 cannot compile sudoku project using a user build toolchain for denzil 2013-03-04 13:22:00 +0000 1 1 6 Yocto Project Subprojects ADT adt 1.2.2 x86 Multiple RESOLVED NOTABUG Medium normal 1.4 1 alexandru.c.georgescu jessica.zhang poky.adt.watcher poky.watcher --- --- --- oldest_to_newest 26860 0 alexandru.c.georgescu 2012-10-24 11:50:06 +0000 TESTED ON Fedora 17 64bit and Ubuntu 12.04 64bit. STEPS TO REPRODUCE: 1. Clone a poky repo 2. Checkout the 1.2.2 denzil: $ git checkout denzil $ git checkout 846b7c388738f382e83576e77b705aa547c1dd9b 3. Source the environment: $ source oe-init-build-env 4. Modify the conf/local.conf for qemuarm 5. Build the toolchain: $bitbake meta-ide-support 6. After build is finnished, open a new console and source the environment. In my case: $ source /home/alex/_1.2.2/git/poky/build/tmp/environment-setup-armv5te-poky-linux-gnueabi 7. Extract the sudoku project archive and configure it. Make sure that it is extracted to a new location, so no other modifications have been made to it. EXPECTED RESULT 7. Configure and make are successful ACTUAL RESULT lex@alex-pc:~/_1.2.2/compile/sudoku-savant-1.3$ ./configure ${CONFIGURE_FLAGS} configure: WARNING: unrecognized options: --with-libtool-sysroot checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-poky-linux-gnueabi-strip... arm-poky-linux-gnueabi-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether arm-poky-linux-gnueabi-g++ -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm accepts -g... yes checking dependency style of arm-poky-linux-gnueabi-g++ -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm... gcc3 checking for library containing strerror... none required checking whether we are using the GNU C++ compiler... (cached) yes checking whether arm-poky-linux-gnueabi-g++ -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm accepts -g... (cached) yes checking dependency style of arm-poky-linux-gnueabi-g++ -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm... (cached) gcc3 checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm checking whether we are using the GNU C compiler... yes checking whether arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm accepts -g... yes checking for arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm option to accept ISO C89... none needed checking dependency style of arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm... gcc3 checking how to run the C++ preprocessor... arm-poky-linux-gnueabi-g++ -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether NLS is requested... yes checking for msgfmt... /home/alex/_1.2.2/git/poky/build/tmp/sysroots/x86_64-linux/usr/bin/msgfmt checking for gmsgfmt... /home/alex/_1.2.2/git/poky/build/tmp/sysroots/x86_64-linux/usr/bin/msgfmt checking for xgettext... /home/alex/_1.2.2/git/poky/build/tmp/sysroots/x86_64-linux/usr/bin/xgettext checking for msgmerge... /home/alex/_1.2.2/git/poky/build/tmp/sysroots/x86_64-linux/usr/bin/msgmerge checking build system type... x86_64-pc-linux-gnu checking host system type... arm-poky-linux-gnueabi checking for ld used by GCC... arm-poky-linux-gnueabi-ld --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm checking if the linker (arm-poky-linux-gnueabi-ld --sysroot=/home/alex/_1.2.2/git/poky/build/tmp/sysroots/qemuarm) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no checking for CFLocaleCopyCurrent... no checking for GNU gettext in libc... yes checking whether to use NLS... yes checking where the gettext function comes from... libc checking for arm-poky-linux-gnueabi-pkg-config... no checking for pkg-config... /home/alex/_1.2.2/git/poky/build/tmp/sysroots/x86_64-linux/usr/bin/pkg-config configure: WARNING: using cross tools not prefixed with host triplet checking pkg-config is at least version 0.9.0... yes checking for PACKAGE... configure: error: Package requirements (gtk+-2.0 >= 2.4.0) were not met: No package 'gtk+-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 PACKAGE_CFLAGS and PACKAGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. alex@alex-pc:~/_1.2.2/compile/sudoku-savant-1.3$ OTHER COMMENTS: Configuring using the ADT or pre-build toolchain works fine. Only with user build toolchain this error happens. 26869 1 jessica.zhang 2012-10-24 21:57:35 +0000 Hi Alex, if you only do bitbake meta-ide-support, sysroot is going to be minimium which indeed missing gtk+, for supporting gtk+, if you bitbake core-image-sato-sdk, the library's going to be populated in sysroot. Otherwise, use a sysroot contains the library and pass sysroot as a parameter during configure 30401 2 alexandru.c.georgescu 2013-03-04 13:22:00 +0000 Hi Jessica, Can you specify how this can happen (use a sysroot contains the library and pass sysroot as a parameter during configure), without altering the environment file? Regards,