Observations/Patch Concerning --prefix Permission Requirements

Kamil Iskra kamil@dwd.interkom.pl
Sun Feb 28 18:15:00 GMT 1999

On 20 Feb 1999 craig@jcb-sc.com wrote:

> This might indicate that --prefix identifies not just an *install*
> directory, but also a directory in which to (potentially) find
> files and programs supporting the build.  Does anyone know if that's
> the case -- if there's a design requirement that one or more existing
> files in the --prefix directory be used during the build process
> in any configuration?

Sure! For example, that's what I relied on when bootstrapping on HP/UX
10.20. I downloaded a pre-built binutils and arranged for them to be
accessible in /usr/local/hppa1.1-hp-hpux10.20/bin and then bootstrapped
egcs 1.1.1 with the default /usr/local prefix and --with-gnu-as. The just
built xgcc would call /usr/local/hppa1.1-hp-hpux10.20/bin/as as the

> I don't have any patches to offer to "fix" this, at the moment.
> It's not entirely clear to me this behavior is broken, but I
> currently lean in that direction.

Well, I think that --prefix-dir should be used during build if it is
accessible, though I agree that ideally the fact that the directory is not
accessible should not cause fatal errors.

/ Kamil Iskra    AmigaOS  Linux/i386  Linux/m68k               \
| GeekGadgets m68k-amigaos GCC maintainer                      |
| iskra@student.uci.agh.edu.pl  kiskra@ernie.icslab.agh.edu.pl |
\ kamil@dwd.interkom.pl   http://student.uci.agh.edu.pl/~iskra /

More information about the Gcc-patches mailing list