From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] error building arm toolchain with latest snapshot- error says missing system headers
Date: Wed, 25 Jul 2007 16:35:21 -0700 (PDT) [thread overview]
Message-ID: <11801829.post@talk.nabble.com> (raw)
In-Reply-To: <11778512.post@talk.nabble.com>
Hi All,
few more things to add.
After the 1st error when i try "make gcc" i get below error. Kindly help me
to solve this. all this started with latest buildroot snapshot
/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0-initial/./gcc/xgcc
-B/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0-initial/./gcc/
-B/home/guru/project/original/toolchains/buildroot/build_arm/staging_dir/usr/arm-linux-uclibcgnueabi/bin/
-B/home/guru/project/original/toolchains/buildroot/build_arm/staging_dir/usr/arm-linux-uclibcgnueabi/lib/
-isystem
/home/guru/project/original/toolchains/buildroot/build_arm/staging_dir/usr/arm-linux-uclibcgnueabi/include
-isystem
/home/guru/project/original/toolchains/buildroot/build_arm/staging_dir/usr/arm-linux-uclibcgnueabi/sys-include
-O2 -g -Os -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem
./include -I. -I.
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0/gcc
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0/gcc/.
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0/gcc/../include
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0/gcc/../libcpp/include
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gmp/include
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/mpfr/include
-I/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0/gcc/../libdecnumber
-I../libdecnumber -g0 -finhibit-size-directive -fno-inline-functions
-fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder \
-c
/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0/gcc/crtstuff.c
-DCRT_BEGIN \
-o crtbegin.o
/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0-initial/./gcc/as:
line 2: exec: -m: invalid option
exec: usage: exec [-cl] [-a name] file [redirection ...]
make[2]: *** [crtbegin.o] Error 1
make[2]: Leaving directory
`/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0-initial/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory
`/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0-initial'
make: ***
[/home/guru/project/original/toolchains/buildroot/toolchain_build_arm/gcc-4.2.0-initial/.compiled]
Error 2
Regards
Gururaja
--
View this message in context: http://www.nabble.com/error-building-arm-toolchain-with-latest-snapshot--error-says-missing-system-headers-tf4140817.html#a11801829
Sent from the BuildRoot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-07-25 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 8:35 [Buildroot] error building arm toolchain with latest snapshot- error says missing system headers Hebbar
2007-07-25 23:35 ` Hebbar [this message]
2007-07-27 16:17 ` Bernhard Fischer
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=11801829.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--cc=buildroot@busybox.net \
/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