From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 14 Nov 2022 10:06:31 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ouVQD-0079tk-7Q for lore@lore.pengutronix.de; Mon, 14 Nov 2022 10:06:31 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1ouVQC-0002M8-72; Mon, 14 Nov 2022 10:06:28 +0100 Received: from h2.cmg1.smtp.forpsi.com ([81.2.195.163]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ouVPg-0002IT-50 for ptxdist@pengutronix.de; Mon, 14 Nov 2022 10:05:56 +0100 Received: from lenoch ([91.218.190.200]) by cmgsmtp with ESMTPSA id uVPco91DlPm6CuVPeoHOL5; Mon, 14 Nov 2022 10:05:54 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=triops.cz; s=f2019; t=1668416755; bh=9ZxUPYm63lzLmR7RL9eCcXwzL5fELYfhxLXA0idvDlg=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=x+q3PKcq6sbMzoRAV5UMJqftXpTqLyO7/jROOnnmBjceOtWYad+gvdXlz/ht0VIdf lefmSDqHR8tiMmCsZ9454EDwkRsnTQeaiKo5M2nKILXsGawEmN0zU6wGGcUtsw/wmS UnyvyvBQgKWYbEnsqKA7E5VnjC3p+aTgzhPrvA++IJDw84RTk4VPWjhD1GOafWyILb 1V+jr/PZq11u1q1WAV/GRlBFrjnvXNHPn0sDooegXgHPipPQOxjKwp6D2/UnhHxMj4 d8lVtJswh1PpH/uzAS6Qp50b83jq3kJaa5yMtnP2ssehwgqwUxt1CC37n9Fdon+8/D Hjp+o9uwrV1UQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=triops.cz; s=f2019; t=1668416755; bh=9ZxUPYm63lzLmR7RL9eCcXwzL5fELYfhxLXA0idvDlg=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=x+q3PKcq6sbMzoRAV5UMJqftXpTqLyO7/jROOnnmBjceOtWYad+gvdXlz/ht0VIdf lefmSDqHR8tiMmCsZ9454EDwkRsnTQeaiKo5M2nKILXsGawEmN0zU6wGGcUtsw/wmS UnyvyvBQgKWYbEnsqKA7E5VnjC3p+aTgzhPrvA++IJDw84RTk4VPWjhD1GOafWyILb 1V+jr/PZq11u1q1WAV/GRlBFrjnvXNHPn0sDooegXgHPipPQOxjKwp6D2/UnhHxMj4 d8lVtJswh1PpH/uzAS6Qp50b83jq3kJaa5yMtnP2ssehwgqwUxt1CC37n9Fdon+8/D Hjp+o9uwrV1UQ== Date: Mon, 14 Nov 2022 10:05:52 +0100 From: Ladislav Michl To: ptxdist@pengutronix.de, christian.melki@t2data.com Message-ID: References: <35a025e1-9b3b-01f5-6776-db2ce5554208@benfm.de> <91afd9cd-62ba-4418-d1bd-a2b15f188ebe@t2data.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <91afd9cd-62ba-4418-d1bd-a2b15f188ebe@t2data.com> X-CMAE-Envelope: MS4wfKinu6n01D4J5PD/yGb7w8cJn9xGCm7VYgWVghFgAeewwcj+nE2+LV+qFr+CZu+jl1uGyCVh+6tUO2f7m9NZ7P6zM1bU/nnmwK2ee6IiOrAUHjeRpzzq 0y+YRnKPLjv4GmN8b/hf4ScpJ/T4kBTzBvkyv8O5ZOZ8QjGt0WrbiG6VekyklWk2xxfgsK5olLsuSFfbhjDXWgzyeiphV39dNXQ1+3mk8OUS6R/uqef6Gr8f LHNhs2w81MMfeY3TZYPGRw== X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.0 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] e2fsprogs: possibly broken when using OSELAS.Toolchain 2022.10.0 X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Cc: Felix Mellmann Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false 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 > > > > > > >