GNU bug report logs - #50106
libtool testsuite failing when LTO is enabled

Previous Next

To reply to this bug, email your comments to 50106 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ondrej Dubaj <odubaj <at> redhat.com>
To: bug-libtool <at> gnu.org
Subject: libtool testsuite failing when LTO is enabled
Date: Wed, 18 Aug 2021 08:49:33 +0200

[Message part 1 (text/plain, inline)]

Hi,
experiencing testsuite failures, when LTO CFLAGS contain

-flto=auto -ffat-lto-objects

and are enabled during the build of libtool.

I might think in some cases it can be expected, but just to make sure, is
it an expected failure?
The failed tests are:

67: Link order of deplibs                           FAILED (link-order2.at:125)
170: Run tests with low max_cmd_len                  FAILED (cmdline_wrap.at:47)

Thank you in advance.

Ondrej

[Message part 2 (text/html, inline)]

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ondrej Dubaj <odubaj <at> redhat.com>
To: bug-libtool <at> gnu.org
Subject: Re: libtool testsuite failing when LTO is enabled
Date: Tue, 7 Sep 2021 16:02:37 +0200

[Message part 1 (text/plain, inline)]

Gentle ping

On Wed, Aug 18, 2021 at 8:49 AM Ondrej Dubaj <odubaj <at> redhat.com> wrote:

> Hi,
> experiencing testsuite failures, when LTO CFLAGS contain
>
> -flto=auto -ffat-lto-objects
>
> and are enabled during the build of libtool.
>
> I might think in some cases it can be expected, but just to make sure, is
> it an expected failure?
> The failed tests are:
>
> 67: Link order of deplibs                           FAILED (link-order2.at:125)
> 170: Run tests with low max_cmd_len                  FAILED (cmdline_wrap.at:47)
>
> Thank you in advance.
>
> Ondrej
>
>
>
>
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.