X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4A10C4A9.4090208@cornell.edu> Date: Sun, 17 May 2009 22:15:05 -0400 From: Ken Brown User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: gcc linker flags Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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? I'm mainly interested in gcc-4 in cygwin 1.7, but if the answers would be different for gcc-3 or cygwin 1.5, I'd like to know that too. Thanks. Ken -- 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/