From: Soren A <sor...@fa...> - 2002-09-28 16:54:48
|
Earnie Boyd <ear...@ya...> wrote around 28 Sep 2002 news:3D9...@ya...: > Norman Vine wrote: >> >> Earnie Boyd writes: >> >> > Norman Vine wrote: >> > > >> > > > >> > > > Why not just check canonical build variable build_os which will >> > > > = mingw32 for mingw32 and will = cygwin for cygwin? >> > > >> > > I guess I don't know what needs to be done to be able to check >> > > for that >> > > >> > >> > if test "$build_os" = mingw32; then >> > ... >> > fi >> >> Thanks Ernie and that's what I thought but .... >> if I add this line to the end of a configure.ac file >> > > Does the configure.ac file contain AC_CANONICAL_HOST? > > Earnie. This is the key point. AC_CYGWIN is deprecated and the recommendation of the Autoconf people is to use AC_CANONICAL_HOST (and to do so early enough in the configure.ac). There's no need for any special kludge for Cygwin and hasn't been for quite awhile. And that's all AC_CYGWIN ever was: a kludge that unfortunately outlived its usefulness to an unusual degree (people got used to seeing it in 'configure.in|ac's and without understanding the full situation just mimic'ed it [call it "magic incantation syndrome"]). And it's a kludge that has potential undesirable side effects -- the documentation says _not merely_ "not needed anymore" but instead "PLEASE DON'T USE IT". IOW not just "deprecated" but "_severely_ deprecated". "Deprecated with extreme prejudice" if you are a fan of action-adventure thrillers. ;-) Norman, if AC_CANONICAL_HOST called at the appropriately early point (I believe that for most purposes just after AC_PROG_CC is appropriate) doesn't fix your problems, I think there is something going wrong. Best, Soren A |