Problem trying to configure / build when using "--program-prefix" option

David Paterson
Mon Apr 18 22:19:00 GMT 2011

Hi all,

I'm running into a strange problem when using the "--program-prefix"
option during configuration.  I've built Newlib successfully before
without it, and now want to "personalise" the cross toolchain I'm
working on.

I'm configuring with :-

../newlib-1.19.0/configure --target=sparc-elf --disable-shared --disable-nls \
--disable-werror --disable-newlib-supplied-syscalls --enable-interwork \
--enable-multilib --with-gnu-as --with-gnu-ld --prefix=/usr/local/SparcTools \

and during the config I'm seeing the following messages :-

checking for sparc-elf-cc... no
checking for sparc-elf-gcc... no
checking for sparc-elf-c++... no
checking for sparc-elf-g++... no
checking for sparc-elf-cxx... no
checking for sparc-elf-gxx... no
checking for sparc-elf-gcc... no
checking for sparc-elf-gcj... no
etc. for several more tool names...

Then, when I try to build (make all) I get :-

/bin/sh: sparc-elf-cc: command not found

Which of course is correct, since there isn't any "sparc-elf-" tools, as they're
all named "test-elf-gcc" and the like.  GCC and Binutils all seem to be happy
with the program prefix option, and create their outputs as expected.

If I rebuild everything without using "--program-prefix" then I get :-

checking for sparc-elf-cc... no
checking for sparc-elf-gcc... sparc-elf-gcc
checking for sparc-elf-c++... sparc-elf-c++

as if finds the tools correctly, and Newlib builds without problems.

I'm guesing there's a config option I need to add to specify that I'm using a
non-target-triplet prefix system, but I've read through the list of options
several times and can't see what I need to use.

I'd appreciate a hint or two as to where I'm going wrong :-)  I'd really like to
use a project-specific prefix for these tools, but if I can't, I guess
I can live
with it...


David P.

More information about the Newlib mailing list