When should I use "--with-local-prefix"

[Kai Ruottu]

> to configure and install gcc-2.8.1?
> 
> For example, if I want to install all my GNU tools in /usr/local/ARM, the
> directories /usr/local/ARM/include and /usr/local/ARM/$target/include is
> created when the tools are installed.
> 
> The default is that include files are search in /usr/local/include.

 Is it really ?  Anyway I have only the 'g++' subdir there, so I have never
seen it tried to be used when using the '-v' in gcc command line...

----------- clip ----------------
GNU CPP version gcc-2.95 19990615 (prerelease) (ARM/coff)
#include "..." search starts here:
#include <...> search starts here:
 E:/usr/local/lib/gcc-lib/arm-coff/2.95/include
 E:/usr/local/lib/gcc-lib/arm-coff/2.95/../../../../arm-coff/include
 /usr/local/lib/gcc-lib/arm-coff/2.95/include
 /usr/local/lib/gcc-lib/arm-coff/2.95/../../../../arm-coff/include
End of search list.
The following default directories have been omitted from the search path:
 /usr/local/lib/gcc-lib/arm-coff/2.95/../../../../include/g++
 /usr/local/lib/gcc-lib/arm-coff/2.95/../../../../arm-coff/sys-include
----------- clip ----------------

> But, is it not better to point to one of the directories specified above.
> But, which one should it be?

 The expected place for the target stuff is under '<prefix>/<target>'.

 Why you must have that redundant 'ARM' ('ARM/arm-coff') in your path names, I 
don't fully understand.

 Why using the default:

  /usr/local/arm-coff/...
and
  /usr/local/lib/gcc-lib/arm-coff/2.8.1

in your case, for the 'arm-coff' spesific stuff isn't enough to make clear 
what's behind them?

 The default binary directory in PATH, '/usr/local/bin' would have the 
ARM-stuff as 'arm-coff-*'...  Now you have choosed to put these at 
'/usr/local/ARM/bin'. If you choose to add e.g. a M.CORE target toolset into
your system, would it be behind '/usr/local/M.CORE/' ?  I would just leave 
these target-name things away and use just the defaults...

----------- clip ------------
E:\usr\local\samples\sort>gcc-mcore-elf -v
Reading specs from E:/usr/local/lib/gcc-lib/mcore-elf/egcs-1.12/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
----------- clip ------------

 Having a network and the possibility to put the binaries somewhere else, e.g.
Linux/x86 binaries into a Solaris2 server, adding the host-name to the search
paths would however be motivated :

   /usr/local/H-i586-linux-gnu/bin
   /usr/local/H-i586-linux-gnu/arm-coff/...
   /usr/local/H-i586-linux-gnu/lib/gcc-lib/arm-coff/...

 Cygnus uses this kind of naming in their releases, but for a single-host user 
it may look as quite ugly... Ok, e.g. the Cygwin-FAQ tries to tell why it 
is like it is...

 As the previous 'gcc-mcore-elf' tells, some people has inverted minds an a
"--with-local-postfix" option would be needed for us... (Fortunately there is 
the 'mv' command...)

 Cheers, Kai
_______________________________________________
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
_______________________________________________
To remove yourself from the crossgcc list, send
mail to crossgcc-request@cygnus.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.