All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Error installing  udev  : frugalware ??
Date: Thu, 12 Jan 2012 10:50:39 +0100	[thread overview]
Message-ID: <87aa5t8d1s.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <8E8EC4AEBD4345D2BF6FE26E33A7874A@JohanW7> (Sagaert Johan's message of "Thu, 12 Jan 2012 10:43:38 +0100")

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

 Sagaert> So I had topdir/package/......
 Sagaert>                        |udev  (173) 
 Sagaert> 				|udevold (114)
 Sagaert> 				|.....

 Sagaert> So it seems the buildroot scripts are scanning the package directory and seems to act on it even if it is not included in the
 Sagaert> package/Config.in.

Yes, *.mk files are included using a wildcard:

include package/*/*.mk

 Sagaert> Strange, because I did not see anything suspected in the build output.

 Sagaert> So I started grep to find out where the frugalware text came from...

 Sagaert> Why is the package directory scanned ?

Because it's the simplest possible implementation. For the Config.in
files we want a specific order in menuconfig (and mconf doesn't support
wildcards), but make does.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-01-12  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 23:32 [Buildroot] Error installing udev : frugalware ?? Sagaert Johan
2012-01-12  8:10 ` Peter Korsgaard
2012-01-12  9:43   ` Sagaert Johan
2012-01-12  9:50     ` Peter Korsgaard [this message]
2012-01-12  9:52     ` Thomas Petazzoni

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=87aa5t8d1s.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.