-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Alfred M. Szmidt on 5/13/2009 7:22 AM:
> +Depending on the package, the default directory layout chosen during
> +@command{configure} can be altered during subsequent execution of
> +@command{make}.
>
> A `make install FOO=VAL' should never alter anything in the build
> directory. The problem is if you pass --bindir=/foo to configure, and
> then do `make install prefix=/bar', the files installed in bindir will
> be installed in /foo, and not /bar as the user might have exepcted;
> this is why passing prefix to `make install' is a bad idea.
Agreed - which is why I went on to say this in the same paragraph:
+However, some programs need to know at
+compile time where files will be installed, so the user should ensure
+that the same directory choice is made for both @samp{make all} and
+@samp{make install}.
Any suggestions on how to improve the wording to make this point more
explicit?
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@xxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoKzXAACgkQ84KuGfSFAYA2DgCeNy41+fIpulQt3j5pdlRtwX8x
dSoAoJJKJhwQYbVlAcjLsNB0u0fE030W
=QY54
-----END PGP SIGNATURE-----
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
