Assuming that the libdb development files are installed (db.h), and that
Bash is used,
To compile with libdb: ./waf configure && ./waf
To compile without libdb: ./waf configure --db=no && ./waf
Check if libdbd is linked to compiled shared libraries:
for lib in $(find . -type f -name "*.so"); do readelf -d $lib | grep
NEEDED | grep libdb; done
Marc
Le 2023-08-04 à 13 h 06, Tim a écrit :
On 04/08/2023 04:35, Fons Adriaensen wrote:
Hello all,
I get this error when starting any program using jack (1.9.22):
BDB2034 unable to allocate memory for mutex; resize mutex region
Cannot open DB environment: Cannot allocate memory
This occurs only after the system and jackd have been running for
a long time (weeks or months). Restarting jackd doesn't help,
a reboot is required.
I assume this is related to jackd using a Berkeley Database to
store optional application and port data.
I don't need this functionality, but there seems to be no option
to disable it. Also it seems that BDB is no longer maintained.
Any hints as to how to avoid this problem ?
Ciao,
Interesting. Had no idea BDB was used.
A search of posts revealed that BDB is only used for the jack metadata.
A search in the code revealed this in the WAF file 'wscript':
db = opt.add_auto_option(
'db',
help='Use Berkeley DB (metadata)')
Sure looks like an option !
See if you can access that option via the WAF configuration script.
Tim.
_______________________________________________
Linux-audio-dev mailing list -- linux-audio-dev(a)lists.linuxaudio.org
To unsubscribe send an email to
linux-audio-dev-leave(a)lists.linuxaudio.org