Bug 76406 – fontconfig - emerge of kdelibs can't find: /var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description damage 2005-01-02 07:16:59 UTC]

the emerge progress of kdelibs cant't find the file:
/var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la
please notice the double slash. the file /usr/lib/libfreetype.la exists. so i think it's just a string concat problem?


Reproducible: Always
Steps to Reproduce:
1. emerge kdelibs

Actual Results:  
grep: /var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la: No such
file or directory
/bin/sed: can't read
/var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la: No such file
or directory
libtool: link:
`/var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la' is not a
valid libtool archive
make[4]: *** [libDCOP.la] Error 1
make[4]: Leaving directory
`/var/tmp/portage/kdelibs-3.3.2-r1/work/kdelibs-3.3.2/dcop'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/kdelibs-3.3.2-r1/work/kdelibs-3.3.2/dcop'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/var/tmp/portage/kdelibs-3.3.2-r1/work/kdelibs-3.3.2/dcop'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.3.2-r1/work/kdelibs-3.3.2'
make: *** [all] Error 2


Expected Results:  
it should emerge kdelibs

i allready tried to re-emerge freetype - it doesn't work, too. i really think
it's a problem of the kdelibs emerge progress.

i will set Secerity to Blocker, because i can't emerge kde without kdelibs.

[Comment 1 Carsten Lohrke (RETIRED) 2005-01-02 07:37:25 UTC]

damage: Usually `find /usr/lib -iname "*\.la" -exec sed -i -r -e "s:/var/tmp/portage/.*/image/::g" '{}' \;` is a workaround for the problem, but the changed mtime will cause portage not to uninstall the affected file(s), if they do not get overwritten by later ebuild versions afaik.

base-system herd: I have seen this problem with different ebuilds maybe two dozen times or so and I'm pretty sure it has nothing to do with invalid ebuilds. Does the libtool version mismatch issue come into play here or is this still another unknown problem?

[Comment 2 damage 2005-01-02 08:09:47 UTC]

# Libraries that this one depends upon.
dependency_libs=' /var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la -lz /usr/lib/libexpat.la'

hmm... it's a problem of a library in media-libs/fontconfig... so i will move this issue to the component library

[Comment 3 damage 2005-01-02 08:17:31 UTC]

sorry, i've forgot to tell, that i have found the line above in /usr/lib/fontconfig.la

[Comment 4 SpanKY 2005-01-02 18:32:24 UTC]

often times it's just an old bug that's been fixed

if you re-emerge fontconfig, does the .la file read correctly ?

[Comment 5 damage 2005-01-03 05:35:23 UTC]

same problem after re-emerge.
btw: libconfig.la is the only file with this silly path

[Comment 6 damage 2005-01-03 05:36:47 UTC]

no, its not true, i didnt re-emerge fontconfig... i will try now... sorry

[Comment 7 damage 2005-01-03 05:48:24 UTC]

# Libraries that this one depends upon.
dependency_libs=' /usr/lib/libfreetype.la -lz /usr/lib/libexpat.la'

hmmm... it looks good in version 2.2.3
so, this issue is/was needless?!

[Comment 8 SpanKY 2005-01-03 06:09:28 UTC]

like i said, it should be fixed, but there's no real way for forcing people out there to re-emerge their packages