On Tue, 11 Oct 2005, Rosenstrauch, David wrote:

> Ah, yes.  That did the trick.
> 
> One of the packages that this package was dependent on had the .la
> file in it.  When I modify that PKGBUILD to whack the .la, and rebuild
> both pkgs, the problem goes away.

Also, if the offending package is in an official repo, you should submit a
bug report.


> 
> Thanks Damir.
> 
> DR
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Behalf Of Damir Perisa
> > Sent: Tuesday, October 11, 2005 12:55 PM
> > To: General Discusson about Arch Linux
> > Subject: Re: [arch] How do you libtool slay a package?
> 
> 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 {} \;
> 
> ...
> 
> ==============================================================================
> Please access the attached hyperlink for an important electronic 
> communications disclaimer: 
> 
> http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
> 
> ==============================================================================
> 
> 
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to