1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Make configure always generate a dummy bdb/build_unix/db.h file. Ugh.

Browse Source 
configure.in:
  Always make a dummy bdb/build_unix/db.h, because the
  dependencies are included in the Makefile, which gets
  distributed, so this file has to exist.  This is ugly.
This commit is contained in:
unknown 2001-03-08 20:06:08 +01:00
parent 8303fd97d5
commit 50e6e06bd7
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
configure.in
View File

@ -1909,12 +1909,16 @@ dnl echo "bdb = '$bdb'; inc = '$bdb_includes', lib = '$bdb_libs'"
else else
if test -d bdb; then : if test -d bdb; then :
else else
mkdir bdb && mkdir bdb/build_unix && cat <<EOF > bdb/build_unix/db.h mkdir bdb && mkdir bdb/build_unix
fi
if test -r bdb/build_unix/db.h; then :
else
cat <<EOF > bdb/build_unix/db.h
This file is a placeholder to fool make. The way that automake This file is a placeholder to fool make. The way that automake
handles 'make distcheck' (calling the VPATH configure with different and GNU make work together causes some files to depend on this
options from the original configure) causes make to think that mysqld header, even if we're not building with Berkeley DB.
depends on this file, even though Berkeley DB isn't being used.
Obviously, if this file *is* used, it'll break and hopefully we can find Obviously, if this file *is* used, it'll break and hopefully we can find
out why this file was generated by $(top_srcdir)/configure instead of out why this file was generated by $(top_srcdir)/configure instead of