test: protect more yacc declarations against C vs. C++ linkage.
[automake.git] / t / remake-m4-pr10111.sh
blobb4d6f993f3ed900ba6cc2aa0fa40015c62ad8a11
1 #! /bin/sh
2 # Copyright (C) 2011-2024 Free Software Foundation, Inc.
4 # This program is free software; you can redistribute it and/or modify
5 # it under the terms of the GNU General Public License as published by
6 # the Free Software Foundation; either version 2, or (at your option)
7 # any later version.
9 # This program is distributed in the hope that it will be useful,
10 # but WITHOUT ANY WARRANTY; without even the implied warranty of
11 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 # GNU General Public License for more details.
14 # You should have received a copy of the GNU General Public License
15 # along with this program. If not, see <https://www.gnu.org/licenses/>.
17 # Check that our remake rules doesn't give spurious successes in
18 # some corner case situations where they should actually fail.
19 # See automake bug#10111.
20 # To be clear, we are speaking about *very* corner-case situations here,
21 # and the fact that the remake rules might get confused in them is not a
22 # big deal in practice (in fact, this test *currently fails*). Still,
23 # keeping the limitation exposed is a good idea anyway.
25 . test-init.sh
27 cat >> configure.ac <<'END'
28 m4_include([foobar.m4])
29 AC_OUTPUT
30 END
32 : > foobar.m4
34 cat > Makefile.am <<'END'
35 $(srcdir)/foobar.m4:
36 echo ': foobar was here :' > $@
37 END
39 $ACLOCAL
40 $AUTOCONF
41 $AUTOMAKE
43 ./configure
45 # OK, so the developer wants to interactively try out how the
46 # "distributed form" of his package behaves.
47 $MAKE distdir
48 cd $distdir
49 # He's interested in trying out a VPATH build.
50 mkdir build
51 cd build
52 ../configure
53 # He wants to verify that the rules he's written to rebuild a file
54 # included by configure.ac works also in VPATH builds.
55 rm -f ../foobar.m4
56 $MAKE
57 grep ': foobar was here :' ../configure
58 $MAKE distcheck