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>,
	Michael Olbrich <m.olbrich@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] e2fsprogs: possibly broken when using OSELAS.Toolchain 2022.10.0
Date: Wed, 16 Nov 2022 18:40:02 +0100	[thread overview]
Message-ID: <f624b666-0d84-b84b-c4f6-50a7bd44240f@t2data.com> (raw)
In-Reply-To: <55c7407e-88b8-85cb-5b3d-5556e7cdeb91@benfm.de>

On 11/16/22 15:08, Felix Mellmann wrote:
> 
> On 16.11.22 08:17, Michael Olbrich wrote:
>> On Sun, Nov 13, 2022 at 06:32:01PM +0100, Felix Mellmann wrote:
>>> 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".
>>>
>>> As I'm no expert at this level, I hope anyone could put some hints about the
>>> issue.
>> Is this a clean build? I've not seen this here with the same toolchain and
>> the error looks like you're mixing compiler versions.
> 
> It was a clean build, yes. But finally - ccache messed it up. After 
> clearing the cache the build was successful.
> 
> Well I should loose my trust in ccache ... Please drop my patch.
> 

I still think that LTO should not be enabled per project like that.
Regardless if it's working or not.
A global for LTO would be much better.

>>
>> Michael
> 
> 
> Felix
> 
> 




  reply	other threads:[~2022-11-16 17:43 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
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 [this message]
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=f624b666-0d84-b84b-c4f6-50a7bd44240f@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=flix.ptxdist@benfm.de \
    --cc=m.olbrich@pengutronix.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