All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] build problems
Date: Wed, 26 Mar 2008 18:17:51 +0100	[thread overview]
Message-ID: <20080326171751.GH29267@mx.loc> (raw)
In-Reply-To: <87ve39buzq.fsf@macbook.be.48ers.dk>

On Wed, Mar 26, 2008 at 12:11:21PM +0100, Peter Korsgaard wrote:
>>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>
>Hi,
>
> >> Also, when I run it right now and try to do a "make configured", I get
> >> an error because it can't copy busybox-1.9.2.config. It looks like
> >> busybox has been updated, but a new config file has not been put into
> >> the target/device/atmel/at91sam9260dfc directory. So do I rename the
> >> busybox-1.9.1.config file to busybox-1.9.2.config? 
>
> Ulf> I think this will work.
> Ulf> The problem is that people updating the busybox support,
> Ulf> disables the use of older busybox, which will force the 
> Ulf> saved config to update the version.
> Ulf> I am not sure that this is a good idea.
>
>I'll be the first to admit to not knowing anything about that 11MB
>blob under target/device/Atmel  - Why make it so fragile to begin with?
>
>By now all the avr/atmel stuff takes up around half the buildroot size
>- I don't have access to any of that hardware, so I won't test it.
>
>I see that the directory only has a busybox config for 1.6.1 and
>1.9.1, so it's broken anyway if the user selects anything else than
>that.
>
>To me it doesn't make sense to keep earlier versions than the latest
>stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)
>- Otherwise it'll get too hard to handle. I think it's also soon time
>to retire some of the really ancient versions like 1.2.x - 1.6.x.

hehe, sounds familiar. I've already had my share of fun with Ulf in
exactly this area and consequently there is that git-repo which fixes
alot of this stuff for good.

cheers,

  reply	other threads:[~2008-03-26 17:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 21:43 [Buildroot] build problems Tim Barr
2008-03-25 22:41 ` Ulf Samuelsson
2008-03-26 11:11   ` Peter Korsgaard
2008-03-26 17:17     ` Bernhard Fischer [this message]
2008-03-26 22:39       ` Peter Korsgaard
2008-03-27 11:24         ` Bernhard Fischer
2008-03-26 21:15     ` Ulf Samuelsson
2008-03-26 21:34       ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2008-03-26 16:09 Tim Barr
2008-03-26 12:59 Tim Barr
2008-03-26 20:50 ` Ulf Samuelsson
2008-03-25  2:37 Steve Calfee
2008-03-24 12:45 Tim Barr
2008-03-24 12:52 ` John Voltz
2008-03-24 21:12 ` Lucian Lazarescu
2008-03-25 10:08 ` Ulf Samuelsson
2008-03-23 15:51 Steve Calfee
2008-03-25 10:10 ` Ulf Samuelsson
2008-03-05  1:33 Steve Calfee
2008-03-05  9:20 ` Ulf Samuelsson
2008-03-04 22:19 Steve Calfee

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=20080326171751.GH29267@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.