From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: Cygwin - second go.
Date: Tue, 15 Aug 2000 10:48:54 +0000 [thread overview]
Message-ID: <1000815104855.ZM18819@candle.brasslantern.com> (raw)
In-Reply-To: <000001c00680$42f44860$21c9ca95@mow.siemens.ru>
On Aug 15, 10:15am, Andrej Borsenkow wrote:
} Subject: RE: PATCH: Cygwin - second go.
}
} > 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.
}
} Are you sure, it is a problem of missing empty line?
Yes.
} 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.
Right.
} This expansion is part of AC_CYGWIN and has nothing to do with AC_EXEEXT.
Wrong. In /usr/lib/autoconf/acspecific.m4 we have:
AC_DEFUN(AC_EXEEXT,
[AC_REQUIRE([AC_CYGWIN])
AC_REQUIRE([AC_MINGW32])
AC_MSG_CHECKING([for executable suffix])
....
The `test "$ac_cv_cygwin" = yes && CYGWIN=yes' comes from AC_CYGWIN and
the `echo $ac_n "checking for mingw32 environment""... $ac_c" 1>&6' is
from AC_MINGW32. The problem is that if you *explicitly* use AC_CYGWIN,
then the first AC_REQUIRE in AC_EXEEXT doesn't expand and the beginning
of AC_MINGW32 gets pasted onto the end of the explicit AC_CYGWIN output.
So maybe the bug you're thinking of is that AC_EXEEXT gets it wrong if
you *don't* explicitly use AC_CYGWIN followed by a blank line; I didn't
try that, but I *did* check the output the way I committed the patch.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-08-15 10:50 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
2000-08-15 10:48 ` Bart Schaefer [this message]
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=1000815104855.ZM18819@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--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).