Re: making script executable?

2003-02-03 Thread Steve M. Robbins
On Mon, Feb 03, 2003 at 05:20:02PM -0500, [EMAIL PROTECTED] wrote: > > > I have a shell script which I want to run as part of a testsuite. However > when I do a 'make distcheck' this script (which does not get configured or > anything at build time) ends up with execute permissions turned off. >

Re: making script executable?

2003-02-03 Thread Bob Proulx
Simon Richter wrote: > > $(SHELL) ? [Drifting off topic...] Does that mean that a SHELL=/bin/csh user will run the script with csh and a SHELL=/bin/zsh user will run the shell with zsh? Wouldn't it be better to use a predictable and most likely a standard shell for both users? /bin/sh "your

Re: making script executable?

2003-02-03 Thread mcmahill
I tried TESTS= '${SHELL} my_script' but automake ends up treating ${SHELL} and my_script as seperate test programs to run. I suppose I could do something like move my_script to my_script.in, let configure simply copy it and then add all-local: chmod 755 my_script but that seems lik

Re: making script executable?

2003-02-03 Thread Simon Richter
Hi, > I have a shell script which I want to run as part of a testsuite. However > when I do a 'make distcheck' this script (which does not get configured or > anything at build time) ends up with execute permissions turned off. $(SHELL) ? Simon -- GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD

making script executable?

2003-02-03 Thread mcmahill
I have a shell script which I want to run as part of a testsuite. However when I do a 'make distcheck' this script (which does not get configured or anything at build time) ends up with execute permissions turned off. Since I want to be able to properly deal with a read only source tree, what sh

Fix for _AC_AM_CONFIG_HEADER_HOOK (CONFIG_HEADER stamp file creation)bug

2003-02-03 Thread Sander Niemeijer
This replacement for the _AC_AM_CONFIG_HEADER_HOOK macro (located in m4/init.m4) fixes an incorrect naming issue of stamp-h* files when only specific headers are recreated through config.status. The problem can be reproduced by creating a configure.ac file containing: --- AC_CONFIG_HEADERS([con

Re: autoreconf --flavor ?

2003-02-03 Thread Andreas Schwab
Patrick Guio <[EMAIL PROTECTED]> writes: |> Dear all, |> I am using currently autoconf 2.57 and automake 1.7.2. |> I find it annoying not to be able to use te nice tool autoreconf without |> that all the following files NEWS, README, AUTHORS and ChangeLog should be |> present in the current direct

autoreconf --flavor ?

2003-02-03 Thread Patrick Guio
Dear all, I am using currently autoconf 2.57 and automake 1.7.2. I find it annoying not to be able to use te nice tool autoreconf without that all the following files NEWS, README, AUTHORS and ChangeLog should be present in the current directory. automake has the possibility to disable that featur