It started with a kalarm problem, proceeded to Gentoo dependency heck, and
has progressed to the point that I fear the destruction of my current Gentoo system.
(I do have a recent tar backup of my entire root filesystem).

Right now I'm fighting with 'glib'.  Some things are calling for glib-1.2*, and that
just won't emerge because the ebuild (get this!) says gcc is incapable of making
an executable.  Faking it with packages.provided won't work because the
dependencies actually use some of the glib stuff during their own ebuilds.

I am partly to blame, of course.  I got frustrated with older ebuilds that were
causing some of the dependency trouble, and got carried away with
"emerge --prune", which I guess is just as broken as it says it is.

Anyway, here's what needs that old glib:

[EMAIL PROTECTED] portage # equery depends glib-1.2*
[ Searching for packages depending on glib-1.2*... ]
media-libs/libmovtar-0.1.3-r1
dev-python/wxpython-2.4.2.4-r3
x11-libs/wxGTK-2.4.2-r3
media-video/mjpegtools-1.6.2-r3
net-analyzer/ethereal-0.99.0
[EMAIL PROTECTED] portage #
Some dependencies are deep, so I cannot just unmerge that list.

There's only one ebuild that satisfies this need: 1.2.10-r5
* dev-libs/glib
     Available versions:  1.2.10-r5 2.6.5 2.8.4 2.8.5 2.8.6 ~2.10.3
     Installed:           2.8.6
     Homepage:            http://www.gtk.org/
     Description:         The GLib library of C routines

I've been building binary packages for quite a long while, but it
doesn't go back quite that far, so I really need it to emerge.  But
it won't.  It won't even configure, because something (autoconf?)  says gcc is at fault:

checking for gcc... gcc
checking whether the C compiler (gcc -O2 -march=pentium4 -fomit-frame-pointer -pipe -mfpmath=sse -msse2 -mmmx -fPIC -Wl,-O1 -ldl-Wl,-O1) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/glib-1.2.10-r5/work/glib-1.2.10/config.log

!!! ERROR: dev-libs/glib-1.2.10-r5 failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  glib-1.2.10-r5.ebuild, line 43:   Called econf '--with-threads=posix' '--enable-debug=yes'
  ebuild.sh, line 541:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.

[EMAIL PROTECTED] portage #

And that file it says to attach:
[EMAIL PROTECTED] portage # cat /var/tmp/portage/glib-1.2.10-r5/work/glib-1.2.10/config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:634: checking for a BSD compatible install
configure:687: checking whether build environment is sane
configure:744: checking whether make sets ${MAKE}
configure:783: checking for working aclocal
configure:796: checking for working autoconf
configure:809: checking for working automake
configure:822: checking for working autoheader
configure:835: checking for working makeinfo
configure:951: checking host system type
configure:972: checking build system type
configure:992: checking for ranlib
configure:1022: checking for gcc
configure:1135: checking whether the C compiler (gcc -O2 -march=pentium4 -fomit-frame-pointer -pipe -mfpmath=sse -msse2 -mmmx -fPIC -Wl,-O1 -ldl-Wl,-O1) works
configure:1151: gcc -o conftest -O2 -march=pentium4 -fomit-frame-pointer -pipe -mfpmath=sse -msse2 -mmmx -fPIC  -Wl,-O1 -ldl-Wl,-O1 conftest.c  1>&5
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../../../i686-pc-linux-gnu/bin/ld: cannot find -ldl-Wl,-O1
collect2: ld returned 1 exit status
configure: failed program was:

#line 1146 "configure"
#include "confdefs.h"

main(){return(0);}
[EMAIL PROTECTED] portage #
This looks like an error in the last option on that command line.  Is it now obsolete?  Could
I install an earlier gcc and make this ebuild use it?

One way out just occurred to me: clear a partition to install that tar of the root partition, and
use it to quickpkg a copy of that old glib.  Is there any simpler way?

--
Kevin O'Gorman, PhD

Reply via email to