This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: AM_MAKE_INCLUDE
- To: corsepiu at faw dot uni-ulm dot de
- Subject: Re: AM_MAKE_INCLUDE
- From: Raja R Harinath <harinath at cs dot umn dot edu>
- Date: 27 Mar 2001 10:04:56 -0600
- Cc: Automake List <automake at gnu dot org>
- List-Id: Discussion list for automake <automake.gnu.org>
- References: <3AC047D4.3F08A6DC@faw.uni-ulm.de>
Hi,
Ralf Corsepius <corsepiu@faw.uni-ulm.de> writes:
> An observation with cvs-autoconf and automake-1.4d:
>
> Given this configure.in:
>
> AC_INIT(Makefile.am)
> AM_INIT_AUTOMAKE(foo,0,no)
> AM_MAKE_INCLUDE
> AC_OUTPUT(Makefile)
>
> # ./configure
[snip]
> Note: style of include "include"
>
> Now touching/editing configure.in and rerunning make:
>
> # touch configure.in
> # make
> [..]
> /bin/sh ./config.status --recheck
> running /bin/sh ./configure --no-create --no-recursion
[snip]
> Note: style of include "#"
I've seen something similar. Running './config.status --recheck'
again seems to fix it.
Unfortunately, the output of make is redirected to /dev/null. My
suspicion is that this could do with the timestamp warning sometimes
emitted by GNU make. Is the directory NFS mounted from a Solaris m/c?
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash