Since autom4te is really a script, should this be something to be deduced
at the scripts runtime rather than at the install time (using configure) ?
Seems restrictive, especially because I was hoping to have a single installation
of the package for both solaris and linux. The autoconf package was configured
only on linux. This seems to work but for the M4 part, so far.
kamaljit
Eric Blake <ebb9@xxxxxxx> wrote: -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Kamaljit Singh on 12/6/2007 8:09 PM:
> What I see in auto4mte (2.61) is that it checks for $ENV("M4") || "/usr/bin/m4"
> which is not good at all, in the sense it doesnt care for the path and hence fails
> for me.
When M4 is not defined in the environment, autom4te falls back on the
hardcoded value that was learned at autoconf configure time, even for the
upcoming 2.62 (it's just that 2.62 will be more likely to make a good
choice than 2.61). If you want the default M4 fallback in autom4te
changed, rerun autoconf's ./configure with your choice of M4 environment
variable, then reinstall autoconf.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@xxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHWNuY84KuGfSFAYARAsbaAJ9yBfK3ve4SCveMBEKF0smx0Cc1RQCfauTm
5rMkUAIo7JbzbbYnK8ZThAY=
=Gwbl
-----END PGP SIGNATURE-----
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
