From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with program_transform_name and naming of installed binaries
Date: Fri, 31 Oct 2008 11:33:07 +0100 [thread overview]
Message-ID: <20081031113307.14125656@surf> (raw)
Hi,
For some reason, the binaries installed by DirectFB and Lite (but maybe
other packages are affected, I don't know), get prefixed with
arm-unknown-linux-uclibcgnueabi-. That doesn't happen for the binaries
of libgif, libjpeg, libfreetype and libpng.
Examples:
arm-unknown-linux-uclibcgnueabi-dfbdump
arm-unknown-linux-uclibcgnueabi-dfbg
arm-unknown-linux-uclibcgnueabi-lite_checktest
arm-unknown-linux-uclibcgnueabi-lite_dfbspy
(These are in my $(STAGING_DIR)/usr/bin).
My understanding is that the Makefile does a sed on the destination
binary name, using the 'program_transform_name' variable, computed
at ./configure time.
In my config.log, I can see the value of this variable:
program_transform_name='s&^&arm-unknown-linux-uclibcgnueabi-&'
Which indeed will transform "foo" into "arm-blablabla-foo".
Of course, this is not the desired behaviour, since binaries on the
target also end up with the arm-blablabla prefix. However, after a
quick look at ./configure, I don't really understand what's the logic
to compute this program_transform_name variable.
Any clue ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next reply other threads:[~2008-10-31 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 10:33 Thomas Petazzoni [this message]
2008-10-31 13:43 ` [Buildroot] Problem with program_transform_name and naming of installed binaries Thomas Petazzoni
2008-10-31 14:26 ` Daniel J Laird
2008-11-03 10:48 ` Peter Korsgaard
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=20081031113307.14125656@surf \
--to=thomas.petazzoni@free-electrons.com \
--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.