From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] systemd: bumped to version 206
Date: Sun, 15 Sep 2013 20:15:15 +0200 [thread overview]
Message-ID: <20130915201515.7f6963f1@skate> (raw)
In-Reply-To: <522C5FE6.6000603@free.fr>
Dear Eric Le Bihan,
On Sun, 08 Sep 2013 13:30:46 +0200, Eric Le Bihan wrote:
> I posted an update of the systemd package. See '[PATCH 1/1] package:
> udev is now provided by systemd or eudev.' In this version, I added
> libgcrypt has a hard dependency for building Systemd. So it builds in
> any case but it forces journal signature.
>
> So, for AM_PATH_LIBGCRYPT to be found, you must have libgcrypt among
> SYSTEMD_DEPENDENCIES, but I'd better have journal signature optional,
> with something like:
>
> ifeq ($(BR2_PACKAGE_SYSTEMD_SIGN_JOURNAL),y)
> SYSTEMD_CONF_OPT += --enable-libgcrypt
> else
> SYSTEMD_CONF_OPT += --disable-libcgrypt
> endif
>
> Is there a way in Buildroot to have a library built for the target and
> installed into 'staging', but not installed on the target (apart for
> pruning the files in post-build.sh)?
No, that's not possible in a clean way.
In this situation, I believe the best option is:
(1) As a temporary measure, take the src/libgcrypt.m4 file from the
libgcrypt sources, and create a patch that adds it to the m4/
directory of systemd sources. This way, regardless of whether
libgcrypt is available or not, the AM_PATH_LIBGCRYPT m4 macro will be
available for autoreconf to use.
(2) As a permanent measure, upstream the other systemd patches so that
ultimately we can get rid of the SYSTEMD_AUTORECONF = YES.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-15 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 16:54 [Buildroot] [PATCH 1/1] systemd: bumped to version 206 Olivier Schonken
2013-09-02 15:04 ` Eric Le Bihan
2013-09-07 16:52 ` Olivier Schonken
2013-09-08 11:30 ` Eric Le Bihan
2013-09-15 18:15 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-30 14:32 eric.le.bihan.dev at free.fr
2013-08-30 14:36 ` Thomas Petazzoni
2013-08-30 16:38 ` eric.le.bihan.dev at free.fr
2013-08-31 11:46 ` Thomas Petazzoni
2013-08-31 20:06 ` Eric Le Bihan
2013-09-01 7:24 ` Thomas Petazzoni
2013-09-02 6:18 ` Arnout Vandecappelle
2013-09-02 9:18 ` Eric Le Bihan
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=20130915201515.7f6963f1@skate \
--to=thomas.petazzoni@free-electrons.com \
--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