From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001502]: BR2_TOOLCHAIN_SYSROOT should depend on BR2_GCC_VERSION_4_2_0 or higher
Date: Wed, 19 Sep 2007 10:33:26 -0700 [thread overview]
Message-ID: <710c64023f5a0286908255bc04dcdfca@busybox.net> (raw)
The following issue has been CLOSED
======================================================================
http://busybox.net/bugs/view.php?id=1502
======================================================================
Reported By: ikonst
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1502
Category: Other
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 09-19-2007 06:32 PDT
Last Modified: 09-19-2007 10:33 PDT
======================================================================
Summary: BR2_TOOLCHAIN_SYSROOT should depend on
BR2_GCC_VERSION_4_2_0 or higher
Description:
The sysroot feature is only available on gcc 4.2.0 and higher. Building it
with gcc 4.1.x will cause an error (as sysroot's help string already
specifies).
toolchain/gcc/Config.in should be changed. Preferably, the rule should be
changed from exclusive:
depends on !BR2_GCC_VERSION_3_3_5 ...
to inclusive:
depends on BR2_GCC_VERSION_4_2_0 || BR2_GCC_VERSION_4_2_1 ||
BR2_GCC_VERSION_4_3
======================================================================
----------------------------------------------------------------------
bernhardf - 09-19-07 07:00
----------------------------------------------------------------------
No, the !ancient is fine. I don't want to special-case working version but
special case deprecat, ancient, unsupported stuff, if anything.
If you select BR2_DEPRECATED, you're on your own anyway, at least in my
POV.
----------------------------------------------------------------------
ikonst - 09-19-07 07:23
----------------------------------------------------------------------
I'm okay with either way: we should just make sure than when a new 4.1.x
version comes out, it's also excluded.
(Personally, I've lost considerable time trying to figure out the problem
which occurs when you try to build gcc 4.1.x with sysroot, so I deem it
important to disallow it within the configuration.)
----------------------------------------------------------------------
bernhardf - 09-19-07 10:33
----------------------------------------------------------------------
fixed in r19894
Issue History
Date Modified Username Field Change
======================================================================
09-19-07 06:32 ikonst New Issue
09-19-07 06:32 ikonst Status new => assigned
09-19-07 06:32 ikonst Assigned To => buildroot
09-19-07 07:00 bernhardf Note Added: 0002752
09-19-07 07:23 ikonst Note Added: 0002762
09-19-07 10:33 bernhardf Status assigned => closed
09-19-07 10:33 bernhardf Note Added: 0002763
======================================================================
next reply other threads:[~2007-09-19 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 17:33 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-19 14:23 [Buildroot] [buildroot 0001502]: BR2_TOOLCHAIN_SYSROOT should depend on BR2_GCC_VERSION_4_2_0 or higher bugs at busybox.net
2007-09-19 14:00 bugs at busybox.net
2007-09-19 13:32 bugs 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=710c64023f5a0286908255bc04dcdfca@busybox.net \
--to=bugs@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