View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005722||GNUnet||build process||public||2019-05-13 16:11||2019-07-30 19:52|
|Reporter||Florian Dold||Assigned To|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0005722: --with-libgcrypt-prefix does not work properly|
|Description||When configuring GNUnet with --with-libgcrypt-prefix=$HOME/local, the configure step fails, even though libgcrypt is installed into that prefix properly. The supposed problem is a mismatch between the header version and library version of libgcrypt.|
It turns out that this is because the conftest program is *not* executed with the correct LD_LIBRARY_PATH. When executing, ldd picks up the distributions libgcrypt.
Thus when compiling with --with-libgcrypt-prefix=$PREFIX, you also have to manually put $PREFIX into LD_LIBRARY_PATH, or otherwise ./configure fails with an obscure error message.
Instead, the configure script should execute the conftest in the right environment, respecting the prefix.
|Tags||No tags attached.|
Is --with-libgcrypt the only affected switch here?
I have no system wide ldd config, but I can assume that this is not exclusive to gcrypt and we might want to double check the other lines where we use it.
||unassigning, pick up if you have a proposed fix.|
|2019-05-13 16:11||Florian Dold||New Issue|
|2019-05-13 18:27||ng0||Note Added: 0014386|
|2019-05-26 20:19||ng0||Assigned To||=> ng0|
|2019-05-26 20:19||ng0||Status||new => assigned|
|2019-05-26 20:19||ng0||Relationship added||has duplicate 0005736|
|2019-07-30 19:52||ng0||Note Added: 0014760|
|2019-07-30 19:52||ng0||Assigned To||ng0 =>|