[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Do fail when regeneration of Makefile.in does not succeed
From: |
Jan Engelhardt |
Subject: |
Do fail when regeneration of Makefile.in does not succeed |
Date: |
Wed, 14 Nov 2012 16:44:08 +0100 (CET) |
User-agent: |
Alpine 2.01 (LNX 1266 2009-07-14) |
Hi,
Is there an option to yield an error instead of a warning
if Makefile.in needs to be regenerated, but can't?
The case before me is that iptables's Makefile.am in openSUSE is
patched after tarball extraction. But, due to 1. $PEBKAC not calling
autoreconf, 2. the system having automake-1.12 instead, Makefile.in
was not regenerated, which ultimately led to files not being shipped
in the resulting RPM. I would like to catch this case at the auto*
level.
[ 50s] make[2]: Entering directory
`/home/abuild/rpmbuild/BUILD/iptables-1.4.16.3/iptables'
[ 50s] cd .. && /bin/sh
/home/abuild/rpmbuild/BUILD/iptables-1.4.16.3/build-aux/missing --run
automake-1.11 --gnu iptables/Makefile
[ 50s] /home/abuild/rpmbuild/BUILD/iptables-1.4.16.3/build-aux/missing: line
52: automake-1.11: command not found
[ 50s] WARNING: `automake-1.11' is missing on your system. You should only
need it if
[ 50s] you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
[ 50s] You might want to install the `Automake' and `Perl' packages.
[ 50s] Grab them from any GNU archive site.
[ 50s] cd .. && /bin/sh ./config.status iptables/Makefile depfiles
[ 51s] config.status: creating iptables/Makefile
[ 51s] config.status: executing depfiles commands
[...]
Jan
- Do fail when regeneration of Makefile.in does not succeed,
Jan Engelhardt <=