delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE |
X-Spam-Check-By: | sourceware.org |
X-Mail-Handler: | MailHop Outbound by DynDNS |
X-Report-Abuse-To: | abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) |
X-MHO-User: | U2FsdGVkX19Ke7RmBst1exzJRShV7wMI |
Date: | Sat, 14 Apr 2012 15:01:03 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: gcc: turning off large-address awareness |
Message-ID: | <20120414190103.GC17287@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <4F896504 DOT 3030006 AT cornell DOT edu> <CA+sc5mnBXZ_+R9OKUX2idT_TBxE82U4ZfbOkcuWZgn9Y6TGxeA AT mail DOT gmail DOT com> <4F89B215 DOT 9050903 AT cornell DOT edu> <20120414173342 DOT GD15801 AT ednor DOT casa DOT cgf DOT cx> <4F89C67B DOT 30905 AT cornell DOT edu> |
MIME-Version: | 1.0 |
In-Reply-To: | <4F89C67B.30905@cornell.edu> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Sat, Apr 14, 2012 at 02:48:27PM -0400, Ken Brown wrote: >On 4/14/2012 1:33 PM, Christopher Faylor wrote: >> You're right that there isn't a way to disable --large-address-aware >> but, since it's part of the specs, I'm not sure what would take >> precedence if there was a --disable* option. >> >> You could try using the above to create your own spec file and use >> that on the command line for gcc, cumbersome as it is. > >That works, thanks. I didn't know about spec files. I'll try to remember to add a --disable option to my next binutils release. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |