Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 851] New: Add option to specify --sysroot value for external toolchain
Date: Fri,  8 Jan 2010 19:01:02 +0000 (UTC)	[thread overview]
Message-ID: <bug-851-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=851

           Summary: Add option to specify --sysroot value for external
                    toolchain
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: grant.b.edwards at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=887)
 --> (https://bugs.busybox.net/attachment.cgi?id=887)
Patch to allow use of relocated external toolchains that require a --sysroot
option

The current support for external toolchains assumes that the
external toolchain supports but does not require that a sysroot
value be passed when invoking the compiler, linker, etc.

This is inconvenient and overly restrictive for a couple
reasons:

  * You might want to be able to switch back and forth between
    different toolchains.  Building the toolchains with unique
    install paths is painful.

  * Developers want to be able to do development in "isolated"
    non-system directories without having to put the external
    toolchain in a global, hard-wired location -- a location
    that might be in use by a different project for a different
    version/flavor of the toolchain.

The attached patch adds a boolean config option that tells
buildroot that the external toolchain requires a sysroot value.
IOW, the the sysroot value reported by "gcc -v" is not correct.

It also adds a configuration variable that specifies the
correct sysroot value for the external toolchain. This value
defaults to an appropriate value for the already-specified
location of the sysroot toolchain.  In most cases, setting the
boolean BR2_TOOLCHAIN_EXTERNAL_NEEDS_SYSROOT will be
sufficient.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-01-08 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 19:01 bugzilla at busybox.net [this message]
2010-02-21 22:33 ` [Buildroot] [Bug 851] Add option to specify --sysroot value for external toolchain bugzilla at busybox.net
2010-04-04 16:03 ` bugzilla at busybox.net
2010-04-04 16:22 ` bugzilla at busybox.net
2010-04-04 16:46 ` bugzilla at busybox.net
2010-04-04 18:04 ` bugzilla at busybox.net
2010-04-04 19:02 ` bugzilla at busybox.net
2010-04-04 21:18 ` bugzilla at busybox.net
2010-04-04 22:03 ` bugzilla at busybox.net
2010-04-07  7:51 ` bugzilla at busybox.net
2010-04-12 22:58 ` bugzilla at busybox.net
2010-04-13  5:34 ` bugzilla at busybox.net
2010-04-13 15:33 ` bugzilla at busybox.net

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=bug-851-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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