From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Cygwin - second go.
Date: Tue, 15 Aug 2000 10:15:51 +0400 [thread overview]
Message-ID: <000001c00680$42f44860$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000815050838.ZM18590@candle.brasslantern.com>
>
> Seems to compile OK on linux, I'll commit the patch.
>
> I just noticed, however that under autoconf 2.13 the definion of AC_CYGWIN
> doesn't work right if you follow it with a `dnl' directive. It ends up
> merging with the expansion of AC_EXEEXT that follows it, so a configure
> script generated from autoconf 2.13 won't ever set CYGWIN=yes properly.
>
> The solution is either to remove the `dnl' comment from the line with
> the AC_CYGWIN call, or simply to put a blank line after it, which is
> what I did.
>
Yes, I knew it; that why I used ac_cv_cygwin and not CYGWIN.
Are you sure, it is a problem of missing empty line? Look, what is generated:
CYGWIN=
test "$ac_cv_cygwin" = yes && CYGWIN=yes echo $ac_n
"checking for mingw32 environment""... $ac_c" 1>&6
that is, CYGWIN is set in environment of `echo' command and lost after this.
This expansion is part of AC_CYGWIN and has nothing to do with AC_EXEEXT.
There is no way to change it. I even believe to have seen a bug report once,
but currently querying autoconf bug database yields no result.
-andrej
next prev parent reply other threads:[~2000-08-15 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-14 17:54 Andrej Borsenkow
2000-08-15 5:08 ` Bart Schaefer
2000-08-15 6:15 ` Andrej Borsenkow [this message]
2000-08-15 10:48 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001c00680$42f44860$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).