All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] help in converting util-linux-ng to autotargets
Date: Wed, 28 Jul 2010 00:07:37 +0200	[thread overview]
Message-ID: <4C4F58A9.50309@gmx.net> (raw)

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

                 reply	other threads:[~2010-07-27 22:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C4F58A9.50309@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.