From: Daniel Diaz <Daniel.Diaz@univ-paris1.fr>
To: cygwin@cygwin.com
Subject: Re: gcc: turning off large-address awareness
Date: Mon, 21 May 2012 07:35:00 -0000 [thread overview]
Message-ID: <loom.20120521T092735-314@post.gmane.org> (raw)
In-Reply-To: <20120414190103.GC17287@ednor.casa.cgf.cx>
Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:
>
> 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
>
>
Hi Christopher,
when do you plan to release a version of binutils recognizing a
--disable-large-address-aware flag ?
Daniel
--
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
next prev parent reply other threads:[~2012-05-21 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 11:52 Ken Brown
2012-04-14 16:37 ` Earnie Boyd
2012-04-14 17:21 ` Ken Brown
2012-04-14 17:34 ` Christopher Faylor
2012-04-14 17:53 ` Earnie Boyd
2012-04-14 18:51 ` Ken Brown
2012-04-14 18:57 ` Christopher Faylor
2012-04-14 18:48 ` Ken Brown
2012-04-14 19:01 ` Christopher Faylor
2012-05-21 7:35 ` Daniel Diaz [this message]
2012-06-20 11:19 Daniel Diaz
2012-06-20 14:49 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120521T092735-314@post.gmane.org \
--to=daniel.diaz@univ-paris1.fr \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).