On Sat, 2014-11-01 at 14:28 +0100, Hans Witvliet wrote:

Hi all,

It seems that I hit a snag, that as a noob I am not able to solve. Let me first explain that, until now, I only used the web-interface.

I cloned one of the existing packages with succes: https://build.opensuse.org/package/show/home:testhans:network:network:vpn/op... As you can see, they all build successfully, even 13.2 and sles12

So i dared to try to build the latest release (not to be found anywhere else on the obs) https://build.opensuse.org/package/show/home:testhans:network:network:vpn/op... After some tweaking the spec-file, some build succeeded But those using systemd failed.

Initially, i assumed PEBKAC, but next I checked upstream, and they said if i used ./configure with --enable-systemd all should be fine Next the dev's wrote because it used to work, and still works for non-systemd, the original author of previous patch should correct it.

However, that author blames the build-environment, the obs. I'll forward his conclusion next to the list...

========================================================================================== From: Witvliet, J, DMO/OPS/I&S/HIN Sent: woensdag 29 oktober 2014 17:41 To: 'openvpn-users@lists.sourceforge.net' Subject: RE [Openvpn-users] 2.3.5 - systemd

Indeed, as David said: No package 'libsystemd-daemon' found OTOH, it should be enabled… (excerpt from the spec:)

…

%configure \ --enable-iproute2 \ --enable-x509-alt-username \ --enable-password-save \ %if %{with_systemd} --enable-systemd \ %endif --enable-plugins \ --enable-plugin-down-root \ --enable-plugin-auth-pam \ --with-lzo-headers=%_includedir/lzo \ CFLAGS="$CFLAGS $(getconf LFS_CFLAGS) -fPIE $PLUGIN_DEFS" \

And it seems to be “turned-on”, in the log: [ 46s] systemd-210-44.1 But some lines further: [ 71s] checking for libsystemd... no

[ 71s] checking for libsystemd... no [ 71s] configure: error: Package requirements (libsystemd-daemon) were not met: [ 71s] [ 71s] No package 'libsystemd-daemon' found

My first assumption was that on this particular build-node, system was not found, But that makes no sense, as 2.3.4 builds OK, with or without system on OS12.2, OS12.3, OS13.1, OS13.2, OSFactory, SLES11SP3 and SLES12 Have to dive a bit deeper, I guess.

Hans

°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°

-----Original Message-----

Hi,

On Wed, Oct 29, 2014 at 03:41:53PM +0100, J.Witvliet@mindef.nl wrote:

...

Does that imply any required-change during building? I tried to build on a remote build-farm, and much to my surprise only

the targets (SLES12, openSUSE_13.2, openSUSE_13.1) with systemd fails, while others like sles11sp3 and openSUSE_12.2 succeed.

Well, if you use --enable-systemd, it should better be there (as it will now try to link to it). If you do not use that, it MUST NOT fail building, whether or not systemd is there.

So - how are you calling configure, what is the error message?

gert