%% 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 config file, configure is ad> expected to fail. Unless you do mean configure, and not ad> config.status? When I first check out my code from CVS, I don't have a build.sh.in file. That file is autogenerated as part of the build process, from a template file. It's not required for a maintainer-mode build: that file is basically a bootstrap assist: a way to build "make" if you don't have any "make" yet. Maintainers are expected to have a full suite of tools at their disposal including make. By the time I actually make a distfile, that file (build.sh.in) will be there and it will be included in the distfile so normal users will never see this issue. But, I need a way to run "autoreconf" in a clean workspace where that file doesn't exist... and if I use normal AC_CONFIG_FILES then automake complains and won't build my Makefile.in. -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ------------------------------------------------------------------------------- These are my opinions---Nortel Networks takes no responsibility for them.