From: eMartian <research@microcoding.info>
To: crossgcc@sourceware.org
Subject: Fail to build gcc with target=arm-elf
Date: Fri, 09 Aug 2013 04:09:00 -0000 [thread overview]
Message-ID: <1376021344515-240634.post@n7.nabble.com> (raw)
Hi,
I build binutils-2.23.2, gcc-4.8.1, newlib-2.0.0 in Cygwin:
1. Full install cygwin.
2. Run cygwin.
3. CC="gcc -B/usr/bin"
4. /src/binutils-2.23.2/configure --target=arm-elf
--prefix=/gnutools/arm-elf --enable-interwork \
--enable-multilib -v 2>&1 | tee configure.out
5. make -w all install 2>&1 | tee make.out
6. PATH=/gnutools/arm-elf/bin:$PATH; export PATH
7. /src/gcc-4.8.1/configure --target=arm-elf --prefix=/gnutools/arm-elf
--enable-languages="c,c++" \
--enable-interwork --enable-multilib --with-gnu-as --with-gnu-ld
--with-newlib \
--with-headers=/src/newlib-2.0.0/newlib/libc/include -v 2>&1 | tee
config.out
8. make -w all-gcc install-gcc LANGUAGES= 2>&1 | tee make.out
It stoped and displayed:
checking for clock_t... yes
checking for F_SETLKW... yes
checking if mkdir takes one argument... no
*** Configuration arm-unknown-elf not supported
Makefile:3860: recipe for target `configure-gcc' failed
make: *** [configure-gcc] Error 1
I don't know what's wrong and how to resolve it. If I use --target=i386-elf
or arm-eabi, I can build the toolchain. But why arm-elf can't?
Best regardes
eMartian
--
View this message in context: http://sourceware-org.1504.n7.nabble.com/Fail-to-build-gcc-with-target-arm-elf-tp240634.html
Sent from the Sourceware - crossgcc list mailing list archive at Nabble.com.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2013-08-09 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 4:09 eMartian [this message]
2013-08-19 9:55 ` Richard Earnshaw
2013-08-19 11:07 ` eMartian
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=1376021344515-240634.post@n7.nabble.com \
--to=research@microcoding.info \
--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).