mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: Felix Mellmann <flix.ptxdist@benfm.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] e2fsprogs: possibly broken when using OSELAS.Toolchain 2022.10.0
Date: Sun, 13 Nov 2022 22:07:48 +0100	[thread overview]
Message-ID: <91afd9cd-62ba-4418-d1bd-a2b15f188ebe@t2data.com> (raw)
In-Reply-To: <35a025e1-9b3b-01f5-6776-db2ce5554208@benfm.de>

Hi Felix,

On 11/13/22 18:32, Felix Mellmann wrote:
> Hi everyone,
> 
> I've just run into a linker problem when building e2fsprogs 1.46.5 using 
> OSELAS.Toolchain 2022.10.0 (arm-v7a-linux-gnueabihf):
> 
> 
> -------------------------
> target: e2fsprogs.compile
> -------------------------
> 
> make: Entering directory 
> '/PTXdist/BSP/platform-imx6/build-target/e2fsprogs-1.46.5'
> cd ./util ; make subst
> make[1]: Entering directory 
> '/PTXdist/BSP/platform-imx6/build-target/e2fsprogs-1.46.5/util'
>      CREATE dirpaths.h
>      CC subst.c
>      LD subst
> lto1: fatal error: bytecode stream in file 'subst.o' generated with LTO 
> version 11.2 instead of the expected 11.3
> compilation terminated.
> lto-wrapper: fatal error: /usr/bin/gcc returned 1 exit status
> compilation terminated.
> /usr/bin/ld: error: lto-wrapper failed
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:369: subst] Error 1
> make[1]: Leaving directory 
> '/PTXdist/BSP/platform-imx6/build-target/e2fsprogs-1.46.5/util'
> make: *** [Makefile:194: util/subst] Error 2
> make: Leaving directory 
> '/PTXdist/BSP/platform-imx6/build-target/e2fsprogs-1.46.5'
> make: *** 
> [/usr/local/lib/ptxdist-2022.11.0/rules/post/ptxd_make_world_compile.make:20: 
> /PTXdist/BSP/platform-imx6/state/e2fsprogs.compile] Error 2
> 
> The error vanishes if ./configure is called with "--disable-lto" instead 
> of "--enable-lto".
> 

First things first.
So it looks like e2fsprogs is mixing compilers and archs here?
That would be my guess to what's behind the 11.2 / 11.3 error.

But probably more importantly,
enable-lto looks like a misconfiguration to me.
Maybe if it was controlled by a global.
And even then one would probably have to weed out a lot of compile
failures given the rocky history of LTO over a lot of stuff.
I suggest you disable it and submit a patch.

Regards,
Christian

> As I'm no expert at this level, I hope anyone could put some hints about 
> the issue.
> 
> 
> Best regards,
> 
> Felix
> 
> 
> 




  reply	other threads:[~2022-11-13 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 17:32 Felix Mellmann
2022-11-13 21:07 ` Christian Melki [this message]
2022-11-14  9:05   ` Ladislav Michl
2022-11-16  7:17 ` Michael Olbrich
2022-11-16 14:08   ` Felix Mellmann
2022-11-16 17:40     ` Christian Melki
2022-11-17  7:45       ` Michael Olbrich
2022-11-17 14:51         ` Felix Mellmann
2022-11-17 14:52         ` Felix Mellmann
2022-11-17 15:05           ` Michael Olbrich
2022-11-17 17:15             ` Christian Melki
2022-11-17 17:50           ` Alexander Dahl

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=91afd9cd-62ba-4418-d1bd-a2b15f188ebe@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=flix.ptxdist@benfm.de \
    --cc=ptxdist@pengutronix.de \
    /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