jack @1.9.14: error: unknown type name 'DB_ENV'

[GuidoStet (Guido Stet)]

While installing jack a buld failure occurred in JackMetadata.h

:info:build ../common/JackMetadata.h:83:9: error: unknown type name 'DB_ENV'
:info:build         DB_ENV* fDBenv;
:info:build         ^

Xcode version: Xcode 11.3.1

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #60463 which reports the same error with Xcode 11.4.1 in Catalina.

[kencu (Ken)]

Appears to be having an issue with one of the db ports, which it must be picking up if installed. I have db48 installed, and jack ignores it and installs without any trouble:

Checking for header db.h                 : yes 
Checking for library db                  : not found 

JACK 1.9.14 svn revision will checked and eventually updated during build
Maximum JACK clients                        : 64 
Maximum ports per application               : 768 
Install prefix                              : /opt/local 
Library directory                           : /opt/local/lib 
Drivers directory                           : /opt/local/lib/jack 
Build debuggable binaries                   : no 
C compiler flags                            : ['-pipe', '-Os', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64', '-Wall', '-I/opt/local/include', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk'] 
C++ compiler flags                          : ['-pipe', '-Os', '-stdlib=libc++', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64', '-Wall', '-std=gnu++11', '-I/opt/local/include', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk'] 
Linker flags                                : ['-L/opt/local/lib', '-Wl,-headerpad_max_install_names', '-stdlib=libc++', '-Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64'] 
Build with engine profiling                 : no 
Build with 32/64 bits mixed mode            : no 
Build standard JACK (jackd)                 : yes 
Build D-Bus JACK (jackdbus)                 : no 
Autostart method                            : classic 
Build doxygen documentation                 : no 
Enable ALSA driver                          : no 
Enable FireWire driver (FFADO)              : no 
Enable IIO driver                           : no 
Enable Portaudio driver                     : no 
Enable WinMME driver                        : no 
Build with CELT                             : no 
Build Opus netjack2                         : no 
Build with libsamplerate                    : yes 
Build with libsndfile                       : yes 
Build with readline                         : no 
Use systemd notify                          : no 
Use Berkeley DB (metadata)                  : no 

and

$ port -v installed jack
The following ports are currently installed:
  jack @1.9.14_0 (active) platform='darwin 18' archs='x86_64' date='2020-05-10T15:56:38-0700'

[ryandesign (Ryan Carsten Schmidt)]

In 9225059aab401095a9273e1bb6e6c17b0c81528f/macports-ports (master):

jack: Do not try to use BerkeleyDB

Closes: #60461

[kencu (Ken)]

well thanks.

I guess the real question here is why was db48 picked up on the OP's system, and not on mine? By all rights, it should have been:

Checking for header db.h                 : 16:11:06 runner ['/usr/bin/clang++', '-pipe', '-Os', '-stdlib=libc++', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64', '-Wall', '-std=gnu++11', '-DAFTEN=1', '-DHAVE_DOXYGEN=0', '-DHAVE_ALSA=0', '-DHAVE_FIREWIRE=0', '-DHAVE_IIO=0', '-DHAVE_PORTAUDIO=0', '-DHAVE_WINMME=0', '-DHAVE_CELT=0', '-DHAVE_OPUS=0', '-DHAVE_SAMPLERATE=1', '-DHAVE_SNDFILE=1', '-DHAVE_READLINE=0', '-DHAVE_SYSTEMD=0', '../test.cpp', '-c', '-o/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_jack/jack/work/jackaudio-jack2-b54a09b/build/.conf_check_67729c8782f8ba5f45b47efe4c886950/testbuild/test.cpp.1.o', '-I/opt/local/include', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk']
16:11:06 runner ['/usr/bin/clang++', 'test.cpp.1.o', '-o/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_jack/jack/work/jackaudio-jack2-b54a09b/build/.conf_check_67729c8782f8ba5f45b47efe4c886950/testbuild/testprog', '-L/opt/local/lib', '-Wl,-headerpad_max_install_names', '-stdlib=libc++', '-Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64']
yes 
Checking for library db                  : 16:11:06 runner ['/usr/bin/clang++', '-pipe', '-Os', '-stdlib=libc++', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64', '-Wall', '-std=gnu++11', '-DAFTEN=1', '-DHAVE_DOXYGEN=0', '-DHAVE_ALSA=0', '-DHAVE_FIREWIRE=0', '-DHAVE_IIO=0', '-DHAVE_PORTAUDIO=0', '-DHAVE_WINMME=0', '-DHAVE_CELT=0', '-DHAVE_OPUS=0', '-DHAVE_SAMPLERATE=1', '-DHAVE_SNDFILE=1', '-DHAVE_READLINE=0', '-DHAVE_SYSTEMD=0', '-DHAVE_DB_H=1', '../test.cpp', '-c', '-o/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_jack/jack/work/jackaudio-jack2-b54a09b/build/.conf_check_da01aefe8e162d38bb0576dc5f305dc2/testbuild/test.cpp.1.o', '-I/opt/local/include', '-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk']
16:11:06 runner ['/usr/bin/clang++', 'test.cpp.1.o', '-o/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_jack/jack/work/jackaudio-jack2-b54a09b/build/.conf_check_da01aefe8e162d38bb0576dc5f305dc2/testbuild/testprog', '-ldb', '-L/opt/local/lib', '-Wl,-headerpad_max_install_names', '-stdlib=libc++', '-Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk', '-arch', 'x86_64']
not found 

and I will leave that as an exercise for the reader....

[ryandesign (Ryan Carsten Schmidt)]

It's only checking for -ldb. There shouldn't be one provided by MacPorts. Maybe these users had copies of libdb installed in /usr/local/lib.

[kencu (Ken)]

sharp eyes. That must be it.

We should always enable --verbose for waf maybe -- can't tell heads or tails without it -- although even then the feedback from the build system is pretty bad. Maybe there is more available somewhere...