%% Akim Demaille [EMAIL PROTECTED] writes:
ad Finally, note that you are allowed to ask config.status to perform
ad substitutions on files it doesn't know[1]. In your case, I'm unsure
ad binding the instantiation to configure instead of make is right.
Doh!
I thought this would be the
* Paul Smith wrote on Sun, Dec 05, 2004 at 08:25:56PM CET:
%% Akim Demaille [EMAIL PROTECTED] writes:
ad Finally, note that you are allowed to ask config.status to perform
ad substitutions on files it doesn't know[1]. In your case, I'm unsure
ad binding the instantiation to configure
* Stepan Kasal wrote on Mon, Dec 06, 2004 at 10:03:27AM CET:
Hello,
On Mon, Dec 06, 2004 at 09:28:17AM +0100, Ralf Wildenhues wrote:
AC_OUTPUT
touch foo.in
./config.status --file foo
why the ``touch''? (./config.status doesn't check the timestamps.)
Oh, that was just copy-n-paste
%% Ralf Wildenhues [EMAIL PROTECTED] writes:
I suppose I could tell those folks to run the config.status step by
hand, but I'd really like to get this built through the configure
script. Ideas?
rw dnl ...
rw AC_CONFIG_FILES([Makefile])
rw AC_OUTPUT
rw touch foo.in
rw
%% Akim Demaille [EMAIL PROTECTED] writes:
I need a way to have a file marked as a config file, but not have
configure (or automake) fail if the .in input file doesn't exist.
ad Hm... What is the service you are expecting? You say that
ad configure shouldn't fail, but if it's a
Paul == Paul Smith [EMAIL PROTECTED] writes:
%% Akim Demaille [EMAIL PROTECTED] writes:
I need a way to have a file marked as a config file, but not have
configure (or automake) fail if the .in input file doesn't exist.
ad Hm... What is the service you are expecting? You say that
ad
%% Akim Demaille [EMAIL PROTECTED] writes:
ad If you have a bootstrap script, why wouldn't it create a fake
ad file, run autoreconf, and them create the right file?
I don't have a bootstrap script for building out of CVS. I could create
one, I guess.
ad Finally, note that you are allowed
Andreas == Andreas Schwab [EMAIL PROTECTED] writes:
Untested code ahead.
m4_syscmd([test -f build.sh.in])dnl
m4_if(m4_sysval, 0, [AC_CONFIG_FILES(build.sh)])
Bad idea: side effects are incompatible with the (autom4te) cache. If
the environment changes but not the sources of configure,
That worked! Thanks Andreas.
--
---
Paul D. Smith [EMAIL PROTECTED] HASMAT--HA Software Mthds Tools
Please remain calm...I may be mad, but I am a professional. --Mad Scientist
%% Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
adl Hi Paul,
Paul == Paul Smith [EMAIL PROTECTED] writes:
Paul In the GNU make package I don't have a README file when
Paul it is first checked out from CVS.
Paul This used to work but now automake is failing:
adl What version(s)
Paul D. Smith [EMAIL PROTECTED] writes:
However, I actually had a second error that I didn't mention because I
figured it would be the same problem... but it's not.
The second error is this:
$ automake --add-missing --no-force
configure.in:398: required file `build.sh.in' not found
Hi Paul,
Paul == Paul Smith [EMAIL PROTECTED] writes:
Paul In the GNU make package I don't have a README file when
Paul it is first checked out from CVS. There is a README.in
Paul which is translated into a README, replacing the version
Paul info etc.
When and how?
Paul This used to
12 matches
Mail list logo