From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: package toolchain toolchain/gcc toolchai etc...
Date: Mon, 29 Jan 2007 17:41:14 -0700 [thread overview]
Message-ID: <20070130004114.GA14588@codepoet.org> (raw)
In-Reply-To: <20070121125852.7783048587@busybox.net>
On Sun Jan 21, 2007 at 04:58:52AM -0800, aldot at uclibc.org wrote:
> Author: aldot
> Date: 2007-01-21 04:58:51 -0800 (Sun, 21 Jan 2007)
> New Revision: 17433
>
> Log:
> - provide means to "install uClibc headers in the target filesystem" without a native compiler
>
>
> Added:
> trunk/buildroot/toolchain/uClibc/Config.in.2
> trunk/buildroot/toolchain/uClibc/Makefile.in
>
> Modified:
> trunk/buildroot/package/Config.in
> trunk/buildroot/toolchain/Makefile.in
> trunk/buildroot/toolchain/gcc/Config.in.2
> trunk/buildroot/toolchain/uClibc/uclibc.mk
I do not understand this change... 'make install_headers' is
only available in the latest uClibc snapshots, thus this fails on
uClibc 0.9.28 and 0.9.28.1. But this also redundant as uClibc's
'make install_dev' is called by the buildroot 'uclibc_target'
target regardless, and thus you get uClibc headers in the target
whether or not BR2_PACKAGE_UCLIBC_TARGET_HEADERS happens to be
set. Thus this option is currently useless and breaks the build
for older uClibc versions.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2007-01-30 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 12:58 [Buildroot] svn commit: trunk/buildroot: package toolchain toolchain/gcc toolchai etc aldot at uclibc.org
2007-01-30 0:41 ` Erik Andersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 10:10 aldot at uclibc.org
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=20070130004114.GA14588@codepoet.org \
--to=andersen@codepoet.org \
--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.