[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changing AC_DEFINE
From: |
Akim Demaille |
Subject: |
Re: Changing AC_DEFINE |
Date: |
01 Jun 2001 19:35:01 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (GTK) |
>>>>> "Tim" == Tim Van Holder <address@hidden> writes:
>> 2. is it safe to use both an FD to confdefs.h and redirections to
>> confdefs.h?
Tim> As Lars said, my experiences with config.log suggest that this is
Tim> not the case on DOS. I suppose I could raise the issue with the
Tim> maintainers of DJGPP's libc and bash to see if this can be
Tim> resolved in future versions, but that would be a fairly long-term
Tim> solution.
In fact my original thinking was that some `foreigners' (i.e., non
maintainers) might play tricks with confdefs.h. But again, (thanks
for reminding me the config.log issue, I seemed to recall there was
something, but had forgotten the context), users are not expected to
do that. So since we are (theoretically) the only ones to touch
confdefs.h (which is not documented...), it remains feasible.
Still, some big users, say GCC, do play such tricks. Now the question
is, are they ready to update their macros to be compliant with this
scheme?
Alexandre?
- RFC: Changing AC_DEFINE, Akim Demaille, 2001/06/01
- Re: RFC: Changing AC_DEFINE, Lars J. Aas, 2001/06/01
- RE: Changing AC_DEFINE, Tim Van Holder, 2001/06/01
- Re: Changing AC_DEFINE,
Akim Demaille <=
- Re: RFC: Changing AC_DEFINE, Alexandre Oliva, 2001/06/01
- Re: RFC: Changing AC_DEFINE, Paul Eggert, 2001/06/01
- Re: RFC: Changing AC_DEFINE, Akim Demaille, 2001/06/02
- Re: RFC: Changing AC_DEFINE, Alexandre Oliva, 2001/06/09
- Re: RFC: Changing AC_DEFINE, Tim Van Holder, 2001/06/09
- Re: RFC: Changing AC_DEFINE, Alexandre Oliva, 2001/06/17
- Re: RFC: Changing AC_DEFINE, Tim Van Holder, 2001/06/18
- Re: RFC: Changing AC_DEFINE, Alexandre Oliva, 2001/06/19