Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 62597 - emerge of kdebase fails due to a wrong path to libidn.la
Summary: emerge of kdebase fails due to a wrong path to libidn.la
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
: 66089 85623 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-09-02 02:33 UTC by Torsten Balzer
Modified: 2005-03-17 07:28 UTC (History)
4 users (show)

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 Torsten Balzer 2004-09-02 02:33:56 UTC
I tried to emerge -u kdebase (previously kde 3.3.0_beta was installed). The configure script runs fine, but the compilation itself stops. During the make process, a path seems to be created (/var/tmp/portage/libidn-0.5.4/image//usr/lib/libidn.la) which doesn't exist. 


Reproducible: Always
Steps to Reproduce:
1. emerge kdebase
2.
3.

Actual Results:  
Emerge stops, leaving the following error message:

-- snip --
grep: /var/tmp/portage/libidn-0.5.4/image//usr/lib/libidn.la: No such file or
directory
/bin/sed: can't read /var/tmp/portage/libidn-0.5.4/image//usr/lib/libidn.la: No
such file or directory
libtool: link: `/var/tmp/portage/libidn-0.5.4/image//usr/lib/libidn.la' is not a
valid libtool archive
make[3]: *** [kded_favicons.la] Error 1
make[3]: Leaving directory
`/var/tmp/portage/kdebase-3.3.0/work/kdebase-3.3.0/libkonq/favicons'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kdebase-3.3.0/work/kdebase-3.3.0/libkonq'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdebase-3.3.0/work/kdebase-3.3.0'
make: *** [all] Error 2 


Of course, the libidn.la is present in /usr/lib. I reemerged libidn several
times and tried older (stable) versions, too.

System configuration:

Gentoo Base System version 1.5.3
Portage 2.0.50-r10 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r0,
2.4.25-gentoo-r1)
=================================================================
System uname: 2.4.25-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=i686 -fomit-frame-pointer -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown
/usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=i686 -fomit-frame-pointer -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.inode.at/ http://mirror.gentoo.no/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X acpi alsa arts avi berkdb cdr crypt cups dga dvb dvd dvdr encode
foomaticdb gdbm gif gpm gtk gtk2 imagemagick imlib java jikes jpeg kde libg++
libwww linguas_de lirc mad mikmod mmx motif mozilla mpeg mysql ncurses nls
oggvorbis opengl oss pam pda pdflib perl png python qt quicktime readline
scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype unicode usb
x86 xml xml2 xmms xv zlib" 

There is a bug that *seems* similar to this: 48300
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2004-09-02 03:13:43 UTC
please try to `emerge libidn` again
Comment 2 Torsten Balzer 2004-09-02 04:44:34 UTC
I already did. I reemerged libidn-5.4.0 twice, then tried libidn-3.7.0, then switched back to 5.4.0 again as the result didn't change. 
Comment 3 Torsten Balzer 2004-09-02 04:46:07 UTC
Sorry, messed up the version numbers: 0.5.4 and 0.3.7, of course.
Comment 4 Carsten Lohrke (RETIRED) gentoo-dev 2004-09-02 05:10:13 UTC
o.k. only to be sure about it - what's the output of `qpkg -l libidn`?
Comment 5 Caleb Tennis (RETIRED) gentoo-dev 2004-09-02 05:28:54 UTC
Try grepping for "/var/tmp/portage" in /usr/lib/*.la and see if you can find which file is causing the offense.
Comment 6 Torsten Balzer 2004-09-02 09:06:29 UTC
@Caleb Tennis
ahab lib # grep "/var/tmp/portage" /usr/lib/*.la
ahab lib #

Nothing...

Excerpt from libidn.la:

---snip---
# Is this an already installed library?
installed=yes

# Should we warn about portability when linking against -modules?
shouldnotlink=no

# Files to dlopen/dlpreopen
dlopen=''
dlpreopen=''

# Directory that this library needs to be installed in:
libdir='/usr/lib'

EOF
Comment 7 Torsten Balzer 2004-09-02 09:09:48 UTC
@Carsten Lohrke:

ahab lib # qpkg -l libidn
net-dns/libidn-0.5.4 *
CONTENTS:
/usr
/usr/bin
/usr/bin/idn
/usr/lib
/usr/lib/libidn.la
/usr/lib/libidn.so.11.4.4
/usr/lib/pkgconfig
/usr/lib/pkgconfig/libidn.pc
/usr/lib/libidn.so.11 -> libidn.so.11.4.4 1093981361
/usr/lib/libidn.a
/usr/share
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/idn.1.gz
/usr/share/man/man3
/usr/share/man/man3/stringprep_4zi.3.gz
/usr/share/man/man3/idna_to_unicode_8z8z.3.gz
/usr/share/man/man3/tld_check_8z.3.gz
/usr/share/man/man3/punycode_encode.3.gz
/usr/share/man/man3/punycode_decode.3.gz
/usr/share/man/man3/idna_to_unicode_4z4z.3.gz
/usr/share/man/man3/pr29_4.3.gz
/usr/share/man/man3/stringprep_utf8_to_unichar.3.gz
/usr/share/man/man3/stringprep_convert.3.gz
/usr/share/man/man3/stringprep.3.gz
/usr/share/man/man3/tld_check_4.3.gz
/usr/share/man/man3/idna_to_ascii_8z.3.gz
/usr/share/man/man3/tld_get_table.3.gz
/usr/share/man/man3/pr29_8z.3.gz
/usr/share/man/man3/tld_check_4t.3.gz
/usr/share/man/man3/stringprep_locale_charset.3.gz
/usr/share/man/man3/idna_to_unicode_lzlz.3.gz
/usr/share/man/man3/idna_to_unicode_44i.3.gz
/usr/share/man/man3/idna_to_unicode_8z4z.3.gz
/usr/share/man/man3/stringprep_4i.3.gz
/usr/share/man/man3/tld_check_4z.3.gz
/usr/share/man/man3/stringprep_utf8_to_ucs4.3.gz
/usr/share/man/man3/idna_to_ascii_4i.3.gz
/usr/share/man/man3/stringprep_ucs4_to_utf8.3.gz
/usr/share/man/man3/stringprep_ucs4_nfkc_normalize.3.gz
/usr/share/man/man3/idna_to_unicode_8zlz.3.gz
/usr/share/man/man3/tld_check_lz.3.gz
/usr/share/man/man3/stringprep_profile.3.gz
/usr/share/man/man3/stringprep_utf8_to_locale.3.gz
/usr/share/man/man3/idna_to_ascii_4z.3.gz
/usr/share/man/man3/pr29_4z.3.gz
/usr/share/man/man3/tld_get_4z.3.gz
/usr/share/man/man3/tld_get_z.3.gz
/usr/share/man/man3/stringprep_check_version.3.gz
/usr/share/man/man3/tld_get_4.3.gz
/usr/share/man/man3/idna_to_ascii_lz.3.gz
/usr/share/man/man3/tld_check_4tz.3.gz
/usr/share/man/man3/tld_default_table.3.gz
/usr/share/man/man3/stringprep_locale_to_utf8.3.gz
/usr/share/man/man3/stringprep_utf8_nfkc_normalize.3.gz
/usr/share/man/man3/stringprep_unichar_to_utf8.3.gz
/usr/share/info
/usr/share/info/libidn.info.gz
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/punycode.el
/usr/share/emacs/site-lisp/idna.el
/usr/share/locale
/usr/share/locale/de
/usr/share/locale/de/LC_MESSAGES
/usr/share/locale/de/LC_MESSAGES/libidn.mo
/usr/include
/usr/include/tld.h
/usr/include/idn-int.h
/usr/include/idn-free.h
/usr/include/idna.h
/usr/include/stringprep.h
/usr/include/punycode.h
/usr/lib/libidn.so -> libidn.so.11.4.4 1093981361


Comment 8 Ralph Little 2004-09-22 13:05:37 UTC
I have this problem also upgrading from KDE 3.2 to 3.3
A quick trawl through my /usr tree reveals that all /usr/kde/3.3/lib/*.la have entries for libidn of "/var/tmp/portage/libidn-0.3.7/image//usr/lib/libidn.la".
I will investigate further
Comment 9 Ralph Little 2004-09-23 02:13:30 UTC
More information which may assist.
I interrupted the upgrade of KDE at some point after the emerge of kdecore, rebooted and restarted the process. 
I noticed during build of one of the modules messages like "warning: library has been moved: libidn" - not the correct text, but built from what I remember. Sorry, I didn't realise that it was significant at the time as the libidn problem had not manifested itself at that point.
I suspect that the problem originated with the emerge of kdecore (but that is a guess) and the problem has filtered down the dependency tree of all of the kde modules that emerge subsequently.
Because I need to get it working, I used sed to correct all the dependency entries I could find most of which being  /usr/kde/3.3/lib/*.la and kicked the emerge off again. Seems OK so far if I report nothing else, assume that that fixed it.
Still have no idea how it happened in the first place. Perhaps interrupting the build was the problem....?
Comment 10 Caleb Tennis (RETIRED) gentoo-dev 2004-09-23 19:21:40 UTC
yeah, that probably did it.  sed is probably the easiest fix here, not really sure how it failed in the first place though.
Comment 11 Caleb Tennis (RETIRED) gentoo-dev 2004-10-02 06:17:51 UTC
*** Bug 66089 has been marked as a duplicate of this bug. ***
Comment 12 Wesley Hill 2004-10-02 18:02:46 UTC
I took Simone Gotti's advice (http://bugs.gentoo.org/show_bug.cgi?id=66089) and reemerged kdelibs, now kdebase is compiling nicely. I don't know how the problem was caused though, since my build wasn't interrupted like Ralph Little's, although I'm happy to blame my occasionally flakey ram.

Sorry for the dupe, I guess I searched for the wrong thing.
Comment 13 Bret Towe 2004-10-10 14:12:03 UTC
i encountered this on my amd64 system
the problem is the library libidn has the wrong path in its .la file
to where the lib file resides and after its wrong there it spreads
as other apps add its info to their .la file

fix libidn and its .la problem then you pretty much have to ether fix all the .la files on the system or remerge all the apps that own the .la files
Comment 14 Caleb Tennis (RETIRED) gentoo-dev 2004-12-06 19:53:18 UTC
Yep - see above comment.  Should all hopefully be fixed in portage.
Comment 15 Gregorio Guidi (RETIRED) gentoo-dev 2005-03-17 07:28:17 UTC
*** Bug 85623 has been marked as a duplicate of this bug. ***