Skip to contentSkip to conversation

converting util-linux-ng to autotargets

Buildroot Ossy 2 participants 3 messages Jul 25, 2010 – Jul 26, 2010

lore
Share & tools
lore

Ossy

author
#0 lore 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

#1 lore raw
Quoted 4 lines · On Sun, 25 Jul 2010 21:47:55 +0200 Ossy <[email protected]> wrote:

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 configuration option should be BR2_PACKAGE_UTIL_LINUX_NG (with underscores), even if the package is named util-linux-ng.

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
author
#2 lore raw

Am 26.07.2010 08:29, schrieb Thomas Petazzoni:

Quoted 3 lines

The configuration option should be BR2_PACKAGE_UTIL_LINUX_NG (with underscores), even if the package is named util-linux-ng.

Yepp. That's it. The package begins to download and it compiles. I'll take the version from openwrt as guide and split the components into separated menu points.

Before the first successful run, I had to switch off the libtool patch, because only 4 out of 6 hunks were successfully applied. After the first run I found some binaries (32bit arm elf) in output/util-linux-ng-2.17/* and sometimes there was a placeholder script generated by libtool. The real binaries were placed in a .libs directory. Honestly, I'm not an expert, but why does libtool generate a wrapper script and for some other binaries not? What do I have to install to the staging directroy? The wrappter skript + ./libs/origbinary or just the binary out of .libs?

Sorry, for the unqualified questions.

Kind regards,
Marcus