Skip to contentSkip to conversation

systemd: bumped to version 206

PATCH New Olivier Schonken 3 participants 5 messages Sep 1, 2013 – Sep 15, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 systemd: bumped to version 206

Hi Eric

Great work on bumping systemd to version 206.

I have started to test building the new version(Using Codesourcery for ARM). One thing I noticed is that with the SYSTEMD_AUTORECONF=YES, autotools complains about undefined macro AM_PATH_LIBGCRYPT if libgcrypt or libgcrypt-devel is not present on the build system. Not sure how to go about pleasing autotools without the additional system dependency. Maybe someone on the buildroot mailing list will know...?

Regards
Olivier Schonken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130901/bd235995/attachment.html>

#1 lore raw

PATCH 1/1 systemd: bumped to version 206

Quoted 6 lines · Olivier Schonken

I have started to test building the new version(Using Codesourcery for ARM). One thing I noticed is that with the SYSTEMD_AUTORECONF=YES, autotools complains about undefined macro AM_PATH_LIBGCRYPT if libgcrypt or libgcrypt-devel is not present on the build system. Not sure how to go about pleasing autotools without the additional system dependency. Maybe someone on the buildroot mailing list will know...?

I removed libgcrypt11-dev from my development machine and built an image for QEMU arm-versatile using Code Sourcery 2013.05, but I have not seen this issue. Can you send me a log file of the build with the error?

#2 lore raw

PATCH 1/1 systemd: bumped to version 206

Hi Eric

Attached is the systemd build log for failure with AUTORECONF enabled for systemd.

I first tried to apply your patch to buildroot 2013.08. Only when I comment out 'SYSTEMD_AUTORECONF = YES' and not apply 'systemd-0005-core-fixed-ms-sscanf-modifier-not-being-available-in.patch' do I get it to build successfully.

patch 'systemd-0005-core-fixed-ms-sscanf-modifier-not-being-available-in.patch' causes below error because of configure.ac being updated by patch. /home/olivier/Buildroot-test/output/build/systemd-206/build-aux/missing:
line 81: aclocal-1.13: command not found
WARNING: 'aclocal-1.13' is missing on your system.
You should only need it if you modified 'acinclude.m4' or 'configure.ac' or m4 files included by 'configure.ac'. The 'aclocal' program is part of the GNU Automake package:
<http://www.gnu.org/software/automake>
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
<http://www.gnu.org/software/autoconf>
<http://www.gnu.org/software/m4/>
<http://www.perl.org/>
make[1]: *** [aclocal.m4] Error 127

Regards
Olivier Schonken

Quoted 9 lines · Eric Le Bihan
Quoted 3 lines · Olivier Schonken

I have started to test building the new version(Using Codesourcery for ARM). One thing I noticed is that with the SYSTEMD_AUTORECONF=YES, autotools complains about undefined macro AM_PATH_LIBGCRYPT if libgcrypt

or

Quoted 3 lines

libgcrypt-devel is not present on the build system. Not sure how to go about pleasing autotools without the additional system dependency. Maybe someone on the buildroot mailing list will know...?

Quoted 6 lines

I removed libgcrypt11-dev from my development machine and built an image for
QEMU arm-versatile using Code Sourcery 2013.05, but I have not seen this issue.
Can you send me a log file of the build with the error?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130907/305dfcdc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: systemd-206.log
Type: application/octet-stream
Size: 1006 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130907/305dfcdc/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: master-config
Type: application/octet-stream
Size: 30789 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130907/305dfcdc/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2013.08-config
Type: application/octet-stream
Size: 30306 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130907/305dfcdc/attachment-0005.obj>

#3 lore raw

PATCH 1/1 systemd: bumped to version 206

Le 07/09/2013 18:52, Olivier Schonken a ?crit :

Quoted 4 lines

I first tried to apply your patch to buildroot 2013.08. Only when I comment out 'SYSTEMD_AUTORECONF = YES' and not apply 'systemd-0005-core-fixed-ms-sscanf-modifier-not-being-available-in.patch' do I get it to build successfully.

Yep, The 'patch systemd-0005-core-fixed-ms-sscanf-modifier-not-being-available-in.patch' replaces the use of the dynamic allocation conversion modifier %m when using uClibc, as it is not implemented in it. You manage to build it because you are using the Code Sourcery toolchain, which comes with glibc.

I made a mistake saying I had not seen the issue after removing libgcrypt11-dev from my development machine: I had forgotten to perform a proper clean of my environment ("D'Oh!").

See https://github.com/elebihan/buildroot/blob/udev-provider/ for a Systemd on ARM with external toolchain configuration (configs/elebihan_demo_systemd_arm_defconfig).

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)?

#4 lore raw

PATCH 1/1 systemd: bumped to version 206

Dear Eric Le Bihan,

Quoted 10 lines · Eric Le Bihan

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)

Quoted 8 lines
	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

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com