[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_OBJEXT again
From: |
Akim Demaille |
Subject: |
Re: AC_OBJEXT again |
Date: |
07 Dec 2000 11:45:12 +0100 |
User-agent: |
Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) |
>>>>> "Mo" == Mo DeJong <address@hidden> writes:
Mo> I have to admit that I am a bit confused about what is going on
Mo> with the _AC_CYGWIN and _AC_MINGW32 macros. I was under the
Mo> impression that they were required for _AC_EXEEXT or _AC_OBJEXT,
Mo> but it seems like the addition of these new patches will mean the
Mo> obj and exe extension will not need to depend on _AC_CYGWIN or
Mo> _AC_MINGW32. I am wondering if the code that checks for $CYGWIN in
Mo> this macro can just be removed?
These lines are my main grief against these macros: they are causing
many problems. But in addition they are the sources of the bizarre
status of OBJEXT and EXEEXT: these lines clearly defines them as
*host* characteristics, while the next lines are *build*
characteristics.
OBJEXT and EXEEXT are my 2.50 nightmare. I hope we will be able to
have something clear and functional. I first need to summarize what
people said, then define precisely what they are (build, or host?),
and finally implement what's been chosen.
Let's not hurry. First, summarize, there are *zillions* of messages
about this.
- Re: AC_OBJEXT again,
Akim Demaille <=
- Re: AC_OBJEXT again, Morten Eriksen, 2000/12/07
- Re: AC_OBJEXT again, Akim Demaille, 2000/12/07
- Re: AC_OBJEXT again, Alexandre Oliva, 2000/12/08
- Re: AC_OBJEXT again, Akim Demaille, 2000/12/12
- Re: AC_OBJEXT again, Akim Demaille, 2000/12/12
- Re: AC_OBJEXT again, Peter Eisentraut, 2000/12/12
- Re: AC_OBJEXT again, Alexandre Oliva, 2000/12/12
- Re: AC_OBJEXT again, Akim Demaille, 2000/12/12
- Re: AC_OBJEXT again, Alexandre Oliva, 2000/12/12
- Re: AC_OBJEXT again, Akim Demaille, 2000/12/12