X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49FD6393.5040801@gmail.com> Date: Sun, 03 May 2009 10:27:47 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] [1.7] pl-0.10.2-1 - the Parma Polyhedra Library References: <49FBF62E DOT 3060904 AT cs DOT unipr DOT it> <49FC71B7 DOT 3030000 AT cwilson DOT fastmail DOT fm> <49FC7EF9 DOT 4050908 AT gmail DOT com> <49FCACE6 DOT 4000104 AT cwilson DOT fastmail DOT fm> <49FCE65C DOT 7040409 AT gmail DOT com> <49FCE88D DOT 6040709 AT cwilson DOT fastmail DOT fm> In-Reply-To: <49FCE88D.6040709@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Charles Wilson wrote: > Dave Korn wrote: >> Charles Wilson wrote: >>> Dave Korn wrote: >>>> Charles Wilson wrote: >>>>> Roberto Bagnara wrote: >>>>> >>>>>> concerning the need to link with "LDFLAGS=-Wl,--enable-auto-import", >>>>>> I am wondering if there is something we could do upstream to simplify >>>>>> the life of Cygwin users. If so, please let me know. >>>>> In gcc-4.x --enable-auto-import is the default. >>>> No, right now it's the default setting in binutils CVS, but I haven't added >>>> it to the gcc specs. (Guess I should for the benefit of those with older >>>> linkers). >>> You're right; I was confused. I was thinking of the binutils change. >>> However, I wonder about the gcc thing. If the specs file includes >>> -Wl,--enable-auto-import, and I pass -Wl,--disable-auto-import on the >>> command line, who wins? >> >> I just don't know. I suspect it may even depend; e.g. DRIVER_SELF_SPECS >> gets applied early, LINK_SPEC later, but I haven't experimented. (On the >> actual ld command-line itself, later options always override earlier ones.) > > In that case, maybe it's better to just leave the default behavior up to > binutils and not try to over-specify using the specs file approach. I'm not sure. It's the compiler that knows what it needs, which is the same regardless of binutils' preferences, I'm leaning toward the idea that it should be in the linker specs for the benefit of anyone using older binutils. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/