public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Oron Peled <oron@actcom.co.il>
To: crossgcc@sourceware.org
Cc: Richard Strand <richard.strand@icomera.com>,
	        "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Subject: Re: Success building seemingly native toolchain
Date: Tue, 29 Sep 2009 23:07:00 -0000	[thread overview]
Message-ID: <200909300107.04449.oron@mailhub.home.il> (raw)
In-Reply-To: <4AC23A57.3060406@icomera.com>

On Tuesday, 29 בSeptember 2009 18:48:23 Richard Strand wrote:
> The toolchain is working perfectly for me and I've not run into any 
> problems yet. Changing to -O2 sounds like a good idea as long as it 
> doesn't break builds for any other architectures.

I'm not sure if it's related, but AFAIR g++ only consider inline
of C++ methods with -O2 or more (maybe some of the inline methods
are crucial for g++ or glibc itself).

-- 
Oron Peled                                 Voice: +972-4-8228492
oron@actcom.co.il                  http://users.actcom.co.il/~oron
"A standard for copy protection is as premature as a standard for 
teleportation."
                                --- Noted computer security expert and
                                    Princeton University Professor
                                    Edward Felten.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2009-09-29 23:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 16:58 Richard Strand
2009-09-28 20:09 ` Yann E. MORIN
2009-09-29 16:29   ` Martin Guy
2009-09-29 16:48   ` Richard Strand
2009-09-29 23:07     ` Oron Peled [this message]
2009-09-30 12:04       ` Richard Strand
2009-10-02 18:30   ` Richard Strand
2009-10-03 16:25     ` Yann E. MORIN

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=200909300107.04449.oron@mailhub.home.il \
    --to=oron@actcom.co.il \
    --cc=crossgcc@sourceware.org \
    --cc=richard.strand@icomera.com \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).