I am attempting to install Gentoo for the first time. The only nonstandard aspect of my configuration that I'm aware of is that I have the root filesystem mounted over nfs. A plain "emerge pango" fails with the error message: libtool: link: warning: library `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/../../..//libfreetype.la' was moved. libtool: link: cannot find the library `/var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la' Reproducible: Always Steps to Reproduce: /etc/make.conf contains: # These settings were set by the catalyst build script that automatically built this stage # Please consult /etc/make.conf.example for a more detailed example CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" CXXFLAGS="${CFLAGS}" USE="-kde cdr" /var/lib/portage/world contains: app-cdr/cdrtools sys-kernel/gentoo-sources sys-apps/vixie-cron app-editors/emacs sys-fs/reiserfsprogs app-editors/nano sys-kernel/linux-headers media-video/nvidia-glx x11-base/xorg-x11 sys-libs/glibc net-nds/portmap app-admin/syslog-ng media-libs/freetype emerge --info reports: Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.4.28-gentoo-r5 i686) ================================================================= System uname: 2.4.28-gentoo-r5 i686 Intel(R) Pentium(R) III Mobile CPU 1133MHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#2, Feb 10 2005, 19:52:20)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.21-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X apm arts avi berkdb bitmap-fonts cdr crypt cups encode f77 font-server foomaticdb fortran gdbm gif gnome gpm gtk gtk2 imlib ipv6 jpeg libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl spell ssl svga tcpd truetype truetype-fonts type1-fonts xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Created attachment 50973 [details] output of "emerge freetype"
Created attachment 50974 [details] output of "emerge pango"
`/var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la' It shouldn't be looking in the temporary build directory for the lib archive, do we need to libtoolize it?
no, there is no proof here anyway that the error actually comes from pango itself. andrew, please do 'grep /var/tmp /usr/lib/*.la' and past the output here.
gentoo root # grep /var/tmp /usr/lib/*.la /usr/lib/libexpat.la:libdir='/var/tmp/portage/expat-1.95.8/image//usr/lib' /usr/lib/libfontconfig.la:dependency_libs=' /var/tmp/portage/freetype-2.1.5-r1/image//usr/lib/libfreetype.la -lz /usr/lib/libexpat.la' /usr/lib/libfreetype.la:libdir='/var/tmp/portage/freetype-2.1.5-r1/image//usr/lib'
Sorry, I meant in freetype, not in pango.
andrew : remerge freetype, fontconfig, expat (in that order) and you should be fine. obz : ft 2.1.9 uses destdir, that should prevent this from happening.
Created attachment 50994 [details] output of emerge freetype, fontconfig, expat
Still fails... see the attachment for emerge output. I thank you for trying to get me fixed up after the fact. However, note that I attempted to carefully follow the install instructions in the Gentoo Handbook and got this failure. Thus my intention in filing this bug report is not so much to ask "how do I get pango to compile now?", but "why did the standard install process fail?"
no it doesn't fail normally.. only in some odd instances.. and your error message is actually different now. And this has nothing todo with pango. tcltk, please fix expat to use DESTDIR to avoid these kind of problems, this is the second time i ask this.
expat is built upon old autotools ... you cant simply start using DESTDIR and have it magically work instead i've added `dosed` calls to src_install() to make sure libexpat.la doesnt include $D crap
I hadn't looked at the pack, use destdir/running libtoolize/whatever other solution suitable as long as it works. I was under the impression expat is maintained upstream & assumed the auto* got updated.