From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: How to cache $CFLAGS, $LIBS etc.
Date: Wed, 16 Aug 2000 11:25:31 +0400 [thread overview]
Message-ID: <000001c00753$28acb0e0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <0FZ400K4WL6P0H@la-la.cambridgesiliconradio.com>
>
> 2. Use `--enable-cflags', `--enable-libs', `--enable-ldflags' or whatever.
> This probably ought to work because the arguments are remembered for use
> with --recheck. But the guide for how configure is used is pretty
> fascistic about not allowing anything RMS wouldn't like, so I don't know if
> there are drawbacks to this. Plus we need to be careful if people supply
> environment variables in the standard way.
>
> Does anyone know how to do this properly?
>
May be it is too late, but NEWS for current CVS autoconf says:
- Remembers environment variables when reconfiguring.
The previous scheme to set envvar before running configure was
ENV=VAL ./configure
what prevented configure from remembering the environment in which
it was run, therefore --recheck was run in an inconsistent
environment. Now, one should run
./configure ENV=VAR
and then --recheck will work properly. Variables declared with
AC_ARG_VAR are also preserved.
It also has the whole bunch of new tests (64 bit, LFS, check for proper
function prototypes etc etc).
The CVS version was recently stamped with version number that probably
indicates it's relative "stableness" :-) If we commit to using it ... some
packages do (NTP being one). It also gives a chance to test autoconf before
release (at least, I'd be very interested to see if tests for 64bit/LFS really
work here).
-andrej
next prev parent reply other threads:[~2000-08-16 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 11:28 Peter Stephenson
2000-08-11 11:32 ` Ollivier Robert
2000-08-11 13:48 ` Trond Eivind Glomsrød
2000-08-11 16:16 ` Bart Schaefer
2000-08-11 16:37 ` Bart Schaefer
2000-08-11 18:08 ` Peter Stephenson
2000-08-16 7:25 ` Andrej Borsenkow [this message]
2000-08-16 12:56 ` 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='000001c00753$28acb0e0$21c9ca95@mow.siemens.ru' \
--to=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).