From: David Fernandez <david.fernandez.work@googlemail.com>
To: crossgcc@sourceware.org
Subject: When building a crossgcc for arm-eabi the test suite gives tons of failures.
Date: Thu, 31 May 2012 19:29:00 -0000 [thread overview]
Message-ID: <4FC7C66E.4010001@googlemail.com> (raw)
Hi there,
I'm building a cross-compiler for arm-eabi out of gcc-4.7.0 and
newlib-1.20.0, after successfully cross-compiling binutils-2.22, which
passed their included tests suite as expected.
I configure it like:
$ ./.../configure --target=arm-eabi --enable-languages=c,c++
--with-gnu-as --with-gnu-ld --with-newlib
--with-gcc-include-dir=/usr/local/arm-eabi/include -v 2>&1 | tee
configure.out
$ make -w all check 2>&1 | tee make.out
I get lots of FAIL messages. I tried to remove the "--with-..." options,
just in case that the test suites were too picky, but it fails the same way.
Is that expected in this kind of builds?
Otherwise, what I'm I doing wrong?
Cheers
David Fernandez
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2012-05-31 19:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FC7C66E.4010001@googlemail.com \
--to=david.fernandez.work@googlemail.com \
--cc=crossgcc@sourceware.org \
/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).