Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>, Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 12/14] meson: update to 0.46.0 -- broke systemd on qemuppc
Date: Tue, 19 Jun 2018 16:06:00 -0400	[thread overview]
Message-ID: <4cfebd9d-73bb-613d-65e5-ca2abfe86eb7@windriver.com> (raw)
In-Reply-To: <CAJTo0LY-xmzar7jRYeboJJ5krAULqPMdwpS7hxgbC8m52uTEew@mail.gmail.com>

On 06/19/2018 03:49 PM, Burton, Ross wrote:
> On 19 June 2018 at 17:00, Khem Raj <raj.khem@gmail.com> wrote:
>>>> I recently started testing qemuppc by booting
>>>> core-image-minimal with systemd as init. It fails with:
>>>>
>>>>      /sbin/init: error while loading shared libraries:
>>>>         /lib/systemd/libsystemd-shared-237.so: R_PPC_REL24 relocation at
>>>> 0x0054574c for symbol `strlen' out of range
>>
>>
>> This would also indicate that libsystemd is probably missing -fPIC during
>> compile, can you check the compiler cmdline passed when building on of .o
>> files that gets includes in libsystemd.
> 
> [1/1423] powerpc-poky-linux-gcc -m32 -mhard-float -mcpu=7400 -mno-spe
> -fstack-protector-strong -D_FORTIFY_SOURCE=2 -no-pie -fno-PIE
> --sysroot=/data/poky-tmp/master/work/ppc7400-poky-linux/systemd/1_237-r0/recipe-sysroot
> -Isrc/libsystemd/src@libsystemd@@systemd@sta -Isrc/libsystemd
> -I../git/src/libsystemd -Isrc/basic -I../git/src/basic -Isrc/shared
> -I../git/src/shared -Isrc/systemd -I../git/src/systemd -Isrc/journal
> -I../git/src/journal -Isrc/resolve -I../git/src/resolve -Isrc/timesync
> -I../git/src/timesync -Isrc/login -I../git/src/login -Isrc/udev
> -I../git/src/udev -Isrc/libudev -I../git/src/libudev -Isrc/core
> -I../git/src/core -I../git/src/libsystemd/sd-bus
> -I../git/src/libsystemd/sd-device -I../git/src/libsystemd/sd-hwdb
> -I../git/src/libsystemd/sd-id128 -I../git/src/libsystemd/sd-netlink
> -I../git/src/libsystemd/sd-network -Isrc/libsystemd-network
> -I../git/src/libsystemd-network -I. -I../git/
> -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99
> -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs
> -Wold-style-definition -Wpointer-arith -Winit-self
> -Wdeclaration-after-statement -Wfloat-equal
> -Wsuggest-attribute=noreturn -Werror=missing-prototypes
> -Werror=implicit-function-declaration -Werror=missing-declarations
> -Werror=return-type -Werror=incompatible-pointer-types
> -Werror=format=2 -Wstrict-prototypes -Wredundant-decls
> -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels
> -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time
> -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option
> -fno-strict-aliasing -fvisibility=hidden -fstack-protector
> -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE
> -Wno-unused-parameter -Wno-missing-field-initializers
> -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull
> -Werror=shadow -ffunction-sections -fdata-sections -include config.h

> -fPIC
Hey Ross ^^^

> -pthread -fvisibility=default -m32 -mhard-float -mcpu=7400
> -mno-spe -fstack-protector-strong -D_FORTIFY_SOURCE=2 -no-pie -fno-PIE
> --sysroot=/data/poky-tmp/master/work/ppc7400-poky-linux/systemd/1_237-r0/recipe-sysroot
> -O2 -pipe -g -feliminate-unused-debug-types
> -fdebug-prefix-map=/data/poky-tmp/master/work/ppc7400-poky-linux/systemd/1_237-r0=/usr/src/debug/systemd/1_237-r0
> -fdebug-prefix-map=/data/poky-tmp/master/work/ppc7400-poky-linux/systemd/1_237-r0/recipe-sysroot=
> -fdebug-prefix-map=/data/poky-tmp/master/work/ppc7400-poky-linux/systemd/1_237-r0/recipe-sysroot-native=
> -MD -MQ 'src/libsystemd/src@libsystemd@@systemd@sta/sd-utf8_sd-utf8.c.o'
> -MF 'src/libsystemd/src@libsystemd@@systemd@sta/sd-utf8_sd-utf8.c.o.d'
> -o 'src/libsystemd/src@libsystemd@@systemd@sta/sd-utf8_sd-utf8.c.o' -c
> ../git/src/libsystemd/sd-utf8/sd-utf8.c
> 
> You're right, no -fPIC.  

fPIC is there, look again!
I just send my reply as your email arrived.

> The no-PIE flags are coming from
> SECURITY_NOPIE_CFLAGS.  I'm guessing security_flags is interacting
> badly with ppc again?

Right and I could just add:
    SECURITY_CFLAGS_pn-systemd_powerpc = "${SECURITY_NO_PIE_CFLAGS}"
in meta/conf/distro/include/security_flags.inc but
I wanted to be sure that I understood why such a change is needed.
The meson update shouldn't break things...

../Randy

> 
> Ross
> 


-- 
# Randy MacLeod
# Wind River Linux


  reply	other threads:[~2018-06-19 20:07 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 12:32 [PATCH 01/14] gobject-introspection: update to 1.56.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 02/14] ffmpeg: update to 4.0 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 03/14] vala: update to 0.40.4 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 04/14] libfm: update to 1.3.0.2 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 05/14] pcmanfm: update to 1.3.0 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 06/14] epiphany: update to 3.28.1.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 07/14] ca-certificates: update to 20180409 Alexander Kanavin
2018-05-08  7:47   ` Richard Purdie
2018-05-08 11:30     ` Alexander Kanavin
2018-05-04 12:32 ` [PATCH 08/14] gnome-desktop3: update to 3.28.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 09/14] libwebp: update to 1.0.0 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 10/14] procps: update to 3.3.14 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 11/14] webkitgtk: update to 2.20.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 12/14] meson: update to 0.46.0 Alexander Kanavin
2018-05-04 12:43   ` Nirbheek Chauhan
2018-06-19  5:03   ` [PATCH 12/14] meson: update to 0.46.0 -- broke systemd on qemuppc Randy MacLeod
2018-06-19  5:17     ` Nirbheek Chauhan
2018-06-19  9:59     ` Burton, Ross
2018-06-19 12:01       ` Alexander Kanavin
2018-06-19 16:00       ` Khem Raj
2018-06-19 19:49         ` Burton, Ross
2018-06-19 20:06           ` Randy MacLeod [this message]
2018-06-19 20:22             ` Burton, Ross
2018-06-19 20:01         ` Randy MacLeod
2018-06-19 20:09           ` Alexander Kanavin
2018-06-19 20:24             ` Nirbheek Chauhan
2018-06-19 23:02               ` Burton, Ross
2018-06-19 23:13                 ` Burton, Ross
2018-06-19 23:39                   ` Khem Raj
2018-05-04 12:32 ` [PATCH 13/14] ifupdown: correct the repository location Alexander Kanavin
2018-05-04 12:32 ` [PATCH 14/14] babeltrace: switch over to git Alexander Kanavin
2018-05-04 12:46   ` Paulo Neves
2018-05-04 12:48     ` Alexander Kanavin
2018-05-04 12:55     ` Burton, Ross
2018-05-04 13:12       ` Paulo Neves
2018-05-04 13:30         ` Scott Rifenbark
2018-05-04 19:51   ` Martin Jansa
2018-05-07 10:17     ` Alexander Kanavin
2018-05-08  9:25       ` Burton, Ross
2018-05-08 15:18         ` Michael Halstead

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=4cfebd9d-73bb-613d-65e5-ca2abfe86eb7@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@intel.com \
    /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