All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-11
Date: Thu, 14 Feb 2013 22:49:38 +0100	[thread overview]
Message-ID: <511D5BF2.5060906@mind.be> (raw)
In-Reply-To: <20130212073431.F3A9752C982@lolut.humanoidz.org>

On 12/02/13 08:34, Thomas Petazzoni wrote:
> Build 4fedd1a67957f52272b63948e766d7ad10bf4f85
> ==============================================
> 
> Status         : NOK
> Failure reason : pv-1.2.0
> Architecture   : x86_64
> Submitted by   : Thomas Petazzoni (Free Electrons build server)
> Submitted at   : 2013-02-11 07:01:56
> Git commit ID  :http://git.buildroot.net/buildroot/commit/?id=6056de8971bf25c9853c38583dc50b5abcb982de
> End of log     :http://autobuild.buildroot.net/results/4fedd1a67957f52272b63948e766d7ad10bf4f85/build-end.log
> Complete log   :http://autobuild.buildroot.net/results/4fedd1a67957f52272b63948e766d7ad10bf4f85/build.log.bz2
> Configuration  :http://autobuild.buildroot.net/results/4fedd1a67957f52272b63948e766d7ad10bf4f85/config
> Defconfig      :http://autobuild.buildroot.net/results/4fedd1a67957f52272b63948e766d7ad10bf4f85/defconfig


 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?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-02-14 21:49 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 [this message]
2013-02-15  4:57   ` Thomas Petazzoni

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=511D5BF2.5060906@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.