From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000782]: Config path for uClibc not included in uClibc makefile
Date: Mon, 12 Feb 2007 05:43:33 -0800 [thread overview]
Message-ID: <c43638bf63ebc0bc02f364dab5683e50@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=782
======================================================================
Reported By: maroc
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 782
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 03-10-2006 16:39 PST
Last Modified: 02-12-2007 05:43 PST
======================================================================
Summary: Config path for uClibc not included in uClibc
makefile
Description:
In the buildroot config, if you specify the path to the uClibc config, this
config is not included when compiling uClibc. The make file for uClibc in
toolchain/uClibc contains the statement:
ifndef $(UCLIBC_CONFIG_FILE)
but the config option for the uClibc config path is named:
BR2_PACKAGE_UCLIBC_CONFIG
so the config file specifed in the buildroot config is not used.
======================================================================
----------------------------------------------------------------------
maroc - 03-16-06 13:35
----------------------------------------------------------------------
Looking at the make file for busybox, I see a line like
BUSYBOX_CONFIG_FILE=$(subst ",, $(strip $(BR2_PACKAGE_BUSYBOX_CONFIG)))
where the busybox config is set from the buildroot config option.
Maybe the uclibc make file needs a similar statement to get the path for
the uclibc config? e.g.
UCLIBC_CONFIG_FILE=$(subst ",, $(strip $(BR2_PACKAGE_UCLIBC_CONFIG)))
----------------------------------------------------------------------
bernhardf - 12-22-06 04:15
----------------------------------------------------------------------
AFAICS there is no BR2_PACKAGE_UCLIBC_CONFIG anymore.
If you want to use a pre-configured .config for uClibc, then
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config
See docs/README.
Issue History
Date Modified Username Field Change
======================================================================
03-10-06 16:39 maroc New Issue
03-10-06 16:39 maroc Status new => assigned
03-10-06 16:39 maroc Assigned To => uClibc
03-16-06 13:35 maroc Note Added: 0001186
12-22-06 04:15 bernhardf Status assigned => closed
12-22-06 04:15 bernhardf Note Added: 0001912
12-22-06 04:15 bernhardf Resolution open => fixed
02-12-07 05:43 vapier Status closed => assigned
02-12-07 05:43 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c43638bf63ebc0bc02f364dab5683e50@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