Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] sysroot
Date: Wed, 30 Dec 2015 16:48:56 +0100	[thread overview]
Message-ID: <5683FCE8.6000206@mind.be> (raw)
In-Reply-To: <CA+C+_XRofByfgd5oo5R1CZykm=vhsXQLD0ESODbkwxXwiTF9QA@mail.gmail.com>

On 29-12-15 04:10, Mathew Benson wrote:
> What is the best way to add 32 bit headers (i.e. gnu/stubs-32.h) to the sysroot
> directory on a 64 bit build?  I need to create a sysroot for some new code
> development and I'd rather use the correct files that buildroot would have
> pulled in if it was a 32 bit build, rather than piece together a sysroot manually.  

 Could you clarify what you intend to do? The sysroot we create for a 64-bit
build cannot be used for 32-bit binaries. The only exception is if you build a
completely standalone executable (i.e. not linked with libc). And that's such an
exceptional case that we don't support it.

 If you want to build 32-bit executables, create a 32-bit buildroot environment.

 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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-12-30 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29  3:10 [Buildroot] sysroot Mathew Benson
2015-12-30 15:48 ` Arnout Vandecappelle [this message]
2015-12-30 18:42   ` Mathew Benson
2015-12-30 22:40     ` Arnout Vandecappelle

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=5683FCE8.6000206@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox