Re: Running ./config.status

2005-02-04 Thread Ralf Corsepius
On Fri, 2005-02-04 at 13:01 -0800, Paul Eggert wrote: > > On Fri, Feb 04, 2005 at 02:49:29PM +0100, Ralf Corsepius wrote: > >> So adding $(SHELL) might not be wrong. > > But SHELL might disagree with CONFIG_SHELL; the latter is used to run > config.status. So adding $(SHELL) might be wrong. Possi

Re: Running ./config.status

2005-02-04 Thread Alexandre Duret-Lutz
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes: Paul> So these days, I suspect that SHELL != CONFIG_SHELL mismatch is the Paul> greatest problem here. Actually it's rather the converse :) The two variables are equal (configure does SHELL=${CONFIG_SHELL-/bin/sh}), and this has caused some

Re: Running ./config.status

2005-02-04 Thread Paul Eggert
> On Fri, Feb 04, 2005 at 02:49:29PM +0100, Ralf Corsepius wrote: >> So adding $(SHELL) might not be wrong. But SHELL might disagree with CONFIG_SHELL; the latter is used to run config.status. So adding $(SHELL) might be wrong. Noah Misch <[EMAIL PROTECTED]> writes: > I suspect more systems sti

Re: Running ./config.status

2005-02-04 Thread Ralf Wildenhues
* Noah Misch wrote on Fri, Feb 04, 2005 at 03:32:01PM CET: > On Fri, Feb 04, 2005 at 02:49:29PM +0100, Ralf Corsepius wrote: > > On Fri, 2005-02-04 at 05:10 -0800, Noah Misch wrote: > > > If you believe `man perlrun', some systems do not respect #! and start all > > > scripts under csh. http://www

Re: Running ./config.status

2005-02-04 Thread Noah Misch
On Fri, Feb 04, 2005 at 02:49:29PM +0100, Ralf Corsepius wrote: > On Fri, 2005-02-04 at 05:10 -0800, Noah Misch wrote: > > If you believe `man perlrun', some systems do not respect #! and start all > > scripts under csh. > > I assume, the systems they refer to, actually are victim to the length >

Re: Running ./config.status

2005-02-04 Thread Ralf Corsepius
On Fri, 2005-02-04 at 05:10 -0800, Noah Misch wrote: > On Fri, Feb 04, 2005 at 08:53:51AM +0100, Stepan Kasal wrote: > > - cd $(top_builddir) && ./config.status $(subdir)/$@ > > + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ > > > The question: Why does Automake add "$(S

Re: Running ./config.status

2005-02-04 Thread Noah Misch
On Fri, Feb 04, 2005 at 08:53:51AM +0100, Stepan Kasal wrote: > - cd $(top_builddir) && ./config.status $(subdir)/$@ > + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ > The question: Why does Automake add "$(SHELL)" to the command? If you believe `man perlrun', some syst

Re: pkgincludedir, pkglibdir and config.status

2005-02-04 Thread Stepan Kasal
Hi, On Mon, Jan 31, 2005 at 02:35:58PM +0300, Konstantin Osipov wrote: > .sh: > @SED@ \ > -e 's!@''bindir''@!$(bindir)!g' \ > -e 's!@''pkglibdir''@!$(pkglibdir)!g' \ [...] > .sh: > $SHELL $(top_builddir)/config.status [EMAIL PROTECTED]:$@ > So I had to look at all .sh templates

Re: "include $(top_builddir)/aminclude.am" is ignored by automake

2005-02-04 Thread Stepan Kasal
Hi, On Fri, Feb 04, 2005 at 10:47:13AM +1100, Tom Howard wrote: > Slight problem; Removed all the generated files, did an autoreconf and > automake complains that fragement.mk is not found. I can just touch the > file before running autoreconf, but is there a nice way to tell automake > that it c