Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] busybox: fix missing dependencies in	unpacked and config rules
Date: Wed, 6 Aug 2008 15:27:33 +0200	[thread overview]
Message-ID: <20080806132733.GA9020@mx.loc> (raw)
In-Reply-To: <87zlnq1eu3.fsf@macbook.be.48ers.dk>

On Wed, Aug 06, 2008 at 02:57:08PM +0200, Peter Korsgaard wrote:
>>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:
>
> Hans-Christian> This patch adds depedency to host-sed and
> Hans-Christian> $(PROJECT_BUILD_DIR) when running make busybox-config
> Hans-Christian> and busybox-unpacked.
>
>Thanks, committed as r23065.

Does that really work?

Please
$ chmod -x $(which sed)
on your build host, so that host-sed has to be actually be built (ISTR
that we rightfully use the busybox sed in this case)
then wipe your obj trees and
$ cp -a my_toplevel_config.BAK .config
$ make busybox-menuconfig

I think that if you had a pristine tree and copyied a backed-up
br2.config to the toplevel, that you could (previously) run all
menuconfig targets (with a disfunctional sed on your host).

  reply	other threads:[~2008-08-06 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  9:16 [Buildroot] [PATCH 1/1] busybox: fix missing dependencies in unpacked and config rules Hans-Christian Egtvedt
2008-08-06 12:57 ` Peter Korsgaard
2008-08-06 13:27   ` Bernhard Fischer [this message]
     [not found]   ` <7F3102E19F8147C3A4922F613D734799@aeglos>
2008-09-25 10:55     ` [Buildroot] [PATCH 1/1] busybox: fix missing dependencies inunpacked " Peter Korsgaard

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=20080806132733.GA9020@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox