On Tue, Jun 19, 2018 at 4:13 PM Burton, Ross wrote:
>
> Okay, odd. Hacked in a few compile fixes and now systemd v237 fails
> to build with Meson git master:
>
> | FAILED: libsystemd.so.0.21.0
> | powerpc-poky-linux-gcc -m32 -mhard-float -mcpu=7400 -mno-spe
> -fstack-protector-strong
Okay, odd. Hacked in a few compile fixes and now systemd v237 fails
to build with Meson git master:
| FAILED: libsystemd.so.0.21.0
| powerpc-poky-linux-gcc -m32 -mhard-float -mcpu=7400 -mno-spe
-fstack-protector-strong -D_FORTIFY_SOURCE=2 -no-pie -fno-PIE
On 19 June 2018 at 21:24, Nirbheek Chauhan wrote:
> On Wed, Jun 20, 2018 at 1:39 AM Alexander Kanavin
> wrote:
>> FWIW, I did fix a similar (or maybe even same) issue with this patch:
>>
On Wed, Jun 20, 2018 at 1:39 AM Alexander Kanavin
wrote:
> FWIW, I did fix a similar (or maybe even same) issue with this patch:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/meson/meson/0001-Linker-rules-move-cross_args-in-front-of-output_args.patch
>
> It's
On 19 June 2018 at 21:06, Randy MacLeod wrote:
>> -fPIC
>
> Hey Ross ^^^
> fPIC is there, look again!
> I just send my reply as your email arrived.
I'm clearly going compiler flag blind...
--
___
Openembedded-core mailing list
2018-06-19 22:01 GMT+02:00 Randy MacLeod :
> The compiler flag order difference is too large for a civilized
> email so it's here:
> diff -Naur: https://pastebin.com/pWSzDm5W
> sdiff -t : https://pastebin.com/5BX8QvNs
>
>
> When linking libsystemd-shared-237.so the location of the:
>
On 06/19/2018 03:49 PM, Burton, Ross wrote:
On 19 June 2018 at 17:00, Khem Raj 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:
Alex wrote:
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
On 19 June 2018 at 17:00, Khem Raj 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
>>>
On 6/19/18 2:59 AM, Burton, Ross wrote:
On 19 June 2018 at 06:03, Randy MacLeod 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
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
On 19 June 2018 at 06:03, Randy MacLeod 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
On Tue, Jun 19, 2018 at 10:34 AM Randy MacLeod
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!
>
>
On 05/04/2018 08:32 AM, Alexander Kanavin wrote:
Rebase a couple of patches
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
14 matches
Mail list logo
