summaryrefslogtreecommitdiff
path: root/src/test/isolation/Makefile
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-03-10 00:03:26 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2011-03-10 00:04:05 -0500
commit174f65ab00bb8de0f119a6a60d562b516ba71bba (patch)
treef649991098c4b28941a60ae7f2a5cc50c7a267a6 /src/test/isolation/Makefile
parent76fdee31c4ff74b7eae5965521a85d29381bcaec (diff)
downloadpostgresql-174f65ab00bb8de0f119a6a60d562b516ba71bba.tar.gz
Fix some oversights in distprep and maintainer-clean targets.
At least two recent commits have apparently imagined that a comment in a Makefile stating that something would be included in the distribution tarball was sufficient to make it so. They hadn't bothered to hook into the upper maintainer-clean targets either. Per bug #5923 from Charles Johnson, in which it emerged that the 9.1alpha4 tarballs are short a few files that should be there.
Diffstat (limited to 'src/test/isolation/Makefile')
-rw-r--r--src/test/isolation/Makefile6
1 files changed, 4 insertions, 2 deletions
diff --git a/src/test/isolation/Makefile b/src/test/isolation/Makefile
index 82ce248a07..0f709a1e3c 100644
--- a/src/test/isolation/Makefile
+++ b/src/test/isolation/Makefile
@@ -29,7 +29,7 @@ all: isolationtester pg_isolation_regress
isolationtester: $(OBJS) | submake-libpq submake-libpgport
$(CC) $(CFLAGS) $(OBJS) $(libpq_pgport) $(LDFLAGS) $(LDFLAGS_EX) $(LIBS) -o $@$(X)
-distprep: specparse.c
+distprep: specparse.c specscanner.c
# There is no correct way to write a rule that generates two files.
# Rules with two targets don't have that meaning, they are merely
@@ -58,7 +58,9 @@ ifdef FLEX
else
@$(missing) flex $< $@
endif
-# specparse.c is in the distribution tarball, so is not cleaned here
+
+# specparse.c and specscanner.c are in the distribution tarball,
+# so do not clean them here
clean distclean:
rm -f isolationtester$(X) pg_isolation_regress$(X) $(OBJS) isolation_main.o
rm -f pg_regress.o