Hello, Peter! > This equivalency only affects stat() and the PATH search of the shell. So > you can write makefiles like this: > > fooprog: $(OBJS) > $(CC) -o $@ $^ > > install: fooprog > $(INSTALL) fooprog$(EXEEXT) $(bindir) > > and they will work. But it probably doesn't in general on other systems > that have executable extensions. In fact, I'd have no idea how to act in > face of arbitrary $(EXEEXT) values. We (Autoconf) just need to supply the right EXEEXT. Dealing with it is a problem of Automake and Make. Since EXEEXT="" makes "cp" fail it's not a good choice. So instead of doing "test contest -ef contest.exe" do "cp contest contest.ac_" and reverse the logic (i.e. if "cp" fails we use ".exe") Regards, Pavel Roskin
- Re: AC_PROG_CC not working Akim Demaille
- Re: AC_PROG_CC not working Bob Friesenhahn
- Re: AC_PROG_CC not working Akim Demaille
- Re: AC_PROG_CC not working Gary V. Vaughan
- Re: AC_PROG_CC not working Akim Demaille
- Re: AC_PROG_CC not working Gary V. Vaughan
- Re: AC_PROG_CC not working Peter Eisentraut
- Re: AC_PROG_CC not working Morten Eriksen
- Re: AC_PROG_CC not working Pavel Roskin
- Re: AC_PROG_CC not working Peter Eisentraut
- Re: AC_PROG_CC not working Pavel Roskin
- Re: AC_PROG_CC not working Morten Eriksen
- Re: AC_PROG_CC not working Earnie Boyd
- Re: AC_PROG_CC not working Earnie Boyd
- Re: AC_PROG_CC not working Pavel Roskin
- Re: AC_PROG_CC not working Earnie Boyd
- RE: AC_PROG_CC not working Bernard Dautrevaux
- RE: AC_PROG_CC not working Earnie Boyd