QEMU available at: http://autobuilder.yoctoproject.org/pub/releases/1.6_M1.rc1 poky c51730aaa91066cfb51ad6ec2920fb4f9d9ea94c Compiling sudokusavant fails on the current qemux86: root@qemux86:~/standalone-automated-MAR-4/sudoku-savant-1.3# ./configure 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... 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 g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking for library containing strerror... none required checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) none checking for gcc... gcc 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 dependency style of gcc... none checking how to run the C++ preprocessor... g++ -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... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for ld used by GCC... /usr/i586-poky-linux/bin/ld checking if the linker (/usr/i586-poky-linux/bin/ld) 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 pkg-config... /usr/bin/pkg-config 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: Package 'gdk-x11-2.0', required by 'gtk+-2.0', not 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. root@qemux86:~/standalone-automated-MAR-4/sudoku-savant-1.3#
Actually, this reproduces following this steps: 1. Download and install adt for qemux86: http://autobuilder.yoctoproject.org/pub/releases/1.6_M1.rc1/adt-installer-QA/adt_installer.tar.bz2 2. run qemu: ubu@ubu-v:/media/ubu/big-ubu/work/m1-rc1/adt-installer$ runqemu ./download_image/bzImage-qemux86.bin ../test-yocto/qemux86 kvm 3. copy to the image sudoku savand and run: ./configure; make
So a couple of basic checks, I downloaded and installed ADT, I examined the sysroot produced during the install process and it contains the gdk-x11-2.0.pc, so the file should exist in the booted image via NFS. But it did not and I saw the following style of error from NFS: NFS: directory usr/lib contains a readdir loop.Please contact your server vendor. The file: ..:� has duplicate cookie 1833309224 Can you verify if on the booted system you have the /usr/lib/pkgconfig/gdk-x11-2.0.pc file? I also booted the .ext3 image instead of using NFS and found that the image would configure and build correctly. My thought might be this is really an NFS bug, not an ADT issue, still a problem! Note, I did not run with KVM enabled. I want to verify QA has NFS errors before taking the next steps
(In reply to comment #2) > So a couple of basic checks, I downloaded and installed ADT, I examined the > sysroot produced during the install process and it contains the > gdk-x11-2.0.pc, so the file should exist in the booted image via NFS. But > it did not and I saw the following style of error from NFS: > > > NFS: directory usr/lib contains a readdir loop.Please contact your server > vendor. The file: ..:� has duplicate cookie 1833309224 > > Can you verify if on the booted system you have the > /usr/lib/pkgconfig/gdk-x11-2.0.pc file? > > I also booted the .ext3 image instead of using NFS and found that the image > would configure and build correctly. > > My thought might be this is really an NFS bug, not an ADT issue, still a > problem! > > Note, I did not run with KVM enabled. > > I want to verify QA has NFS errors before taking the next steps Hi Saul, I managed to reproduce it on my host (using NFS of course): root@qemux86-64:~/standalone-automated-MAR-4/sudoku-savant-1.3# ls /usr/lib/pkNFS: directory usr/lib contains a readdir loop.Please contact your server vendor. The file: xml2Conf.sh has duplicate cookie 1167227051 NFS: directory usr/lib contains a readdir loop.Please contact your server vendor. The file: xml2Conf.sh has duplicate cookie 1167227051 oNFS: directory usr/lib contains a readdir loop.Please contact your server vendor. The file: xml2Conf.sh has duplicate cookie 1167227051 NFS: directory usr/lib contains a readdir loop.Please contact your server vendor. The file: xml2Conf.sh has duplicate cookie 1167227051 ^C onfig/kdNFS: directory lib/pkgconfig contains a readdir loop.Please contact your server vendor. The file: xcb-screensaver.pc has duplicate cookie 4106177285 NFS: directory lib/pkgconfig contains a readdir loop.Please contact your server vendor. The file: xcb-screensaver.pc has duplicate cookie 4106177285 I also commented on 5637 as well.
I can confirm that the same type of issue happens on both x86 and x86-64 arches. Making it a duplicate with 5639 *** This bug has been marked as a duplicate of bug 5639 ***