From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 16 May 2016 16:43:36 +0200 Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-13 In-Reply-To: References: <20160514063024.2C7B91025E9@stock.ovh.net> <20160514154655.57ae0bad@free-electrons.com> <20160516131538.70d77f39@free-electrons.com> <20160516145031.7ac19309@free-electrons.com> Message-ID: <20160516164336.3f794389@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Mon, 16 May 2016 15:34:20 +0100, Martin Bark wrote: > > Well, going all the way to autotools or cmake is not really necessary > > to solve these problems. You can just call pkg-config from a Makefile: > > > > LDFLAGS = $(shell pkg-config --libs libgcrypt) > > > > and that's it. No? > > gcrypt has it's owm libgrypt-config so you need something like > > GCRYPT_CONFIG?=libgrypt-config > LDFLAG_GCRYPT=$(shell $(GCRYPT_CONFIG) --libs) > > However, libgcrypt-config --libs always returns -lgcrypt -lgpg-error > so this method does not save you linking against libgpg-error. Given > the iputils Makefile does not currently use anything like pkg-config > or libgcrypt-config i decided on the simpler method. Gaah, OK. Then, yes your patch is the simplest solution. I thought libgcrypt had pkg-config support, but it does not. Will you send a Buildroot patch that backports the upstream-accepted contribution you have made? Thanks a lot! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com