brakmic
commented
3 years ago I have to correct my above post a bit as I ran into this issue with olad.
There was a problem with libmicrohttpd. First, I tried it by disabling the creation of shared libraries with --disable-shared in configure. However, the problem remained as the error now appeared at linking:
After some searching, I found out that my libmicrohttpd, which was installed with brew, was not of "universal" type, so that I uninstalled brew's version and went on to compile it myself.
I checked out the original sources from GNU, configured, compiled and installed them as shown below.
You can also check INSTALL file from there for more info on "universal" variant of this library.
> git clone https://git.gnunet.org/libmicrohttpd.git
> ./configure CC="clang -arch x86_64" \
CXX="clang++ -arch x86_64" \
CPP="clang -E" CXXCPP="clang++ -E" --enable-https CPPFLAGS="-I/usr/local/opt/gnutls/include" LDFLAGS="-L/usr/local/opt/gnutls/lib"
> make
> make installFor HTTPS support your will need to have gnutls installed, which can also be done with brew.
Now I could go back and change the configure from my first posting to this one (I removed all those extra flags regarding libmicrohttpd):
./configure --disable-unittests --disable-gcov --enable-python-libs --enable-http --enable-ja-rule LDFLAGS="-L/usr/local/opt/protobuf/lib -L/usr/local/lib" CPPFLAGS="-I/usr/local/opt/protobuf/include -I/usr/local/include" PYTHON="/usr/local/bin/python3" DOXYGEN_PAPER_SIZE="a4"After make and make install I was able to start olad with HTTP support:
peternewman
danielskeenan
Hi,
I'm a total beginner regarding OLA, but I'd like to share a few things I experienced while trying to compile it under macOS 11.4 Big Sur.
First, I tried to follow the original documentation and compile it with MacPorts, but for some unknown reason MacPorts' selfupdate failed, because during update the script tried to link arm64 binaries with amd_x64. This btw. doesn't seem very 'logical' to me. Why should it try something like this?
But there is brew as an alternative, so that I installed all the packages with it and tried again.
After some trial & error I figured out that for some packages we have to provide additional flags to configure or the compilation would fail at a later stage. I assume that there exist various independent C and C++ compilation targets that expect their configuration flags for certain libraries and their includes.
For example, when compiling with HTTP Server activated, one must provide the same libmicrohttpd paths to C and C++ separately. I am not sure how many of available packages demand such treatment, but if other users run into similar problems, I'd recommend them to check with configure --help if there are flags available for their particular library that's not getting linked by default.
Here's my configure call:
As shown, I am pointing at libmicrohttpd twice:
Also, I had to point at protobuf's includes and libs manually with CPPFLAGS and LDFLAGS
Although the original documentation talks about Python 2 libraries like py27-protobuf and version 2 of the interpreter, I am using Python 3 here. So far I saw no problems of any kind with it.
This is the configure output:
I am sorry, if this is the proper way of sharing my experiences with OLA compilation, but I could not find any markdown document that I could edit to make a PR.
Regards,