-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthew Woehlke wrote: > Harald Servat wrote: >> I'm trying to provide a compiler to this macro (using it's name and >> the full path name) when some special conditions occur but as it isn't >> on the default $PATH, AC_PROG_CC skips it. >> >> Right now, I can only find two solutions. Just add the the directory >> that contains this compiler to the $PATH or set CC (in the configure.ac) >> with this compiler when those conditions happen. >> First approach isn't quite user-friendly because each time I want to >> run configure I have to touch the PATH variable. The latter would skip a >> new compiler given by the user through CC environment variable when >> invoking configure. > > I'm not clear what's wrong with option 1. Can't you set PATH in the > configure script? I would guess you can check these "conditions" and > only tinker with it when they occur, even. Why is this "unfriendly"? > Yes, I can set it. But that's my "problem": If I set it at my .bashrc (for example) when I share this package other users must put this directory in their PATH too, and I want to avoid this if possible because I want this procedure as automatic and transparent as possible. If I set PATH on the configure script, Makefile will not find it by default because this new value for PATH isn't seen by the Makefile. So, in this situation, I'm unable to give an automatic compiler selection without asking the user to alter it's PATH. Of course, I can do it. It's feasible. But I'm looking for a solution that does not require the user to alter his PATH. Regards, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGEoFGwMPeuqUCg9wRAkovAJ9OzFStPLdFWWasmBAWSgsc18dINgCffciv YPK2mkslI6rJRBtsJA6Oq14= =xory -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
