Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-05 Thread Simon McVittie
On 05/11/13 16:45, Colin Walters wrote: > On Tue, 2013-11-05 at 16:39 +, Colin Guthrie wrote: >> Does this not increase the danger that a "make dist" run on a machine >> without those deps installed would result in a "configure" script that >> accidentally doesn't have support for those feature

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-05 Thread Colin Walters
On Tue, 2013-11-05 at 16:39 +, Colin Guthrie wrote: > Does this not increase the danger that a "make dist" run on a machine > without those deps installed would result in a "configure" script that > accidentally doesn't have support for those features? Or do I > misunderstand how the m4_ifdef

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-05 Thread Colin Guthrie
'Twas brillig, and Colin Walters at 05/11/13 15:33 did gyre and gimble: > On Tue, 2013-11-05 at 16:22 +0100, Lennart Poettering wrote: > >> This pretty much like all other projects >> handle this, too. > > Just for what it's worth in a number of parts of GNOME we started using > m4_ifdef more con

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-05 Thread Colin Walters
On Tue, 2013-11-05 at 16:22 +0100, Lennart Poettering wrote: > This pretty much like all other projects > handle this, too. Just for what it's worth in a number of parts of GNOME we started using m4_ifdef more consistently. For example: https://git.gnome.org/browse/glib/tree/configure.ac?id=f49

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-05 Thread Lennart Poettering
On Tue, 05.11.13 15:44, Djalal Harouni (tix...@opendz.org) wrote: > > On Mon, Nov 04, 2013 at 10:28:20PM +0100, Jan Engelhardt wrote: > > > > On Monday 2013-11-04 13:01, Lennart Poettering wrote: > > >On Sat, 02.11.13 02:11, Djalal Harouni (tix...@opendz.org) wrote: > > >> > > >>I'm building fr

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-05 Thread Djalal Harouni
On Mon, Nov 04, 2013 at 10:28:20PM +0100, Jan Engelhardt wrote: > > On Monday 2013-11-04 13:01, Lennart Poettering wrote: > >On Sat, 02.11.13 02:11, Djalal Harouni (tix...@opendz.org) wrote: > >> > >>I'm building from git tree, and I've noticed that systemd autogen.sh > >>will fail if the libgcr

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-04 Thread Jan Engelhardt
On Monday 2013-11-04 13:01, Lennart Poettering wrote: >On Sat, 02.11.13 02:11, Djalal Harouni (tix...@opendz.org) wrote: >> >>I'm building from git tree, and I've noticed that systemd autogen.sh >>will fail if the libgcrypt and its headers are missing. > >This is expected that way. If you build

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-04 Thread Lennart Poettering
On Sat, 02.11.13 02:11, Djalal Harouni (tix...@opendz.org) wrote: > Hi list, > > I'm doing some systemd testing on clean machines. I'm building from git > tree, and I've noticed that systemd autogen.sh will fail if the > libgcrypt and its headers are missing, this will produce a buggy > configure

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-01 Thread Djalal Harouni
List please hold on these patch! It seems that AM_PATH_LIBGCRYPT will also define LIBGCRYPT_LIBS which is used to link again libgcrypt and other libraries related to libgcrypt. My bad, this current patch will not fix the problem! I guess that we are stuck with this :-/ until gcrypt converts to p

[systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-01 Thread Djalal Harouni
Hi list, I'm doing some systemd testing on clean machines. I'm building from git tree, and I've noticed that systemd autogen.sh will fail if the libgcrypt and its headers are missing, this will produce a buggy configure script. The error messages were not clear, I did lost time debugging... :-/