Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch pre-built-packages
Date: Sat, 29 Dec 2012 17:14:47 +0100	[thread overview]
Message-ID: <cover.1356797653.git.thomas.petazzoni@free-electrons.com> (raw)

Hello,

Recently, we have had a number of users having issues with external
toolchains because those are built for 32 bits Linux, and most
developers know use 64 bits build machines. The error message such
users get so far is very cryptic "Cannot execute cross-compiler".

So, this set of patches adds a small infrastructure in the form of a
Kconfig option and a check in dependencies.sh. The Kconfig option
allows packages to tell whether they need 32 bits compatibility
libraries, and the check in dependencies.sh verifies that those
libraries are installed (simply by checking the presence of the 32
bits dynamic loader).

Then, all pre-built external toolchains as well as the sam-ba tool are
modified to use this mechanism.

As a preliminary patch, all the pre-built external toolchains are
changed to be visible only if the host architecture is x86 or x86-64.

Thanks,

Thomas

The following changes since commit 4848386446b937d4d0d9d3e9489932ca3fcb1003:

  libffi: fix mips build failures (2012-12-28 16:55:09 +0100)

are available in the git repository at:

  git://git.free-electrons.com/users/thomas-petazzoni/buildroot.git pre-built-packages

for you to fetch changes up to fbccee70c941bfc2e0c8d0c62cf78e726ae35170:

  sam-ba: select BR2_HOSTARCH_NEEDS_IA32_LIBS (2012-12-29 17:06:41 +0100)

----------------------------------------------------------------
Thomas Petazzoni (4):
      toolchain-external: add dependency on BR2_HOST_ARCH
      Infrastructure to warn the user about missing 32 bits libraries
      toolchain-external: use BR2_HOSTARCH_NEEDS_IA32_LIBS where needed
      sam-ba: select BR2_HOSTARCH_NEEDS_IA32_LIBS

 Config.in                              |    6 ++++
 package/sam-ba/Config.in.host          |    1 +
 support/dependencies/dependencies.sh   |   11 +++++++
 toolchain/toolchain-external/Config.in |   54 ++++++++++++++++++++++++++++++++
 4 files changed, 72 insertions(+)

Thanks,
-- 
Thomas Petazzoni

             reply	other threads:[~2012-12-29 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-29 16:14 Thomas Petazzoni [this message]
2012-12-29 16:14 ` [Buildroot] [PATCH 1/4] toolchain-external: add dependency on BR2_HOST_ARCH Thomas Petazzoni
2012-12-29 16:14 ` [Buildroot] [PATCH 2/4] Infrastructure to warn the user about missing 32 bits libraries Thomas Petazzoni
2013-01-07  7:55   ` Arnout Vandecappelle
2012-12-29 16:14 ` [Buildroot] [PATCH 3/4] toolchain-external: use BR2_HOSTARCH_NEEDS_IA32_LIBS where needed Thomas Petazzoni
2012-12-29 16:14 ` [Buildroot] [PATCH 4/4] sam-ba: select BR2_HOSTARCH_NEEDS_IA32_LIBS Thomas Petazzoni
2013-01-06 15:43 ` [Buildroot] [pull request] Pull request for branch pre-built-packages Thomas Petazzoni
2013-01-06 20:43 ` Peter Korsgaard

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=cover.1356797653.git.thomas.petazzoni@free-electrons.com \
    --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