Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 24450 - cant emerge pango, because linking failed
Summary: cant emerge pango, because linking failed
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-14 05:28 UTC by Tobias Gebhard
Modified: 2011-10-30 22:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Gebhard 2003-07-14 05:28:10 UTC
I have done a fresh basig gentoo installation.
After installing X i wanted to emerge pango, but it failed:
pango ist normaly compiled, but linking failed with this errormessatge:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lpango-1.0

Reproducible: Always
Steps to Reproduce:
1. nomrally install Gentoo Linux 1.4_rc4  from stage 1
2. emerge pango --> this will fail with the error described above

Actual Results:  
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lpango-1.0
collect2: ld returned 1 exit status
libtool: install: error: relink `libpangoft2-1.0.la' with the above command
before installing it
make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory `/var/tmp/portage/pango-1.2.1-r1/work/pango-1.2.1/pango'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/var/tmp/portage/pango-1.2.1-r1/work/pango-1.2.1/pango'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/pango-1.2.1-r1/work/pango-1.2.1/pango'
make: *** [install-recursive] Error 1

!!! ERROR: x11-libs/pango-1.2.1-r1 failed.
!!! Function einstall, Line 327, Exitcode 2
!!! einstall failed

Expected Results:  
pango should be installed without error.

mmh i searched buglists for pango, but it seems that i am the only one with that
problem...(users fault?) but i did it like it was descibed in the installation guide
if its not my fault, then it is a critical bug, but cant believe it (so i choose
normal as severity)
Comment 1 Spider (RETIRED) gentoo-dev 2003-07-14 12:47:07 UTC
now this is strange... 

Can you please paste output of "emerge info"??
Comment 2 Tobias Gebhard 2003-07-14 13:14:31 UTC
Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4)
=================================================================
System uname: 2.4.21-pfeifer-r1_pre2 i686 AMD Athlon(tm) XP 2600+
GENTOO_MIRRORS="http://www.fhh.opensource-mirror.de/gentoo.org/ http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="apm crypt cups imlib libwww mad mikmod motif ncurses nls oggvorbis svga xml2 xv zlib gdbm berkdb slang readline tcpd pam perl python X kde qt qtmt arts usagi gtk odbc 3dnow sse avi quicktime oss ssl cdr dvd sdl encode fbcon gif gnome png gtk2 java jpeg mmx mozilla mozaccess-builtin pdflib libg++ gpm mpeg nocardbus opengl samba spell truetype xmms x86"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
Comment 3 Paul Thompson 2003-08-02 20:57:57 UTC
I also have this problem. In looking at the build dir,
work/pango-1.2.1/pango/.libs/ has some libraries that
have a trailing "U". This results in some broken
symlinks (they point to the lib name without the "U")
and some direct references to the files without
the "U". I havent been able to figure out why so
far...
Comment 4 Paul Thompson 2003-08-03 15:36:19 UTC
hmmm.
ignore my previous post; that seems to have been a weird artifact
of going into the failed build dir and retrying 'make'.
The actual problem seems to be that pango tries to link
against stuff it installs _while_ its installing. Because
we use the image directory to install in, before qmerge, unless
you already have pango libs in the usual place (ie. /usr/lib)
then the link fails. This could be a bug for people for whom
the compile succeeds, as it would link against the _old_ pango
libs. Attached is a hack patch that enabled me to emerge this
package. It should use ${D}/usr/lib, but this is what I used...
Comment 5 Paul Thompson 2003-08-03 15:41:52 UTC
Well, I am unable to create an attachment with the !@#$ patch,
as bugzilla keeps telling me the file is empty. Never had
that problem before... here is cut/paste:

--- pango-1.2.1-r1.ebuild.orig  2003-08-03 18:21:00.098969134 -0400
+++ pango-1.2.1-r1.ebuild       2003-08-03 18:21:20.355118793 -0400
@@ -44,7 +44,8 @@
                myconf="${myconf}  --enable-debug"
        fi
        
-       econf ${myconf} --without-qt || die
+       LDFLAGS="-L/var/tmp/portage/pango-1.2.1-r1/image/usr/lib"
+       econf ${myconf} --without-qt "LDFLAGS=${LDFLAGS}" || die
        make || die "serial make failed" 
 }
Comment 6 foser (RETIRED) gentoo-dev 2003-08-04 08:05:44 UTC
Paul that is a problem on your side, those paths should already be properly handled. And its another problem, so it shouldnt have been posted here.

Reporter, your problem might not be related to pango directly, please search bugzilla for similar errors. It might have to do with gcc config or your libtool version or something else in the compile chain (what is your libtool version btw?).
Comment 7 Tobias Gebhard 2003-08-04 10:49:30 UTC
Well, tried something here and there but with no success, so i reinstalled it from scratch, modified the make.conf only a little bit and now the system runs fine.

Maybe there was an error in my (copied from another system) make.conf. Dont know.