Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] help in converting util-linux-ng to autotargets
@ 2010-07-27 22:07 Ossy
  0 siblings, 0 replies; only message in thread
From: Ossy @ 2010-07-27 22:07 UTC (permalink / raw)
  To: buildroot

Hi mailinglist,

I was able to convince a recent version of util-linux-ng (1.17.2) to 
compile for my target which is arm926t.

After the compilation I find several arm 32bit elfs in 
output/build/util-linux-ng-2.17.

I have three unclear issues for now:

A)
What do I do with the placeholder scripts from libtool?
Sometimes I find a libtool script instead of the expected binary. The 
binary itself is located in the corresponding .libs directory.
Do I need to install both - placeholder skript and binary out of .libs?

B)
How do I define the $(INSTALL)-part in the *mk-file for autotargets?
I found this or similar example:
define UTIL_LINUX_NG_INSTALL_TARGET_CMDS
        $(INSTALL) -D $(@D)/usr/bin/chkdupexe 
$(TARGET_DIR)/usr/sbin/chkdupexe
endef

Do I need to know every location of every binary out of util-linux-ng to 
install it from output/build/util-linux-ng-2.17 to STAGING-DIR?
This is quite a lot. With the old variant a make install (into 
STAGING_DIR) would be sufficnet I guess.
I'm a bit lazy. Do I need to define a line for every binary copy to 
staging? How would it look like?

C)
I like to build the libraries libblkid and libuuid and install them in 
the target fs. I found a link, the .a and .so variants in 
output/build/somedir. Which one do I need to isntall? Is it neccessary 
to copy the symlink from libuuid.so->libuuid.so.VERSION to the target fs?


Thanks for any hint.


Kind regards,
Marcus

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-07-27 22:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-27 22:07 [Buildroot] help in converting util-linux-ng to autotargets Ossy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox