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: <4A10EC0D.1050908@gmail.com> Date: Mon, 18 May 2009 06:03:09 +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: gcc linker flags References: <4A10C4A9 DOT 4090208 AT cornell DOT edu> In-Reply-To: <4A10C4A9.4090208@cornell.edu> 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 Ken Brown wrote: > I've seen builds by other people in which the following linker flags are > used: > > (a) --enable-auto-import > (b) --enable-runtime-pseudo-reloc > (c) --enable-auto-image-base > > My understanding is that (b) and (c) are already the default and that > (a) will be the default when binutils is updated. Moreover, (a) is > mostly used to suppress errors (though there are exceptions where it > makes a difference). So none of these are really needed in most cases. > Do I have it more or less right? You could equally say "All or some of them are needed in most cases, but hopefully the compiler and toolchain will take care of it for you in future and you won't have to bother about them". 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/