#40 building on OpenBSD

[Adam Thompson]

Mostly just FYI at this point...

I'm trying to compile it on OpenBSD 6.2-current, and it hasn't been super smooth, regardless of whether I use the system compiler (clang 4.0.0) or gcc 4.2.1 from ports.

So far:
1. git clone https://git.code.sf.net/p/isync/isync isync-isync
2. cd isync-isync
3. export AUTOCONF_VERSION=2.69
4. export AUTOMAKE_VERSION=1.15
5. export CC=cc
6. export LDFLAGS="-L/usr/local/lib/db4 -L/usr/local/lib/eopenssl"
7. export CPPFLAGS="-I/usr/local/include/db4 -I/usr/local/include/eopenssl"
8. ./autogen.sh
9. make
10. make install
11. export LD_LIBRARY_PATH=/usr/local/lib/db4:/usr/local/lib/eopenssl"

If I don't force CC to "cc" instead of "gcc", I get some errors along the lines of "error: #pragma GCC diagnostic not allowed inside functions" in util.c. Which is kind of funny, that gcc can't handle its own pragmas but clang can...
If I don't force the DB4 version from ports, the base system version of db is apparently too old.
If I don't force the use of OpenSSL 1.0.2 from ports, the base system's version of LibreSSL lacks two functions:

socket.o: In function verify_cert_host': socket.c:(.text+0x4fe): undefined reference toX509_OBJECT_get0_X509'
socket.o: In function init_ssl_ctx': socket.c:(.text+0x6f6): undefined reference toX509_STORE_get0_objects'

So other than that, it builds. Haven't tested it much yet.
In theory, all these things could/should be handled inside autoconf (especially the OpenSSL/LibreSSL difference, IMHO), but autoconf scares me so I'm not about to propose patches, sorry!

[Oswald Buddenhagen]

that gcc version is incredibly old.
anyway, 094af8720cae202f76f8b1c46d47a40361a7ad8b was supposed to fix that incompatibility.

the libressl topic was raised on the mailing list, but the contributor did not follow through with it (i'm not positive about the versions and compatibility levels; which #defines to check for).

bdb is properly version-checked (well, at least i tried :D), so you're just stating the need for action on your side, right?

[Adam Thompson]

I don't know how to handle the DB version issue, tbh... or even if it needs to be handled. But at least the steps necessary to make the thing build are now documented somewhere.

[Oswald Buddenhagen]

a bunch of openbsd fixes were contributed and released with v1.3.1, so i'm assuming this can be closed.