Le Tuesday 11 October 2005 16:02, Rosenstrauch, David a écrit : | I've got an AUR package that I'm trying to rebuild, but it's not | compiling due to the libtool slay: | | grep: /usr/lib/libstdc++.la: No such file or directory | /bin/sed: can't read /usr/lib/libstdc++.la: No such file or directory | libtool: link: `/usr/lib/libstdc++.la' is not a valid libtool archive | | How does one go about whacking this?
somewhere in your system, there is an .la file that contains the
"/usr/lib/libstdc++.la" reference. the package that contains this file
that contains this reference has to be libtool-slayed to make your
package build.
to check where this reference comes from, do this:
[EMAIL PROTECTED] ~]$ cd /usr/lib
[EMAIL PROTECTED] lib]$ grep "libstdc++.la" *.la
this should result in something like this output:
somefile.la:dependency_libs='... ... ... /usr/lib/libstdc++.la ... ... ...'
then you need to find out what package owns somefile.la:
pacman -Qo /usr/lib/somefile.la
and then this package needs to be slayed. this means simply that you need
to remove the somefile.la you found from the package, re-relase it and
your package in trouble will build again.
to remove all .la files from some package, you can add this line to the
build() at the end in the PKGBUILD:
find $startdir/pkg -name '*.la' -exec rm {} \;
this is more or less it. remember: kde apps sometimes need the .la file
for kde module loading feature (like filelight, kaffeine ...) for kpart
or other runtime-loading instructions. always test the packages you
slayed on functionallity and if something is broken, this package
probably cannot be slayed.
hope that helps,
greetings,
Damir
PS
feel free to wiki-fy this infos
--
The people who really run organizations are usually found several
levels down, where it is still possible to get things done.
(Small Gods)
pgphxWFhT3vMH.pgp
Description: PGP signature
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
