[OE-core] [PATCH 12/14] meson: update to 0.46.0 -- broke systemd on qemuppc

[Alexander Kanavin]

The order of arguments to compiler and linker matters. I remember that
when converting recipes from autotools to meson, I had to fix the
order to be exactly same, or some weird, arch-specific issues arose.
Can you check the precise command line in both working and broken
case, and what has changed there?

Alex

2018-06-19 12:59 GMT+03:00 Burton, Ross <ross.burton at intel.com>:
> On 19 June 2018 at 06:03, Randy MacLeod <randy.macleod at windriver.com> wrote:
>> It seems that this meson update broke systemd on qemuppc.
>> I'll look into it a more tomorrow but below is what I know so far.
>> It looks like the libsystemd-shared.so size increased by 18% despite
>> the build flags being the same!
>>
>> Despite my IRC handle, I'm a meson newbie so any tips will
>> be appreciated. I'll work on getting meson/ninja to be more
>> verbose tomorrow to track down what really changed.
>>
>>
>> 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
>>
>> or in some cases:
>>
>>   systemd[1]: \
>>      unhandled signal 11 at b804b784 nip 0070d184 lr 008ee1ac code 1
>>   Kernel panic - not syncing: \
>>      Attempted to kill init! exitcode=0x0000000b
>> when running:
>>     runqemu slirp nographic qemuppc ext4
>>
>> The error only appears when using the distro poky-lsb
>> or a security template in the WR builds.
>
> Khem suggests that this is due to the new gcc and PIE on PPC being
> bust, but even after passing no-pie this is still happening for me.
>
> Ross