Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Fwd: Re: zsh compilation problem with autoconf git

X-seq: zsh-workers 24499
From: Eric Blake <ebb9@xxxxxxx>
To: Ismail Dönmez <ismail@xxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxx, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>, bug-autoconf@xxxxxxx
Subject: Re: Fwd: Re: zsh compilation problem with autoconf git
Date: Wed, 30 Jan 2008 06:03:56 -0700
In-reply-to: <20080129223819.GA12715@xxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <200801300003.33400.ismail@xxxxxxxxxxxxx> <20080129223819.GA12715@xxxxxxxxxxx>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Clint Adams on 1/29/2008 3:38 PM:
|> So the question is, is this thing needed at all, if yes why?
|
| Presumably Src/mkmakemod.sh would need to be generated to check that
| value in any supported manner.  I don't recall a reason that that
| can't be done.

The point was: Why not just use documented interfaces (such as AC_SUBST)
and skip the grep altogether?  The underlying interface is intentionally
unstable, and attempts to grep it are bound to fail as new autoconf
releases use new means of achieving the same results.  Your code will be
easier to maintain if you don't have to add a new grep statement for every
new autoconf release.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@xxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHoHW784KuGfSFAYARAkEbAJwIpAFwnIJH/hnrDZGD1hZSXX3NewCeLNhg
b5aVFo5xmZr7J5B7FTJeuPQ=
=JCNc
-----END PGP SIGNATURE-----

References:
- Fwd: Re: zsh compilation problem with autoconf git
  - From: Ismail Dönmez
- Re: Fwd: Re: zsh compilation problem with autoconf git
  - From: Clint Adams

Messages sorted by: Reverse Date, Date, Thread, Author