From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: config.modules glitch in configure or make dependencies
Date: Fri, 13 Sep 2002 17:53:17 +0000 [thread overview]
Message-ID: <1020913175317.ZM9183@candle.brasslantern.com> (raw)
In-Reply-To: <4665.1031932669@csr.com>
On Sep 13, 4:57pm, Peter Stephenson wrote:
} Subject: Re: config.modules glitch in configure or make dependencies
}
} "Bart Schaefer" wrote:
} > Consider the following patch; configure writes config.modules.sh and also
} > arranges that config.status will source it, and then sources it.
}
} Well, it's about the only bit of the configuration not yet done in (at
} least) two stages, so I don't see why it shouldn't share the pain.
It's not really two stages; the code still executes at the same time it
always did, it just happens to be in two files. If you prefer, it could
be written like this:
AC_OUTPUT_COMMANDS(,[if test -z "\$CONFIG_FILES\$CONFIG_HEADERS"; then
`cat ./${CONFIG_MODULES}.sh && rm -f ./${CONFIG_MODULES}.sh`
fi])
. ./${CONFIG_MODULES}.sh
That actually copies the code from configure into config.status, so that
the .sh file doesn't have to be left behind.
--
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
next prev parent reply other threads:[~2002-09-13 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 14:20 Bart Schaefer
2002-09-12 9:37 ` Peter Stephenson
2002-09-12 14:58 ` Bart Schaefer
2002-09-13 9:18 ` Peter Stephenson
2002-09-13 15:46 ` Bart Schaefer
2002-09-13 15:57 ` Peter Stephenson
2002-09-13 17:53 ` Bart Schaefer [this message]
2002-09-13 18:31 ` Clint Adams
2002-09-13 22:47 ` 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=1020913175317.ZM9183@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.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).