From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] systemd: fix AM_PATH_LIBGCRYPT not found
Date: Fri, 13 Jun 2014 14:23:04 +0200 [thread overview]
Message-ID: <871tutf17b.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1402521982-31067-1-git-send-email-eric.le.bihan.dev@free.fr> (Eric Le Bihan's message of "Wed, 11 Jun 2014 23:26:22 +0200")
>>>>> "Eric" == Eric Le Bihan <eric.le.bihan.dev@free.fr> writes:
> This patch installs a copy of libgcrypt.m4 from the libgcrypt source tarball
> to systemd m4 directory.
> Libgcrypt uses a custom m4 macro and not pkg-config to check if the
> development files are available. Though libgcrypt support is optional in
> systemd, this macro should be available whenever autoreconf is used,
> otherwise the re-configuration will fail with:
> configure.ac:616: warning: macro 'AM_PATH_LIBGCRYPT' not found in library
> The call to autoreconf is required, as it is needed by the patch which
> solves the `ln --relative` issue.
> As asking the user to install the development package of libgcrypt on
> the host machine or adding libgcrypt as a build dependency to systemd is
> not acceptable, the required file is added to the m4 directory.
> Fixes: http://autobuild.buildroot.net/results/1524d346fa17749e2ae62e063b9cfdd0de95c76a/
> Fixes: http://autobuild.buildroot.net/results/10bcd92437eaa27eb61f8281c93efcb53d555e35/
> Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-06-13 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 21:26 [Buildroot] [PATCH 1/1] systemd: fix AM_PATH_LIBGCRYPT not found Eric Le Bihan
2014-06-11 21:32 ` Yann E. MORIN
2014-06-12 7:15 ` Thomas Petazzoni
2014-06-12 17:05 ` Yann E. MORIN
2014-06-13 12:23 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tutf17b.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox