emerge fails, ./configure works - why? [worked around]

[oliver]

I need gnome-libs for a legacy app at work so I have the old ebuild/files/patches saved off in a PORTDIR_OVERLAY location

When I emerge gnome-libs, I get the following error

Code: Select all

checking for dlfcn.h... (cached) yes
checking for locale.h... (cached) yes
checking for gmodule support... no
configure: error: Dynamic linking is not available on this platform. Some apps,
like panel, will not run properly.
 * ERROR: gnome-base/gnome-libs-1.4.2 failed:
 *   (no error message)
 *
 * Call stack:
 *     ebuild.sh, line  48:  Called src_compile
 *   environment, line 2920:  Called die
 * The specific snippet of code:
 *       ./configure --host=${CHOST} --prefix=/usr --libdir=/usr/$(get_libdir) --mandir=/usr/share/man --infodir=/usr/share/info --sysconfdir=/etc --localstatedir=/var/lib --enable-prefer-db1 ${myconf} || die;
 *
 * If you need support, post the output of 'emerge --info =gnome-base/gnome-libs-1.4.2',
 * the complete build log and the output of 'emerge -pqv =gnome-base/gnome-libs-1.4.2'.
 * This ebuild is from an overlay named 'oliver': '/usr/local/portage/'
 * The complete build log is located at '/var/tmp/portage/gnome-base/gnome-libs-1.4.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-base/gnome-libs-1.4.2/temp/environment'.
 * S: '/var/tmp/portage/gnome-base/gnome-libs-1.4.2/work/gnome-libs-1.4.2'

>>> Failed to emerge gnome-base/gnome-libs-1.4.2, Log file:


If I cd to /var/tmp/portage/gnome-base/gnome-libs-1.4.2/work/gnome-libs-1.4.2/ and do the following, the "./configure && make" works

Code: Select all

# . /etc/make.conf
# ./configure --host=${CHOST} --prefix=/usr --libdir=/usr/$(get_libdir) --mandir=/usr/share/man --infodir=/usr/share/info --sysconfdir=/etc --localstatedir=/var/lib --enable-prefer-db1 ${myconf}


I have all use flags disabled via /etc/portage/package.use ( -*) but I see this in the 'emerge' output:

Code: Select all

 * USE:  amd64 elibc_glibc kernel_linux multilib userland_GNU

Is this the source of the difference? If so, can I override the behaviour?

I know I can manually compile gnome-libs and put it in package.provided but I was wondering what the root cause is

This is on a freshly installed, updated Sabayon 3.5 AMD64 (Gnome)
Thanks

[oliver]

I'm putting this down to the code being so obsolete... I found an old Sabayon 4.2, booted it up, and my gnome-libs ebuild compiled perfectly. I quickpkg'd it up and dropped in on the new build and all is good.

Thanks for reading

[Thev00d00]

4.2 is new?! Blimey.... 5.3 is latest!

[oliver]

I meant that I booted up an old 4.2 CD, emerged gnome-libs there (and it's dependencies), ran quickpkg on it (still on 4.2), then emerged the created gnome-libs-1.4.2.tbz file on my new 5.3 installation. Worked like a charm.

While 4.2 was a fine release, 5.3 is where it's at