Re: DSO linking changes for wheezy

2010-11-15 Thread Matt Turner
On Mon, Nov 15, 2010 at 8:15 PM, Samuel Thibault wrote: > Matt Turner, le Mon 15 Nov 2010 19:51:10 -0500, a écrit : >> On Mon, Nov 15, 2010 at 7:24 PM, Roger Leigh wrote: >> > What's the actual problem --as-needed is trying to solve? >> > >> > The answer is mainly unwanted libraries being linked

Re: DSO linking changes for wheezy

2010-11-15 Thread Samuel Thibault
Matt Turner, le Mon 15 Nov 2010 19:51:10 -0500, a écrit : > On Mon, Nov 15, 2010 at 7:24 PM, Roger Leigh wrote: > > What's the actual problem --as-needed is trying to solve? > > > > The answer is mainly unwanted libraries being linked in as a result > > of using pkg-config (and various other -conf

Re: DSO linking changes for wheezy

2010-11-15 Thread Roland McGrath
> I can't see why you think --as-needed is fundamentally wrong or unnecessary. It is fundamentally wrong because -lfoo means I demand that the initializers of libfoo.so run, whether or not I called anything in it. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject

Re: DSO linking changes for wheezy

2010-11-15 Thread Matt Turner
On Mon, Nov 15, 2010 at 7:24 PM, Roger Leigh wrote: > What's the actual problem --as-needed is trying to solve? > > The answer is mainly unwanted libraries being linked in as a result > of using pkg-config (and various other -config variants), though there > are other, lesser, culprits.  The pkg-c

Re: DSO linking changes for wheezy

2010-11-15 Thread Matthias Klose
On 16.11.2010 01:24, Roger Leigh wrote: On Mon, Nov 15, 2010 at 11:02:57PM +0100, Matthias Klose wrote: On 14.11.2010 16:06, Roger Leigh wrote: While I understand the rationale for --no-copy-dt-needed-entries for preventing encapsulation violations via indirect linking, I don't agree with the u

Re: DSO linking changes for wheezy

2010-11-15 Thread Matthias Klose
On 14.11.2010 13:19, Julien Cristau wrote: On Fri, Oct 29, 2010 at 15:43:57 +0200, Matthias Klose wrote: For wheezy I'm planning to change the linking behaviour for DSOs (turning on --as-needed and --no-copy-dt-needed-entries. The rationale is summarized in http://wiki.debian.org/ToolChain/DSOL

Re: DSO linking changes for wheezy

2010-11-15 Thread Roger Leigh
On Mon, Nov 15, 2010 at 11:02:57PM +0100, Matthias Klose wrote: > On 14.11.2010 16:06, Roger Leigh wrote: While I understand the rationale for --no-copy-dt-needed-entries for preventing encapsulation violations via indirect linking, I don't agree with the use of --as-needed *at all*.

Re: DSO linking changes for wheezy

2010-11-15 Thread Roland McGrath
> On 15.11.2010 07:16, Roland McGrath wrote: > yes, OpenSuse is using --as-needed, but not --no-add-needed. That is a pretty nutty choice. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: htt

Re: DSO linking changes for wheezy

2010-11-15 Thread Philipp Kern
On Mon, Nov 15, 2010 at 11:02:57PM +0100, Matthias Klose wrote: > maybe, and fix it in N - ~100 packages? Or fix the ~100 packages? > The point of injection is for discussion. I would prefer having > this set in dpkg-buildflags, and then disabled by these ~100 > packages. Note that this is proba

Re: DSO linking changes for wheezy

2010-11-15 Thread Matthias Klose
On 14.11.2010 16:06, Roger Leigh wrote: While I understand the rationale for --no-copy-dt-needed-entries for preventing encapsulation violations via indirect linking, I don't agree with the use of --as-needed *at all*. If a library has been explicitly linked in, it shouldn't be removed. This is

Re: DSO linking changes for wheezy

2010-11-15 Thread Matthias Klose
On 15.11.2010 07:16, Roland McGrath wrote: airlied_, does Fedora use --as-needed by default? Fedora 14 too? mattst88: yes The naming of the options makes people easily confused. --no-add-needed is the only option Fedora's gcc passes. yes, OpenSuse is using --as-needed, but not --no-add-ne

Re: Intel Wifi Link 5100 -> halt system on Squeeze

2010-11-15 Thread Lennart Sorensen
On Sat, Nov 13, 2010 at 04:58:52PM -0300, Felipe Valverde wrote: > Definitively the culprit is the new driver. I tried the testing and the > > unstable driver but they just do not work properly. They will freeze my > > laptop as soon as I try to connect to a wireless network. My fix is just a > > b