From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Error compiling arm-elf-gcc-4.5.0
Date: Tue, 20 Apr 2010 16:37:00 -0000 [thread overview]
Message-ID: <4BCDB8FD.4050206@wippies.com> (raw)
In-Reply-To: <1271753344.7037.15.camel@lab7.powersoft.it>
20.4.2010 11:49, Massimiliano Cialdi kirjoitti:
> I have configured as follows:
> configure --enable-languages=c,c++ --target=arm-elf --with-gnu-as
> --with-gnu-ld --prefix=path-to/arm-elf-gcc-4.5.0
The given $prefix should be some 'absolute' pathname, the default is
'/usr/local' when no '--prefix=$prefix' is given. Yours is 'relative'
to some directory.
> when I make all I get the following error:
>
> Links are now set up to build a cross-compiler
> from x86_64-unknown-linux-gnu to arm-unknown-elf.
> checking for exported symbols...
> path-to/arm-elf-gcc-4.5.0/arm-elf/bin/objdump: conftest: File format not
> recognized
> checking for -rdynamic... path-to/arm-elf-gcc-4.5.0/arm-elf/bin/objdump:
> conftest: File format not recognized
Hard to say what is the search root for these, probably the main $BUILD
directory. In any case there seems to be nothing which the configure
script expects, here an 'objdump' for the 'arm-elf' target...
> my system is ubuntu 9.10 64 bit with
> gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9)
>
> binutils:
> GNU ld (GNU Binutils for Ubuntu) 2.20
Of course you should first have binutils for 'arm-elf' in the
'$prefix/bin' (for humans and this dir in PATH) and in
'$prefix/arm-elf/bin' (for the GCC to be built). The
'path-to/arm-elf-gcc-4.5.0/arm-elf/bin/objdump' shows this
scheme with your given $prefix and $target values.
next prev parent reply other threads:[~2010-04-20 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 15:23 Massimiliano Cialdi
2010-04-20 16:37 ` Kai Ruottu [this message]
2010-04-21 7:17 ` Massimiliano Cialdi
2010-04-21 13:21 ` Kai Ruottu
2010-04-21 13:44 ` Massimiliano Cialdi
2010-04-21 14:52 ` Kai Ruottu
2010-04-22 13:55 ` Kai Ruottu
[not found] ` <BLU124-W8C43C3FDBE76D44D97CBDC2080@phx.gbl>
2010-04-23 17:31 ` Kai Ruottu
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=4BCDB8FD.4050206@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gcc.gnu.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).