From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-08
Date: Mon, 9 Jun 2014 23:10:36 +0200 [thread overview]
Message-ID: <20140609211036.GA10459@ned> (raw)
In-Reply-To: <20140609063010.9CF93101624@stock.ovh.net>
Hi!
On Mon, Jun 09, 2014 at 08:30:10AM +0200, Thomas Petazzoni wrote:
> arm | systemd-213 | NOK | http://autobuild.buildroot.net/results/1524d346fa17749e2ae62e063b9cfdd0de95c76a/
>
D'Oh! AM_PATH_LIBGCRYPT comes haunting us again!
This problem spawned a discussion in the past [1], and was temporarily solved,
as the call to autoreconf was removed [2].
Let's see:
- systemd upstream says gcrypt is a dependency, but will remove the m4 macro if gcrypt
moves to pkg-config [3].
- gcrypt upstream does not like pkg-config [4].
- Some other embedded distros have patched gcrypt to provide support for
pkg-config [5] [6].
- OpenEmbedded added gcrypt as dependency [7].
- We are stuck with autoreconf, as it is needed to solve the `ln --relative`
issue via a patch, which will not be accepted by upstream [8].
Adding libgcrypt as a dependency is a no-go, as the end user gets some
unneedded stuff in its target rootfs. So we're left with the solution of
adding libgcrypt.m4 to m4 directory of systemd. Though this solution was
considered "temporary", can it now be accepted as "definitive"? [9]
Best regards,
ELB
[1] http://lists.busybox.net/pipermail/buildroot/2013-September/077768.html
[2] http://git.buildroot.net/buildroot/commit/?id=34291708d077e5626453378df133a683c9606bef
[3] http://lists.freedesktop.org/archives/systemd-bugs/2012-September/000161.html
[4] http://lists.gnupg.org/pipermail/gcrypt-devel/2007-February/001109.html
[5] http://git.yoctoproject.org/cgit/cgit.cgi/poky/plain/meta/recipes-support/libgcrypt/files/add-pkgconfig-support.patch
[6] http://git.overlays.gentoo.org/gitweb/?p=proj/embedded-cross.git;a=blob;f=dev-libs/libgcrypt/files/libgcrypt-pkgconfig-support.patch
[7] http://git.yoctoproject.org/cgit/cgit.cgi/poky/plain/meta/recipes-core/systemd/systemd_213.bb
[8] https://www.mail-archive.com/systemd-devel at lists.freedesktop.org/msg18966.html
[9] http://lists.busybox.net/pipermail/buildroot/2013-September/078232.html
next prev parent reply other threads:[~2014-06-09 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-08 Thomas Petazzoni
2014-06-09 10:07 ` Yann E. MORIN
2014-06-09 10:11 ` Thomas Petazzoni
2014-06-09 10:15 ` Yann E. MORIN
2014-06-09 12:04 ` François Perrad
2014-06-09 12:19 ` Yann E. MORIN
2014-06-09 21:10 ` Eric Le Bihan [this message]
2014-06-11 8:56 ` Thomas Petazzoni
2014-06-11 21:04 ` Eric Le Bihan
2014-06-11 21:13 ` Yann E. MORIN
2014-06-11 21:47 ` Eric Le Bihan
2014-06-11 21:54 ` Yann E. MORIN
2014-06-12 7:08 ` Thomas Petazzoni
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=20140609211036.GA10459@ned \
--to=eric.le.bihan.dev@free.fr \
--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