From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] converting util-linux-ng to autotargets
Date: Mon, 26 Jul 2010 22:39:35 +0200 [thread overview]
Message-ID: <4C4DF287.9090006@gmx.net> (raw)
In-Reply-To: <20100726082906.49146628@surf>
Am 26.07.2010 08:29, schrieb Thomas Petazzoni:
> 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
prev parent reply other threads:[~2010-07-26 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 19:47 [Buildroot] converting util-linux-ng to autotargets Ossy
2010-07-26 6:29 ` Thomas Petazzoni
2010-07-26 20:39 ` Ossy [this message]
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=4C4DF287.9090006@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.