From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Explicit dependencies on uclibc in makefiles
Date: Thu, 20 Aug 2009 10:52:41 +0200 [thread overview]
Message-ID: <20090820085241.GC22901@mx.loc> (raw)
In-Reply-To: <d6cda7730908130743ic7fa66fy5f32814fc828d887@mail.gmail.com>
On Thu, Aug 13, 2009 at 11:43:27AM -0300, Thiago A. Corr?a wrote:
>2009/8/13 Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>:
>> On Thu, 13 Aug 2009 15:19:48 +0100
>> Will Newton <will.newton@gmail.com> wrote:
>>
>> <snipp>
>>
>>> Why does bash depend on uclibc but grep doesn't? Does grep have a bug
>>> or can we remove the unneeded dependency from bash?
>>>
>>
>> IIRC uclibc is earlier in the dependency loop anyway, uclibc is in the
>> BASE_TARGETS list. See top level Makefile.
>>
>
>Ah, ok. I never looked it up at the top Makefile. Well, then I guess
>we could drop uclibc from all packages/*
indeed.
>This actually should be done for the glibc support to work properly I guess.
http://repo.or.cz/w/buildroot.git?a=commit;h=7a1e0eccede82028e176ee4671fe79b1a34c0779
http://repo.or.cz/w/buildroot.git?a=commit;h=567d5c24536c8462b6df24f6c7654a72b00f202d
http://repo.or.cz/w/buildroot.git?a=commit;h=ab606461d9033d8dca2dd698751308d9aa0c528f
http://repo.or.cz/w/buildroot.git?a=commit;h=31cb73c8370d65a2fde86415de59369dc433b02d
and related commits.
As previously stated, i invite anybody to bring your tree up to snuff
prev parent reply other threads:[~2009-08-20 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 15:55 [Buildroot] Explicit dependencies on uclibc in makefiles Will Newton
2009-08-13 14:05 ` Thiago A. Corrêa
2009-08-13 14:19 ` Will Newton
2009-08-13 14:37 ` Hans-Christian Egtvedt
2009-08-13 14:43 ` Thiago A. Corrêa
2009-08-13 19:02 ` Thomas Petazzoni
2009-08-20 8:52 ` Bernhard Reutner-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=20090820085241.GC22901@mx.loc \
--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.