Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] Supply better default uClibc config file when using ct-ng
Date: Tue, 06 Dec 2011 12:19:28 +0000	[thread overview]
Message-ID: <4EDE0850.10502@carallon.com> (raw)
In-Reply-To: <5b4fbca78f7b4e45fa487a81d96270a5@zacarias.com.ar>

On 06/12/2011 00:44, Gustavo Zacarias wrote:
> On 05.12.2011 18:33, Yann E. MORIN wrote:
>
>> Will and Gustavo, please coordinate with each other:
>>
>> - Will wants to reference that file to commonalise the uClibc
>> configuration
>> files between the internal backend and the crosstool-NG backend, see:
>> http://lists.busybox.net/pipermail/buildroot/2011-December/048123.html
>>
>> - Gustavo wants to remove the file because the internal toolchain backend
>> is dropping support for uClibc-0.9.30; see:
>> http://lists.busybox.net/pipermail/buildroot/2011-December/048099.html
>>
>> I am not sure what the proper resolution could be. Surely enough, I think
>> what Will wants to do is the correct way: use a single (set of) files for
>> both backends. Also, the internal backend should not be impacted by some
>> requirements of the ct-ng backend.
>>
>> Anyway, in the meantime, because Gustavo's patch is not yet applied...
>> Will, you can add my:
>> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
>>
>> Regards,
>> Yann E. MORIN.
>
> It's quite simple actually, if we support any form of uClibc 0.9.30.x
> there are packages which won't build unless functionality backporting is
> done.
> For example udev needs needs 99c1547124d7f410a3e3db66aa5816e53a96c156
> for 0.9.31 (and would so for 0.9.30.x)
> Any takers for undeprecating and testing a ton of packages against
> 0.9.30.x?
> Maybe the backporting is there for ct-ng toolchains?
> Regards.
>

I had not noticed that 0.9.30 was marked as deprecated, added that to ct-ng.

Not sure we need to rush to remove 0.9.30 as it is already marked 
deprecated, but when we do remove it I guess we should remove from ct-ng 
toolchains as well.

Will


-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2011-12-06 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 18:08 [Buildroot] [PATCH 0/4] Improved uClibc support with ct-ng generated toolchain Will Wagner
2011-12-05 18:08 ` [Buildroot] [PATCH 1/4] Allow user to pick uClibc version when using ct-ng Will Wagner
2011-12-05 21:24   ` Yann E. MORIN
2011-12-05 18:08 ` [Buildroot] [PATCH 2/4] Supply better default uClibc config file " Will Wagner
2011-12-05 21:33   ` Yann E. MORIN
2011-12-06  0:44     ` Gustavo Zacarias
2011-12-06 12:19       ` Will Wagner [this message]
2011-12-06 12:27         ` Gustavo Zacarias
2011-12-05 18:08 ` [Buildroot] [PATCH 3/4] Allow user to specify a custom " Will Wagner
2011-12-05 21:38   ` Yann E. MORIN
2011-12-05 18:08 ` [Buildroot] [PATCH 4/4] Allow user to select nptl when using 0.9.32 with ct-ng Will Wagner
2011-12-05 21:40   ` Yann E. MORIN

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=4EDE0850.10502@carallon.com \
    --to=will_wagner@carallon.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