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] New package util-linux-ng
Date: Tue, 12 Aug 2008 17:55:57 +0200	[thread overview]
Message-ID: <20080812155557.GA3571@mx.loc> (raw)
In-Reply-To: <20080812154103.GA20961@cbg.dyndns.org>

On Tue, Aug 12, 2008 at 05:41:03PM +0200, Steffen Schulz wrote:
>On 080812 at 10:00, Bernhard Fischer wrote:
>> On Mon, Aug 11, 2008 at 07:01:57PM +0200, Steffen Schulz wrote:
>> >On 080810 at 07:27, Steffen Schulz wrote:
>> >> - util-linux still wants to compile even though it was not selected and
>> >>   removed from Config.in
>> >> - with util-linux-ng.mk, the are no errors, the package is simply ignored
>> >
>> >Maybe I should have phrased that more like a question. I have a similar
>> >problem now with a strongSwan package I need in buildroot.
>> >
>> >I created a .mk that uses makefile.autotools.in. I select the new
>> >packet in menuconfig and type make, but the package is simply ignored.
>> 
>> Make sure to run 'make oldconfig' or menuconfig so the package shows up
>> in .config ?
>
>I did a menuconfig and selected the packages. And indeed .config says:
>
>BR2_PACKAGE_strongSwan=y
>BR2_PACKAGE_UTIL-LINUX-NG=y

Alright, that'd be it.
First, package names are supposed to be in caps and
second, i don't think '-' will do any good, use '_' instead.

  reply	other threads:[~2008-08-12 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10  5:06 [Buildroot] New package util-linux-ng Steffen Schulz
2008-08-11 17:01 ` Steffen Schulz
2008-08-12  7:44   ` Bernhard Fischer
2008-08-12 15:41     ` Steffen Schulz
2008-08-12 15:55       ` Bernhard Fischer [this message]
2008-08-24  8:54 ` Peter Korsgaard
2008-08-25 17:40   ` Steffen Schulz

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=20080812155557.GA3571@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