Created attachment 317982 [details] build.log at the emerge --oneshot net-misc/wget stage of building a prefix on a fedora16 x86-64 host, i get: >>> Failed to emerge dev-libs/glib-2.32.3, Log file: looks like it is missing libffi library checking for LIBFFI... no configure: error: Package requirements (libffi >= 3.0.0) were not met: No package 'libffi' 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 LIBFFI_CFLAGS and LIBFFI_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details.
Created attachment 317984 [details] emerge_info
note: dev-libs/libffi-3.0.11::gentoo is iinstalled
From the doc: $ emerge --oneshot "<net-misc/wget-1.13.4-r1" (until we fix #393277) are you sure you copy 'n' pasted that exactly as is?
and you are on Fedora 14, not 16.
thanks and sorry. was using a script based on the docs that was working fine on another machine. that looks like my issue.
i hit the same error again when i do: env FEATURES="-collision-protect" emerge --oneshot sys-apps/portage -v [ebuild N ] dev-libs/glib-2.32.3::gentoo USE="-debug -doc (-fam) (-selinux) -static-libs -systemtap -test -utils -xattr" 0 kB [ebuild N ] dev-util/pkgconfig-0.26::gentoo USE="-hardened" 0 kB [ebuild N ] virtual/pkgconfig-0::gentoo 0 kB [ebuild N ] x11-misc/shared-mime-info-1.0::gentoo 0 kB [ebuild N ] dev-lang/python-2.7.3-r2::gentoo USE="gdbm ipv6 ncurses readline ssl threads (wide-unicode) xml (-aqua) (-berkdb) -build -doc -examples -sqlite -tk -wininst" 0 kB [ebuild N ] sys-apps/portage-2.2.01.20757::gentoo USE="(ipc) -build -doc -epydoc -prefix-chaining (-selinux) -xattr" LINGUAS="-pl" 0 kB [ebuild N ] app-admin/python-updater-0.10-r2::gentoo 0 kB
maybe just a pkg-config issue. this gets me past it. export PKG_CONFIG_PATH=$EPREFIX/usr/lib/pkgconfig/
Another workaround that I found was installing dev-libs/glib-2.32.2. This installs sucessfully and pulls in virtual/pkgconfig and dev-util/pkgconifg. After that I was able to sucessfully upgrade to dev-libs/glib-2.32.3.
could be pkg-config problem indeed, since we're bootstrapping still, probably working on the deps of pkg-config (glib, yes, which needs pkg-config in turn again) I think this would be solved if we could rid ourselves of pkg-config, bug #417741
once we can mask pkg-config, this bootstrap problem can go away.
Is this bug used to track the addition of the code in bootstrap-prefix.sh? # ugly hack to make sure we can compile glib, which is depended upon # by shared-mime-info in case an ancient pkg-config is available on # the system that glib doesn't grok (e.g. Solaris 10) export LIBFFI_CFLAGS="-I$(echo ${ROOT}/usr/lib*/libffi-*/include)" export LIBFFI_LIBS="-lffi"
comment 10 is bogus, so I don't understand what you're trying to say here
(In reply to comment #12) > comment 10 is bogus, so I don't understand what you're trying to say here glib failed to build and I was going to file a new bug, but then I noticed the code in comment #11 was new. So, is the code in comment #11 a result of this bug? (If the answer is yes, I'll attach a new build.log here. If the answer is no, I'll open a new bug report to triage)
w/e I encountered the problem during Solaris bootstrap
(In reply to comment #14) > w/e > > I encountered the problem during Solaris bootstrap IFF version <=2.32.2 gets restored to the prefix tree (I suggest 2.30.3) then I suggest the following diff: Index: bootstrap-prefix.sh =================================================================== --- bootstrap-prefix.sh (revision 61160) +++ bootstrap-prefix.sh (working copy) @@ -1033,11 +1033,12 @@ app-misc/pax-utils # need this early for OSX (before libiconv - gen_usr_ldscript) sys-apps/coreutils sys-apps/findutils - "<app-arch/tar-1.26-r1" + "<app-arch/tar-1.26-r1" # bug 406131 sys-apps/grep sys-apps/gawk sys-devel/make sys-libs/zlib + "<dev-libs/glib-2.32.3" # bug 426302 ) emerge_pkgs "" "${pkgs[@]}" || return 1
That shouldn't be ok, since PKG_CONFIG_PATH is now banned by the bootstrap script, and the libffi overrides should force it not to look at pkg-config
Created attachment 321222 [details] glib-2.32.4 build.log (In reply to comment #16) > That shouldn't be ok, since PKG_CONFIG_PATH is now banned by the bootstrap > script, and the libffi overrides should force it not to look at pkg-config See attached log, then. gclosure.c:29:17: error: ffi.h: No such file or directory
and if you do this? echo "#!/bin/sh" > ${EPREFIX}/tmp/usr/bin/pkg-config echo "exit 1" >> ${EPREFIX}/tmp/usr/bin/pkg-config stupid package.
and chmod 755 it
(In reply to comment #19) > and chmod 755 it yes, got me past the issue on RHEL 5.7
ok, thanks for testing, we now use this brute-force approach from stage1
