From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question on UCLIBC_CONFIG_FILE usage.
Date: Sat, 5 May 2007 12:07:54 +0200 [thread overview]
Message-ID: <20070505100754.GD8387@aon.at> (raw)
In-Reply-To: <463BF58C.6010602@realitydiluted.com>
On Fri, May 04, 2007 at 10:10:04PM -0500, Steven J. Hill wrote:
>I am obviously missing something here. If I do not specify UCLIBC_CONFIG_FILE
>on the command line to make, then a config file in 'toolchain/uClibc' will be
>used. None of the values assigned to it in the target directories will ever
>be picked up because the top-level Makefile does 'include target/Makefile.in'
>last which is too late for 'toolchain/uClibc/uclibc.mk' to pick up the value
>in a target-specific directory. Anyone care to comment? Thanks.
Since uclibc.mk has the config-file as a prerequisite (which is fine by
itself) it is evaluated right at that spot (to nil, if not specified on
the command-line).
Can't look right now, but perhaps including target/Makefile.in before
toolchain/Makefile.in in the toplevel Makefile would make it behave like
expected?
Perhaps we should store BR2_UCLIBC_CONFIG_FILE in .config, too.
prev parent reply other threads:[~2007-05-05 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 3:10 [Buildroot] Question on UCLIBC_CONFIG_FILE usage Steven J. Hill
2007-05-05 10:07 ` Bernhard Fischer [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=20070505100754.GD8387@aon.at \
--to=rep.dot.nop@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.