Re: [ptxdist] e2fsprogs: possibly broken when using OSELAS.Toolchain 2022.10.0

[Ladislav Michl <oss-lists@triops.cz>]

On Sun, Nov 13, 2022 at 10:07:48PM +0100, Christian Melki wrote:
> 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.

I second that. Also see commit 'debian: stop using LTO (link-time optimization)'
https://github.com/tytso/e2fsprogs/commit/cfb073a4d4f37768b0be81660054044162dd8766

Regards,
	l.

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