From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-11
Date: Fri, 15 Feb 2013 05:57:42 +0100 [thread overview]
Message-ID: <20130215055742.4402d9ee@skate> (raw)
In-Reply-To: <511D5BF2.5060906@mind.be>
Dear Arnout Vandecappelle,
On Thu, 14 Feb 2013 22:49:38 +0100, Arnout Vandecappelle wrote:
> The problem with this one is the following:
>
> /home/test/test/output1/host/usr/bin/i686-pc-linux-gnu-ld -r -o src/library.o src/library/getopt.o src/library/gettext.o
> /home/test/test/output1/host/usr/bin/i686-pc-linux-gnu-ld: i386:x86-64 architecture of input file `src/library/gettext.o' is incompatible with i386 output
>
>
> This is because the Sourcery toolchain is a multilib toolchain that can
> generate two different emulations (elf_i386 and elf_x86_64). gcc adds the
> "-m elf_x86_64" option to ld, but of course there is no way for configure
> or whatever to discover that this is necessary.
>
> There are probably other packages that suffer the same problem - in fact,
> any package that uses $(TARGET_LD) will most likely suffer from it.
>
> I'm not sure how to solve this. We could set TARGET_LD to
> "$(TARGET_CROSS)ld -m elf_x86_64" for the specific case of x86_64 external
> toolchains (it probably doesn't hurt to add the default emulation
> explicitly). But there may be other external toolchains with the same
> problem - none of the current ones, at first sight, but who knows what the
> future brings.
>
> So what do you think?
We discussed this during the Buildroot Developers meeting, don't you
remember ? :-)
From your report:
Flags in external toolchain wrapper. The source of this discussion
is the Cavium toolchain which requires an additional linker option
to link correctly. Note that this is only about compile/link flags
that are strictly needed for compiling for the right target, so
typically things like -mfpu. The conclusion is that we want:
[...]
Just like the Cavium toolchain required a special -m flag at link time,
the Sourcery toolchain also needs a -m flag at link time.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-02-15 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 7:34 [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-11 Thomas Petazzoni
2013-02-14 21:49 ` Arnout Vandecappelle
2013-02-15 4:57 ` Thomas Petazzoni [this message]
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=20130215055742.4402d9ee@skate \
--to=thomas.petazzoni@free-electrons.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