From: Richard Strand <richard.strand@icomera.com>
To: yann.morin.1998@anciens.enib.fr
Cc: crossgcc@sourceware.org
Subject: Success building seemingly native toolchain
Date: Tue, 15 Sep 2009 16:58:00 -0000 [thread overview]
Message-ID: <4AAFC7B0.20605@icomera.com> (raw)
Hi,
I had a problem where crosstool-ng would break when it was building NPTL
when using glibc 2.7 and above. As I am using i686 to build i486 I
suspect this was the "seemingly native toolchains do not build" bug. I
have now managed to successfully get this to build by setting
CT_TARGET_CFLAGS="-O2".
Is this a known workaround for the problem (I couldn't find anything on
it), and does this work for everyone else?
Regards,
Richard Strand
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2009-09-15 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 16:58 Richard Strand [this message]
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
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=4AAFC7B0.20605@icomera.com \
--to=richard.strand@icomera.com \
--cc=crossgcc@sourceware.org \
--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).