Skip to contentSkip to conversation

Problem with program_transform_name and naming of installed binaries

Buildroot Thomas Petazzoni 3 participants 4 messages Oct 31, 2008 – Nov 3, 2008

lore
Share & tools
lore
#0 lore 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

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

Le Fri, 31 Oct 2008 11:33:07 +0100,
Thomas Petazzoni <[email protected]> a ?crit :

Quoted 6 lines

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 ?

FYI, the related autoconf documentation is available at
http://www.gnu.org/software/autoconf/manual/html_node/Transforming-Names.html#Transforming-Names.

It seems that by default, the binary names are transformed to be prefixed with the target name, which is what I see. Should we add --program-prefix= and --program-transform-name= to the CONFIGURE_OPTS ?

Thomas

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

if passing the --program-prefix= and --program-transform-name= to the CONFIGURE_OPTS means that I do not need to rename executables (to remvoe mipsel-unknown-gnu-) then I am all for this being added to CONFIGURE OPTS.

Cheers
Daniel Laird

#3 lore raw
In reply to Thomas Petazzoni
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni <[email protected]> writes:

Hi,

Thomas> It seems that by default, the binary names are transformed to be Thomas> prefixed with the target name, which is what I see. Should we add Thomas> --program-prefix= and --program-transform-name= to the CONFIGURE_OPTS ?

I haven't seen the issue here (don't use directfb), but if it solves the problem and doesn't cause any other issues I say go for it.

Signature · 1 line
Bye, Peter Korsgaard