Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rafael A Barrero <rafa@linux.it>
To: buildroot@busybox.net
Subject: [Buildroot] new DHCP version and make error
Date: Wed, 29 Nov 2006 02:13:11 +0100 (CET)	[thread overview]
Message-ID: <49328.206.190.75.8.1164762791.squirrel@picard.linux.it> (raw)
In-Reply-To: <1164758347.4016.24.camel@dv>

Hi;

I agree that buildroot should take step forward in this direction. A
"distribution building system" should be able to maintain a stable process
for creating these distributions, no?

I for example have just begun to work with buildroot and I'm coming across
missing software distributions or software distributions that simply do
not compile.

For example - gettext-0.14.6 does not compile... what do you guys suggest?
Do I remove it from my list? Use an alternate version? Fix the bug?

Does anyone have a known-good list somewhere (for x86 targets)? What
versions allow buildroot to compile cleanly? Completely?

I certainly don't mind pitching a hand... I've got some spare systems and
could put together a quick test matrix. Thoughts?

Thanks,

Rafael.

> On Tue, 2006-11-28 at 17:37 -0500, Marc Lindahl wrote:
>> On Nov 28, 2006, at 5:28 PM, Pavel Roskin wrote:
>> > I'd like to see buildroot become a distribution over time.
>>
>> I thought buildroot was a distribution building system, not an actual
>> distribution...
>
> OK, let's call it a distribution building system.  Once Buildroot 1 is
> released and the work starts on Buildroot 2, Buildroot 1 needs to remain
> functional for some time.
>
> It could be updated for security, but updating it just to reflect
> changes on the Web (such as new download locations) would be too much
> work.
>
> Of course, the task of mirroring could be relegated to the creators of
> the specific distributions, but I think the buildroot project shouldn't
> miss an opportunity to become more relevant to the embedded community.
>
> There are cases when stability of the platform is highly desirable.  If
> buildroot itself provides it, we'll see more people dealing with it
> directly rather than through distributions based on some old snapshot.
>
> --
> Regards,
> Pavel Roskin
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>

  reply	other threads:[~2006-11-29  1:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 20:27 [Buildroot] new DHCP version and make error Rafael A Barrero
2006-11-28 21:38 ` Rafael A Barrero
2006-11-28 22:28   ` Pavel Roskin
2006-11-28 22:37     ` Marc Lindahl
2006-11-28 23:59       ` Pavel Roskin
2006-11-29  1:13         ` Rafael A Barrero [this message]
2006-11-29  1:43           ` Pavel Roskin
2006-11-29  8:52 ` 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=49328.206.190.75.8.1164762791.squirrel@picard.linux.it \
    --to=rafa@linux.it \
    --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