From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: .la files and their future on Gentoo
Date: Tue, 05 Oct 2010 21:59:41 +0200 [thread overview]
Message-ID: <4CAB83AD.90105@gentoo.org> (raw)
In-Reply-To: <20101005153301.6e80e528@snowcone>
On 10/5/10 4:33 PM, Ciaran McCreesh wrote:
> On Tue, 05 Oct 2010 13:49:43 +0200
> Luca Barbato<lu_zero@gentoo.org> wrote:
>> Bluntly put, you seem to not know how libtool exactly works and
>> further down in the thread how linking exactly works. Please try to
>> learn the fine Gentoo docs on the subject and feel free to ask more
>> details on irc.
>
> Ah, so you do know exactly how libtool works?
I had to face it in code to workaround some cases already, it hadn't
been a nice experience.
> Great! It should be easy for you to fix it to only specify direct link
> dependencies then, thus solving the underlying problem in one place rather
> than working around it by fixing thousands of individual packages.
Sadly that would be already partially fixed by as-needed, the problem is
that libtool mangles also library search paths when using .la files and
that breaks in a number of situations we have in some sort of normal
uses of Gentoo.
> I look forward to testing your patch!
The patch to avoid the issues by omitting the usage of .la in case
--shared is provided is easy enough and solves quite well the problems
mentioned.
lu
next prev parent reply other threads:[~2010-10-05 19:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 19:54 [gentoo-dev] .la files and their future on Gentoo Jorge Manuel B. S. Vicetto
2010-10-02 21:12 ` Rémi Cardona
2010-10-03 11:53 ` David Leverton
2010-10-03 13:20 ` Richard Freeman
2010-10-03 13:39 ` David Leverton
2010-10-03 14:29 ` Luca Barbato
2010-10-03 15:39 ` David Leverton
2010-10-04 1:26 ` [gentoo-dev] " Duncan
2010-10-04 15:19 ` Richard Freeman
2010-10-05 1:55 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-05 7:52 ` Angelo Arrifano
2010-10-05 10:03 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-05 11:04 ` Angelo Arrifano
2010-10-05 11:25 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-05 11:28 ` Diego Elio Pettenò
2010-10-05 12:13 ` Angelo Arrifano
2010-10-05 11:40 ` [gentoo-dev] " Samuli Suominen
2010-10-05 11:49 ` [gentoo-dev] " Luca Barbato
2010-10-05 13:44 ` Angelo Arrifano
2010-10-05 14:33 ` Ciaran McCreesh
2010-10-05 19:59 ` Luca Barbato [this message]
2010-10-05 20:20 ` Ciaran McCreesh
2010-10-06 9:20 ` Luca Barbato
2010-10-06 10:04 ` David Leverton
2010-10-06 10:53 ` Jorge Manuel B. S. Vicetto
2010-10-05 18:23 ` David Leverton
2010-10-05 4:58 ` [gentoo-dev] " Duncan
2010-10-03 16:57 ` [gentoo-dev] " Angelo Arrifano
2010-10-04 0:48 ` Luca Barbato
2010-10-03 22:00 ` Rémi Cardona
2010-10-04 0:42 ` Luca Barbato
2010-10-04 6:35 ` Michał Górny
2010-10-04 7:00 ` Rémi Cardona
2010-10-03 16:50 ` Angelo Arrifano
2010-10-05 2:13 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-05 6:18 ` Ciaran McCreesh
2010-10-05 22:38 ` Enrico Weigelt
2010-10-05 22:54 ` David Leverton
2010-10-07 12:46 ` Enrico Weigelt
2010-10-07 4:45 ` Alec Warner
2010-10-07 5:32 ` Duncan
2010-10-07 6:21 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-07 6:31 ` Ciaran McCreesh
2010-10-08 14:23 ` Fabian Groffen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CAB83AD.90105@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox