From: Steven J. Hill <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question on UCLIBC_CONFIG_FILE usage.
Date: Fri, 04 May 2007 22:10:04 -0500 [thread overview]
Message-ID: <463BF58C.6010602@realitydiluted.com> (raw)
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.
-Steve
next reply other threads:[~2007-05-05 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 3:10 Steven J. Hill [this message]
2007-05-05 10:07 ` [Buildroot] Question on UCLIBC_CONFIG_FILE usage Bernhard Fischer
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=463BF58C.6010602@realitydiluted.com \
--to=sjhill@realitydiluted.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox