rm -f /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/freetype/cache/* rmdir /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/freetype/cache rm -f /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/freetype/internal/* rmdir /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/freetype/internal rmdir: failed to remove `/var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/freetype/internal': No such file or directory make: [install] Error 1 (ignored) please provide to drop also unnecessary .la files, /usr/lib64/libfreetype.la is installed even with USE flag static-libs not enabled.
It is confirmed also in 2.4.9
(In reply to comment #0) > rm -f > /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/ > freetype/cache/* > rmdir > /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/ > freetype/cache > rm -f > /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/ > freetype/internal/* > rmdir > /var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/ > freetype/internal > rmdir: failed to remove > `/var/tmp/portage/media-libs/freetype-2.4.9-r1/image//usr/include/freetype2/ > freetype/internal': No such file or directory > make: [install] Error 1 (ignored) Doesn't look to be anything we do. File a bug upstream. > please provide to drop also unnecessary .la files, /usr/lib64/libfreetype.la > is installed even with USE flag static-libs not enabled. I honestly don't care. I ripped out the static-libs stuff on purpose. See bug #392099. When base-system can agree on how exactly static-libs is supposed to work, let me know.
(In reply to comment #2) > When base-system can agree on how exactly static-libs is supposed to work, > let me know. freetype2.pc has working Libs.private: line so get libraries for static linking with `pkg-config --static --libs freetype2` for example. when this condition gets met, the libtool archive is useless and harmless too since they cause overlinking through dependency_libs='-lfoo' in reverse dependencies. see, http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-libs/freetype/freetype-2.4.9-r1.ebuild?r1=1.1&r2=1.2
(In reply to comment #3) > (In reply to comment #2) > > When base-system can agree on how exactly static-libs is supposed to work, > > let me know. > > freetype2.pc has working Libs.private: line so get libraries for static s/so// > linking with `pkg-config --static --libs freetype2` for example. > when this condition gets met, the libtool archive is useless and harmless s/harmless/harmful/ sorry about typing errors, it's late.
(In reply to comment #3) > (In reply to comment #2) > > When base-system can agree on how exactly static-libs is supposed to work, > > let me know. > > freetype2.pc has working Libs.private: line so get libraries for static > linking with `pkg-config --static --libs freetype2` for example. > when this condition gets met, the libtool archive is useless and harmless > too since they cause overlinking through dependency_libs='-lfoo' in reverse > dependencies. > > see, > > http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-libs/freetype/freetype- > 2.4.9-r1.ebuild?r1=1.1&r2=1.2 Thanks.
Sorry, I was in a foul mood this morning. If you can identify the cause behind the error message I will send it upstream. Thanks.
This version is no longer in the tree. Please re-open if this problem appears in current versions.