Re: Suggestion for --with-local-prefix configure option

[fheitka@ibm.net]

In < c37ea7d.36ef0bb1@aol.com >, on 03/16/99 
   at 08:56 PM, N8TM@aol.com said:

>In a message dated 3/16/99 10:16:13 AM Pacific Standard Time,
>dm@reeducation-
>labor.lcs.mit.edu writes:

>> Currently the option always defaults to /usr/local,
>>  regardless of --prefix.  I argue that this default is wrong for most
>>  cases.

>I'll present an inexpert but biased opinion.  I have no problem with the
>/usr/local default.  I let the snapshots go in /usr/local on all systems
>where I have the privilege to do so, without having to worry about
>whether it is a workable version.  I install the "stable" releases in the
>primary compiler location for the target, if I have privileges there. 
>The only target I use where /usr/local is accessible to me and is on the
>standard search path is HPUX.  But there, I have to play symlink games
>because there isn't any disk space in the real /usr/local, not even
>enough to run applications which need significant space on /tmp.

Lately, I've been inclined to put binutils and egcs binaries in their own
directory like: --prefix=/usr/egcs-m68k-glibc2.1 and make links to the
/usr/bin or /usr/local/bin directory.  This makes it much easier to keep
track of different versions.  Also if your are trying a new version, you
can just change the links.  I think this is a good way to install egcs. Is
there any problems with this?

Fred