[Buildroot] Problem with program_transform_name and naming of installed binaries

[Buildroot] Problem with program_transform_name and naming of installed binaries

[Thomas Petazzoni]

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

[Buildroot] Problem with program_transform_name and naming of installed binaries

[Thomas Petazzoni]

Le Fri, 31 Oct 2008 11:33:07 +0100,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :

> 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
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

[Buildroot] Problem with program_transform_name and naming of installed binaries

[Daniel J Laird]

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

[Buildroot] Problem with program_transform_name and naming of installed binaries

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 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.

-- 
Bye, Peter Korsgaard