From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001410]: uclibc.mk produces .config that confuses uclibc's configuration system
Date: Fri, 29 Jun 2007 04:18:21 -0700 [thread overview]
Message-ID: <d4e547cc265b99a2f4e744ca6187e362@bugs.busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1410
======================================================================
Reported By: bjdooks
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1410
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 06-29-2007 04:18 PDT
Last Modified: 06-29-2007 04:18 PDT
======================================================================
Summary: uclibc.mk produces .config that confuses uclibc's
configuration system
Description:
If building for ARM, and providing an configuration from a file in a target
sub-directory, the uclibc.mk file incorrectly re-writes the .config for
building uclibc, causing warnings and an incorrect .config
The problem stems from unsetting CONFIG_<x> options, then re-specifying
them as CONFIG_<x>=y later in the file. The current configuration system
(make oldconfig) seems to take the first occurence as the proper setting.
This means that options that should be set end up being unset as 'make
oldconfig' removes any further refrences to CONFIG_<x> from the file.
For example, if you specify the buildroot config as CONFIG_ARM920T=y, then
the uclibc.mk removes that turning it into # CONFIG_ARM920T is unset and
then adds CONFIG_ARM920T=y to the end of the file. Then 'make oldconfig'
is run, and CONFIG_ARM920T=y is deleted, thus causing CONFIG_GENERIC_ARM=y
to be placed in the config file.
The warnings produced by 'make oldconfig' are:
config:209:warning: trying to reassign symbol CONFIG_ARM920T
.config:210:warning: trying to reassign symbol CONFIG_ARM_OABI
.config:211:warning: trying to reassign symbol CONFIG_ARM_EABI
Also note, that the EABI/OABI are also being warned about, so are
also fixed.
The simple fix is to change the sed expressions unsetting these options to
simply deleting them from the file.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-29-07 04:18 bjdooks New Issue
06-29-07 04:18 bjdooks Status new => assigned
06-29-07 04:18 bjdooks Assigned To => buildroot
06-29-07 04:18 bjdooks File Added: uclibc-arm-config.patch
======================================================================
next reply other threads:[~2007-06-29 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 11:18 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-29 11:20 [Buildroot] [buildroot 0001410]: uclibc.mk produces .config that confuses uclibc's configuration system bugs at busybox.net
2007-07-08 0:33 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=d4e547cc265b99a2f4e744ca6187e362@bugs.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