Commit c91715e3 authored by tim@work.mysql.com's avatar tim@work.mysql.com

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

parent 55217d8c
...@@ -1909,12 +1909,16 @@ dnl echo "bdb = '$bdb'; inc = '$bdb_includes', lib = '$bdb_libs'" ...@@ -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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment