Sorry Gert, In my previous mail I had both log and spec attached, which the list bounced back (size) I am calling it via the web/interface of
https://build.opensuse.org/package/show/home:testhans:network:network:vpn/openvpn-next (before mentioning it, I only had some suse/repo´s enabled, I left redhat/centos/fedora/debian/Ubuntu off for the moment) Hans From: Witvliet, J, DMO/OPS/I&S/HIN Sent: woensdag 29 oktober 2014 17:41 To: '[email protected]' Subject: RE [Openvpn-users] 2.3.5 - systemd Indeed, as David said: No package 'libsystemd-daemon' found OTOH, it should be enabled... (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----- From: Gert Doering [mailto:[email protected]] Sent: woensdag 29 oktober 2014 17:03 To: Witvliet, J, DMO/OPS/I&S/HIN Cc: [email protected]<mailto:[email protected]> Subject: Re: [Openvpn-users] 2.3.5 - systemd Hi, On Wed, Oct 29, 2014 at 03:41:53PM +0100, [email protected]<mailto:[email protected]> 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 -- ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
openvpn.spec
Description: openvpn.spec
------------------------------------------------------------------------------
_______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
