All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] converting util-linux-ng to autotargets
Date: Sun, 25 Jul 2010 21:47:55 +0200	[thread overview]
Message-ID: <4C4C94EB.8010105@gmx.net> (raw)

Hi mailinglsit,

I tried to update to a newer version util-linux. As proposed by Thomas 
Pettazonni I like to use the new autotargets infrastructure.

I searched the mailinglist archives and applied the pattern for 
converting to autotargets to util-linux-ng.mk

For a simple roundtrip my config looks like this:
#############################################################
UTIL-LINUX-NG_VERSION=2.17
UTIL-LINUX-NG_SITE=$(BR2_KERNEL_MIRROR)/linux/utils/util-linux-ng/v$(UTIL-LINUX-NG_VERSION)
   UTIL-LINUX-NG_SOURCE=util-linux-ng-$(UTIL-LINUX-NG_VERSION).tar.bz2
UTIL-LINUX-NG_CONF_OPT=--disable-use-tty-group
UTIL-LINUX-NG_DEPENDENCIES=

define UTIL-LINUX-NG_INSTALL_TARGET_CMDS
         $(INSTALL) -D $(@D)/usr/bin/chkdupexe 
$(TARGET_DIR)/usr/sbin/chkdupexe
/init.d/
endef

$(eval $(call AUTOTARGETS,package,util-linux-ng))


My br-config includes the util-linux-ng package:
ossy at debian-virtual:~/buildroot/buildroot-dev$ cat .config|grep 
UTIL-LINUX-NG
BR2_PACKAGE_UTIL-LINUX-NG=y


The packae isn't touched in any way. The output/build directory includes 
ALL other packages. But BR never tried to create a util-linux-ng 
directory. All other conversion-patches to autotarget only modifed the 
*mk files. Nothing more.

Where can I find a log or something else where br tried to include 
util-linux-ng but run over it (because of some silly typos etc.)?

Thanks for your help.

Regards,
Marcus

             reply	other threads:[~2010-07-25 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 19:47 Ossy [this message]
2010-07-26  6:29 ` [Buildroot] converting util-linux-ng to autotargets Thomas Petazzoni
2010-07-26 20:39   ` Ossy

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=4C4C94EB.8010105@gmx.net \
    --to=ossy1980@gmx.net \
    --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.