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 11016] Wrong compiler used for external user host packages
Date: Tue, 15 May 2018 20:58:18 +0000	[thread overview]
Message-ID: <bug-11016-163-HfFm3uLwzE@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11016-163@https.bugs.busybox.net/>

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

Arnout Vandecappelle <arnout@mind.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #2 from Arnout Vandecappelle <arnout@mind.be> ---
Buildroot does not build its own native compiler (i.e. the compiler used to
build host-packages). We don't plan to do so. It would increase the complexity
significantly.

Instead, Buildroot can exclude packages that require a recent native compiler,
using the symbols BR2_HOST_GCC_AT_LEAST_X_Y. So in your case, you could add
'depends on BR2_HOST_GCC_AT_LEAST_5' to the Config.in of
amstParseSharedLibraries. Clearly, that doesn't solve your problem because you
simply will not be able to build your packages.

However, you can fairly easily build gcc7 yourself and install it somewhere in
your PATH.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2018-05-15 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  8:02 [Buildroot] [Bug 11016] New: Wrong compiler used for external user host packages bugzilla at busybox.net
2018-05-14  8:03 ` [Buildroot] [Bug 11016] " bugzilla at busybox.net
2018-05-14  8:19 ` bugzilla at busybox.net
2018-05-15 20:58 ` bugzilla at busybox.net [this message]

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-11016-163-HfFm3uLwzE@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