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] [PATCH] ext-toolchain: Automatically set -m64 if the architecture is x86_64
Date: Mon, 23 Jan 2012 22:36:57 +0100	[thread overview]
Message-ID: <20120123223657.32c86e82@skate> (raw)
In-Reply-To: <1327169083-15538-1-git-send-email-arnout@mind.be>

Le Sat, 21 Jan 2012 19:04:43 +0100,
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> a ?crit :

> From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
> 
> Without the -m64, choosing the x86_64 architecture with a Sourcery
> external toolchain will result in a 32-bit rootfs.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
>  This patch comes on top of ThomasP's external toolchain updates
> http://free-electrons.com/~thomas/buildroot.git
> for-2012.02/ext-toolchain-updates (Without those updates, the
> Sourcery x86 toolchain simply doesn't work, because it creates 32-bit
> executables but the libc installed on the target is 64-bit.)
> 
>  Thomas, it would be great if you could add this patch to your branch.

Looks good. I'll integrate it in my branch and repost the whole branch
soon.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-01-23 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 18:04 [Buildroot] [PATCH] ext-toolchain: Automatically set -m64 if the architecture is x86_64 Arnout Vandecappelle
2012-01-23 21:36 ` Thomas Petazzoni [this message]
2012-03-05 10:12 ` Thomas Petazzoni
2012-03-13 21:55   ` Arnout Vandecappelle
2012-03-14 22:23     ` Thomas Petazzoni
2012-03-13 22:30   ` [Buildroot] [PATCHv2] " Arnout Vandecappelle
2012-03-14 22:25     ` Thomas Petazzoni
2012-03-14 23:01     ` Peter Korsgaard
2012-03-15  8:17       ` Arnout Vandecappelle
2012-03-15  9:44         ` 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=20120123223657.32c86e82@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