From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error while making buildroot for an i386 architecture
Date: Mon, 3 Sep 2007 16:20:49 +0200 [thread overview]
Message-ID: <002c01c7ee36$f90ea640$0402a8c0@atmel.com> (raw)
In-Reply-To: 1188828402.6167.8.camel@PcNacho
Subject: [Buildroot] Error while making buildroot for an i386 architecture
> Hi! my name is Nacho and this is my first e-mail to the list,
> I'm trying to create a filesystem with buildroot and my target
> is an ATX
> board.
> I follow the instructions for producing the filesystem in the
> documentation:
> make menuconfig and later on make.
> I chose the default toolchain and no packages on the busybox
> part of the
> menuconfig just to check if the output is what I need.
> I get the following error during the make command:
>
> # Strip the host binaries
> strip --strip-all -R .note
> -R .comment /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-addr2line /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-ar /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-as /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-c++filt /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-cpp /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gcc /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gcc-4.2.1 /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gccbug /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gcov /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-ld /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-ldconfig /home/nacho/Desktop/buildroot/buil!
> d_i386/staging_dir/usr/bin/i386-linux-uclibc-ldd /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-nm /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-objcopy /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-objdump /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-ranlib /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-readelf /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-size /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-strings /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-strip
> strip: /home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gccbug: File format not recognized
> make: ***
> [/home/nacho/Desktop/buildroot/toolchain_build_i386/gcc-4.2.1-final/.installed] Error 1
>
>
> I have no idea of what's the problem because the toolchain is in
> it's
> directory so it means that it's been succesfully downloaded and
> compiled, isn't it?.
>
> I'd thank some help from anybody in the list.
>
> Best Regards,
>
> Nacho
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
It is a bug in buildroot, which we are tryuing to fix right now.
/home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gccbug
is not an executable binary, it is a script file and thus cannot be "stripped"
rename manually
/home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gccbug
to
/home/nacho/Desktop/buildroot/build_i386/staging_dir/usr/bin/gccbug
and retry
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-09-03 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 14:06 [Buildroot] Error while making buildroot for an i386 architecture Ignacio Lorenzo Subirá Otal
2007-09-03 14:20 ` Ulf Samuelsson [this message]
2007-09-04 11:46 ` 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='002c01c7ee36$f90ea640$0402a8c0@atmel.com' \
--to=ulf@atmel.com \
--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