Re: Very strange compiler/linker related build failures in rawhide

2020-08-20 Thread Vít Ondruch
Hi Jeff,


Dne 27. 07. 20 v 14:28 Vít Ondruch napsal(a):
> Dne 27. 07. 20 v 12:25 Vít Ondruch napsal(a):
>> Dne 24. 07. 20 v 21:01 Jeff Law napsal(a):
>>> On Fri, 2020-07-24 at 20:52 +0200, Vít Ondruch wrote:
 The LTO break Ruby on various platforms.


 https://koji.fedoraproject.org/koji/taskinfo?taskID=47582573

 vs

 https://koji.fedoraproject.org/koji/taskinfo?taskID=47621733

 (Note these are my experimental builds testing single test case).
>>> I haven't gotten a clean ruby build with or without LTO.
>> Ruby builds just fine on x86_64 according to Koschei:
>>
>> https://koschei.fedoraproject.org/package/ruby?
>>
>>
>>>   So I haven't
>>> investigated Ruby for any LTO specific failures.
>>>
 The only difference is redhat-rpm-config 162-1.fc33 => 163-1.fc33.
 Adding `%define _lto_cflags %{nil}` helped to recover, but if it was at
 least behaving the same on all platforms :/


 And this is Koschei failure: 
 https://koschei.fedoraproject.org/package/ruby?

 Looking at the full test suite, it seems it causes some troubles to
 SIGSEV signal handler (Ruby spawns subprocess and kills it).
>>> Does the signal handler modify any global variables?
>> I am afraid there happens a lot of interesting stuff. This is the method
>> responsible for printing the output which likely fails:
>>
>> https://github.com/ruby/ruby/blame/master/vm_dump.c#L920
>>
>> But the issue might be that the signal handler itself might be somehow
>> modified and the modification fails. This is the default signal handler:
>>
>> https://github.com/ruby/ruby/blob/master/signal.c#L1137
>>
>>
>>>   That's been a common source
>>> of issues I've seen.
>> I am afraid I'll need to open some upstream ticket to help with answers
>> to questions like this :/
>
> https://bugs.ruby-lang.org/issues/17052


I have upstream response. From the ticket above:


~~~

It seems the generated DWARF section is broken. For instance
addr2line(1) also fails to understand it.

% nm ./miniruby | fgrep -w rb_f_kill | LC_ALL=C addr2line -e ./miniruby
addr2line: Dwarf Error: Could not find abbrev number 64.
??:?
:?

When you kill LTO option the above one liner must show "signal.c:423" or
something.

vo.x (Vit Ondruch) is it possible for you to ask this to linker people
instead? As addr2line(1) is also affected, it is hard for me to think we
are the ones who is doing something wrong.

~~~


HTH


Vít


>
>
> Vít
>
>
>>
>> Vít
>>
>>
>>> jeff
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-27 Thread Vít Ondruch

Dne 27. 07. 20 v 12:25 Vít Ondruch napsal(a):
> Dne 24. 07. 20 v 21:01 Jeff Law napsal(a):
>> On Fri, 2020-07-24 at 20:52 +0200, Vít Ondruch wrote:
>>> The LTO break Ruby on various platforms.
>>>
>>>
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=47582573
>>>
>>> vs
>>>
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=47621733
>>>
>>> (Note these are my experimental builds testing single test case).
>> I haven't gotten a clean ruby build with or without LTO.
>
> Ruby builds just fine on x86_64 according to Koschei:
>
> https://koschei.fedoraproject.org/package/ruby?
>
>
>>   So I haven't
>> investigated Ruby for any LTO specific failures.
>>
>>> The only difference is redhat-rpm-config 162-1.fc33 => 163-1.fc33.
>>> Adding `%define _lto_cflags %{nil}` helped to recover, but if it was at
>>> least behaving the same on all platforms :/
>>>
>>>
>>> And this is Koschei failure: https://koschei.fedoraproject.org/package/ruby?
>>>
>>> Looking at the full test suite, it seems it causes some troubles to
>>> SIGSEV signal handler (Ruby spawns subprocess and kills it).
>> Does the signal handler modify any global variables?
>
> I am afraid there happens a lot of interesting stuff. This is the method
> responsible for printing the output which likely fails:
>
> https://github.com/ruby/ruby/blame/master/vm_dump.c#L920
>
> But the issue might be that the signal handler itself might be somehow
> modified and the modification fails. This is the default signal handler:
>
> https://github.com/ruby/ruby/blob/master/signal.c#L1137
>
>
>>   That's been a common source
>> of issues I've seen.
>
> I am afraid I'll need to open some upstream ticket to help with answers
> to questions like this :/


https://bugs.ruby-lang.org/issues/17052


Vít


>
>
> Vít
>
>
>> jeff
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-27 Thread Vít Ondruch

Dne 24. 07. 20 v 21:01 Jeff Law napsal(a):
> On Fri, 2020-07-24 at 20:52 +0200, Vít Ondruch wrote:
>> The LTO break Ruby on various platforms.
>>
>>
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=47582573
>>
>> vs
>>
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=47621733
>>
>> (Note these are my experimental builds testing single test case).
> I haven't gotten a clean ruby build with or without LTO.


Ruby builds just fine on x86_64 according to Koschei:

https://koschei.fedoraproject.org/package/ruby?


>   So I haven't
> investigated Ruby for any LTO specific failures.
>
>>
>> The only difference is redhat-rpm-config 162-1.fc33 => 163-1.fc33.
>> Adding `%define _lto_cflags %{nil}` helped to recover, but if it was at
>> least behaving the same on all platforms :/
>>
>>
>> And this is Koschei failure: https://koschei.fedoraproject.org/package/ruby?
>>
>> Looking at the full test suite, it seems it causes some troubles to
>> SIGSEV signal handler (Ruby spawns subprocess and kills it).
> Does the signal handler modify any global variables?


I am afraid there happens a lot of interesting stuff. This is the method
responsible for printing the output which likely fails:

https://github.com/ruby/ruby/blame/master/vm_dump.c#L920

But the issue might be that the signal handler itself might be somehow
modified and the modification fails. This is the default signal handler:

https://github.com/ruby/ruby/blob/master/signal.c#L1137


>   That's been a common source
> of issues I've seen.


I am afraid I'll need to open some upstream ticket to help with answers
to questions like this :/


Vít


>
> jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-27 Thread Caolán McNamara
On Fri, 2020-07-24 at 10:40 -0600, Jeff Law wrote:
> On Fri, 2020-07-24 at 17:59 +0200, Fabio Valentini wrote:
> > On Fri, Jul 24, 2020 at 5:48 PM Jeff Law  wrote:
> > > On Fri, 2020-07-24 at 17:44 +0200, Fabio Valentini wrote:
> > > > On Fri, Jul 24, 2020 at 5:11 PM Jeff Law 
> > > > wrote:
> > Looks like somebody already did that and attached the .ii file to
> > the RHBZ.
> > https://bugzilla.redhat.com/show_bug.cgi?id=1859588
> Unfortunately neither Marek nor I can reproduce with the compilers
> we've tested.

On a F32 box with

dnf --nogpg --enablerepo=rawhide update gcc

it reproduces 100% for me (gcc-10.1.1-2.fc33.x86_64). My guess is
there's a problem with "using". With trial-and-error I expanded the
various locations that triggered the ICE to explicit calls to the right
method and managed to complete a build for rawhide.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Jeff Law
On Fri, 2020-07-24 at 15:00 -0600, Jerry James wrote:
> On Fri, Jul 24, 2020 at 2:49 PM Eric Sandeen  wrote:
> > Hm, is this related?  (libtool segfault building xfsprogs)
> > 
> > https://kojipkgs.fedoraproject.org//work/tasks/9149/47779149/build.log
> > 
> > /bin/sh ../libtool --quiet --tag=CC --mode=link gcc -Wl,-z,relro 
> > -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
> > -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now 
> > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -rpath /lib64 -version-info 
> > 0:0:0 -static -o libfrog.la avl64.lo bitmap.lo bulkstat.lo convert.lo 
> > crc32.lo fsgeom.lo list_sort.lo linux.lo logging.lo paths.lo projects.lo 
> > ptvar.lo radix-tree.lo scrub.lo topology.lo util.lo workqueue.lo
> > ../libtool: line 1085: 137776 Segmentation fault  (core dumped) ar cru 
> > .libs/libfrog.a avl64.o bitmap.o bulkstat.o convert.o crc32.o fsgeom.o 
> > list_sort.o linux.o logging.o paths.o projects.o ptvar.o radix-tree.o 
> > scrub.o topology.o util.o workqueue.o
> > gmake[2]: *** [../include/buildrules:71: libfrog.la] Error 139
> > gmake[1]: *** [include/buildrules:36: libfrog] Error 2
> > make: *** [Makefile:92: default] Error 2
> > error: Bad exit status from /var/tmp/rpm-tmp.fcTM51 (%build)
> > RPM build errors:
> > Bad exit status from /var/tmp/rpm-tmp.fcTM51 (%build)
> > Child return code was: 1
> > EXCEPTION: [Error()]
> 
> Isn't that ar segfaulting?  I just saw the same thing (an ar segfault)
> while trying to do a mock build of z3 with --enablerepo=local.
More likely the binutils update if that's gone in.  Nick's probably already
wrapped for the day.

Jeff
> 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Jerry James
On Fri, Jul 24, 2020 at 2:49 PM Eric Sandeen  wrote:
> Hm, is this related?  (libtool segfault building xfsprogs)
>
> https://kojipkgs.fedoraproject.org//work/tasks/9149/47779149/build.log
>
> /bin/sh ../libtool --quiet --tag=CC --mode=link gcc -Wl,-z,relro 
> -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
> -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -rpath /lib64 -version-info 
> 0:0:0 -static -o libfrog.la avl64.lo bitmap.lo bulkstat.lo convert.lo 
> crc32.lo fsgeom.lo list_sort.lo linux.lo logging.lo paths.lo projects.lo 
> ptvar.lo radix-tree.lo scrub.lo topology.lo util.lo workqueue.lo
> ../libtool: line 1085: 137776 Segmentation fault  (core dumped) ar cru 
> .libs/libfrog.a avl64.o bitmap.o bulkstat.o convert.o crc32.o fsgeom.o 
> list_sort.o linux.o logging.o paths.o projects.o ptvar.o radix-tree.o scrub.o 
> topology.o util.o workqueue.o
> gmake[2]: *** [../include/buildrules:71: libfrog.la] Error 139
> gmake[1]: *** [include/buildrules:36: libfrog] Error 2
> make: *** [Makefile:92: default] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.fcTM51 (%build)
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.fcTM51 (%build)
> Child return code was: 1
> EXCEPTION: [Error()]

Isn't that ar segfaulting?  I just saw the same thing (an ar segfault)
while trying to do a mock build of z3 with --enablerepo=local.
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Eric Sandeen
On 7/24/20 1:31 AM, Fabio Valentini wrote:
> Hi all,
> 
> I'm starting to see various very strange kinds of build failures in
> rawhide, that seem to have started with either of these updates (or a
> combination of them):
> 
> - annobin 9.21-1.fc33 → 9.22-1.fc33
> - binutils 2.34.0-6.fc33 → 2.34.0-7.fc33
> - elfutils 0.179-2.fc33 → 0.180-2.fc33
> - glibc 2.31.9000-13.fc33 → 2.31.9000-14.fc33
> 
> These rawhide updates all happened at roughly the same time, so it's
> difficult to say which one of them is to blame (if any of them).

Hm, is this related?  (libtool segfault building xfsprogs)

https://kojipkgs.fedoraproject.org//work/tasks/9149/47779149/build.log

/bin/sh ../libtool --quiet --tag=CC --mode=link gcc -Wl,-z,relro 
-Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld -rpath /lib64 -version-info 0:0:0 
-static -o libfrog.la avl64.lo bitmap.lo bulkstat.lo convert.lo crc32.lo 
fsgeom.lo list_sort.lo linux.lo logging.lo paths.lo projects.lo ptvar.lo 
radix-tree.lo scrub.lo topology.lo util.lo workqueue.lo 
../libtool: line 1085: 137776 Segmentation fault  (core dumped) ar cru 
.libs/libfrog.a avl64.o bitmap.o bulkstat.o convert.o crc32.o fsgeom.o 
list_sort.o linux.o logging.o paths.o projects.o ptvar.o radix-tree.o scrub.o 
topology.o util.o workqueue.o
gmake[2]: *** [../include/buildrules:71: libfrog.la] Error 139
gmake[1]: *** [include/buildrules:36: libfrog] Error 2
make: *** [Makefile:92: default] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.fcTM51 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.fcTM51 (%build)
Child return code was: 1
EXCEPTION: [Error()]
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Jeff Law
On Fri, 2020-07-24 at 20:52 +0200, Vít Ondruch wrote:
> The LTO break Ruby on various platforms.
> 
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=47582573
> 
> vs
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=47621733
> 
> (Note these are my experimental builds testing single test case).
I haven't gotten a clean ruby build with or without LTO.  So I haven't
investigated Ruby for any LTO specific failures.

> 
> 
> The only difference is redhat-rpm-config 162-1.fc33 => 163-1.fc33.
> Adding `%define _lto_cflags %{nil}` helped to recover, but if it was at
> least behaving the same on all platforms :/
> 
> 
> And this is Koschei failure: https://koschei.fedoraproject.org/package/ruby
> 
> Looking at the full test suite, it seems it causes some troubles to
> SIGSEV signal handler (Ruby spawns subprocess and kills it).
Does the signal handler modify any global variables?  That's been a common 
source
of issues I've seen.

jeff
> 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Vít Ondruch
The LTO break Ruby on various platforms.


https://koji.fedoraproject.org/koji/taskinfo?taskID=47582573

vs

https://koji.fedoraproject.org/koji/taskinfo?taskID=47621733

(Note these are my experimental builds testing single test case).


The only difference is redhat-rpm-config 162-1.fc33 => 163-1.fc33.
Adding `%define _lto_cflags %{nil}` helped to recover, but if it was at
least behaving the same on all platforms :/


And this is Koschei failure: https://koschei.fedoraproject.org/package/ruby

Looking at the full test suite, it seems it causes some troubles to
SIGSEV signal handler (Ruby spawns subprocess and kills it).


Vít



Dne 24. 07. 20 v 10:31 Fabio Valentini napsal(a):
> Hi all,
>
> I'm starting to see various very strange kinds of build failures in
> rawhide, that seem to have started with either of these updates (or a
> combination of them):
>
> - annobin 9.21-1.fc33 → 9.22-1.fc33
> - binutils 2.34.0-6.fc33 → 2.34.0-7.fc33
> - elfutils 0.179-2.fc33 → 0.180-2.fc33
> - glibc 2.31.9000-13.fc33 → 2.31.9000-14.fc33
>
> These rawhide updates all happened at roughly the same time, so it's
> difficult to say which one of them is to blame (if any of them).
>
> One error I've seen in libreoffice is a gcc / annobin segfault:
>
> [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> *** WARNING *** there are active plugins, do not report this as a bug
> unless you can reproduce it without enabling any plugins.
> Event| Plugins
> PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> PLUGIN_START_UNIT| annobin: Generate global annotations
> PLUGIN_ALL_PASSES_START  | annobin: Generate per-function annotations
> PLUGIN_ALL_PASSES_END| annobin: Register per-function end symbol
> /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> internal compiler error: Segmentation fault
>  1733 | join();
>   |  ^
>
> Other errors look like this one from switchboard-plug-onlineaccounts:
>
> src/libonline-accounts.so.p/Authentification/Server.c: In function
> ‘online_accounts_server_on_bus_acquired’:
> src/libonline-accounts.so.p/Authentification/Server.c:498:2: error:
> function ‘__errno_location’ is initialized like a variable
>   498 |  gint errno = 0;
>   |  ^~~~
>
> Where errno is neither __errno_location, nor a function, but a gint??
>
> Other failures I've seen end up with linker failures, line these, from
> postgresql:
>
> ld: undefined reference to `postgresql_subtrans__checkpoint__start_semaphore'
>
> Does somebody have a clue what's going on here? It's currently
> blocking rawhide composes because libreoffice fails to build /
> install.
>
> See also: https://pagure.io/releng/failed-composes/issue/1571
>
> Thanks,
> Fabio
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Dominique Martinet
Jeff Law wrote on Fri, Jul 24, 2020:
> > Looks like somebody already did that and attached the .ii file to the RHBZ.
> > https://bugzilla.redhat.com/show_bug.cgi?id=1859588
>
> Unfortunately neither Marek nor I can reproduce with the compilers we've 
> tested.
>  Is it possible the OOM killer is killing the process?  Is there anything in 
> the
> system logs that might be relevant?

I was able to reproduce running a rawhide mock, it's definitely not
memory pressure.

It's a plain segfault in cc1plus - I'd give a backtrace but it looks
mangled up so I didn't take the time to install debuginfos

-- 
Dominique
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Jeff Law
On Fri, 2020-07-24 at 17:59 +0200, Fabio Valentini wrote:
> On Fri, Jul 24, 2020 at 5:48 PM Jeff Law  wrote:
> > On Fri, 2020-07-24 at 17:44 +0200, Fabio Valentini wrote:
> > > On Fri, Jul 24, 2020 at 5:11 PM Jeff Law  wrote:
> > > > > One error I've seen in libreoffice is a gcc / annobin segfault:
> > > > > 
> > > > > [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> > > > > *** WARNING *** there are active plugins, do not report this as a bug
> > > > > unless you can reproduce it without enabling any plugins.
> > > > > Event| Plugins
> > > > > PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> > > > > PLUGIN_START_UNIT| annobin: Generate global 
> > > > > annotations
> > > > > PLUGIN_ALL_PASSES_START  | annobin: Generate per-function 
> > > > > annotations
> > > > > PLUGIN_ALL_PASSES_END| annobin: Register per-function end 
> > > > > symbol
> > > > > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> > > > > destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> > > > > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> > > > > internal compiler error: Segmentation fault
> > > > >  1733 | join();
> > > > This sounds like a compiler bug.  Can you try adding
> > > > "%define _lto_cflags %{nil}"
> > > > 
> > > > To the .spec file and see if that gets you over the hump?  I've seen 
> > > > one failure
> > > > of this nature in my LTO testing and haven't gotten around to producing 
> > > > a
> > > > bugreport suitable for upstream (but the affected package has LTO 
> > > > disabled to
> > > > keep it from failing its builds).  My tester reports that it's never 
> > > > got a clean
> > > > control build of libreoffice, so I've never dug into it for any LTO 
> > > > specific
> > > > failures.
> > > 
> > > I added this %define _lto_cflags %{nil} to the top of the libreoffice
> > > .spec file, and compiled it in mock locally.
> > > And it spits out the same GCC crash error message without LTO.
> > THanks for checking.  That'll make things easier ;-)
> > 
> > Add -save-temps to the compile line and also build with V=1 so you can get 
> > the
> > full command line.  Pass along the .ii file and that full command line and 
> > I'll
> > take a peek at what's going on inside GCC.
> > 
> > jeff
> > 
> 
> Looks like somebody already did that and attached the .ii file to the RHBZ.
> https://bugzilla.redhat.com/show_bug.cgi?id=1859588
Unfortunately neither Marek nor I can reproduce with the compilers we've tested.
 Is it possible the OOM killer is killing the process?  Is there anything in the
system logs that might be relevant?

Jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Fabio Valentini
On Fri, Jul 24, 2020 at 5:48 PM Jeff Law  wrote:
>
> On Fri, 2020-07-24 at 17:44 +0200, Fabio Valentini wrote:
> > On Fri, Jul 24, 2020 at 5:11 PM Jeff Law  wrote:
> > > > One error I've seen in libreoffice is a gcc / annobin segfault:
> > > >
> > > > [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> > > > *** WARNING *** there are active plugins, do not report this as a bug
> > > > unless you can reproduce it without enabling any plugins.
> > > > Event| Plugins
> > > > PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> > > > PLUGIN_START_UNIT| annobin: Generate global annotations
> > > > PLUGIN_ALL_PASSES_START  | annobin: Generate per-function 
> > > > annotations
> > > > PLUGIN_ALL_PASSES_END| annobin: Register per-function end 
> > > > symbol
> > > > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> > > > destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> > > > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> > > > internal compiler error: Segmentation fault
> > > >  1733 | join();
> > > This sounds like a compiler bug.  Can you try adding
> > > "%define _lto_cflags %{nil}"
> > >
> > > To the .spec file and see if that gets you over the hump?  I've seen one 
> > > failure
> > > of this nature in my LTO testing and haven't gotten around to producing a
> > > bugreport suitable for upstream (but the affected package has LTO 
> > > disabled to
> > > keep it from failing its builds).  My tester reports that it's never got 
> > > a clean
> > > control build of libreoffice, so I've never dug into it for any LTO 
> > > specific
> > > failures.
> >
> > I added this %define _lto_cflags %{nil} to the top of the libreoffice
> > .spec file, and compiled it in mock locally.
> > And it spits out the same GCC crash error message without LTO.
> THanks for checking.  That'll make things easier ;-)
>
> Add -save-temps to the compile line and also build with V=1 so you can get the
> full command line.  Pass along the .ii file and that full command line and 
> I'll
> take a peek at what's going on inside GCC.
>
> jeff
>

Looks like somebody already did that and attached the .ii file to the RHBZ.
https://bugzilla.redhat.com/show_bug.cgi?id=1859588
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Jeff Law
On Fri, 2020-07-24 at 17:44 +0200, Fabio Valentini wrote:
> On Fri, Jul 24, 2020 at 5:11 PM Jeff Law  wrote:
> > > One error I've seen in libreoffice is a gcc / annobin segfault:
> > > 
> > > [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> > > *** WARNING *** there are active plugins, do not report this as a bug
> > > unless you can reproduce it without enabling any plugins.
> > > Event| Plugins
> > > PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> > > PLUGIN_START_UNIT| annobin: Generate global annotations
> > > PLUGIN_ALL_PASSES_START  | annobin: Generate per-function 
> > > annotations
> > > PLUGIN_ALL_PASSES_END| annobin: Register per-function end 
> > > symbol
> > > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> > > destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> > > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> > > internal compiler error: Segmentation fault
> > >  1733 | join();
> > This sounds like a compiler bug.  Can you try adding
> > "%define _lto_cflags %{nil}"
> > 
> > To the .spec file and see if that gets you over the hump?  I've seen one 
> > failure
> > of this nature in my LTO testing and haven't gotten around to producing a
> > bugreport suitable for upstream (but the affected package has LTO disabled 
> > to
> > keep it from failing its builds).  My tester reports that it's never got a 
> > clean
> > control build of libreoffice, so I've never dug into it for any LTO specific
> > failures.
> 
> I added this %define _lto_cflags %{nil} to the top of the libreoffice
> .spec file, and compiled it in mock locally.
> And it spits out the same GCC crash error message without LTO.
THanks for checking.  That'll make things easier ;-)

Add -save-temps to the compile line and also build with V=1 so you can get the
full command line.  Pass along the .ii file and that full command line and I'll
take a peek at what's going on inside GCC.

jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Fabio Valentini
On Fri, Jul 24, 2020 at 5:11 PM Jeff Law  wrote:
> > One error I've seen in libreoffice is a gcc / annobin segfault:
> >
> > [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> > *** WARNING *** there are active plugins, do not report this as a bug
> > unless you can reproduce it without enabling any plugins.
> > Event| Plugins
> > PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> > PLUGIN_START_UNIT| annobin: Generate global annotations
> > PLUGIN_ALL_PASSES_START  | annobin: Generate per-function 
> > annotations
> > PLUGIN_ALL_PASSES_END| annobin: Register per-function end symbol
> > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> > destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> > internal compiler error: Segmentation fault
> >  1733 | join();
> This sounds like a compiler bug.  Can you try adding
> "%define _lto_cflags %{nil}"
>
> To the .spec file and see if that gets you over the hump?  I've seen one 
> failure
> of this nature in my LTO testing and haven't gotten around to producing a
> bugreport suitable for upstream (but the affected package has LTO disabled to
> keep it from failing its builds).  My tester reports that it's never got a 
> clean
> control build of libreoffice, so I've never dug into it for any LTO specific
> failures.

I added this %define _lto_cflags %{nil} to the top of the libreoffice
.spec file, and compiled it in mock locally.
And it spits out the same GCC crash error message without LTO.

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Jeff Law
On Fri, 2020-07-24 at 10:31 +0200, Fabio Valentini wrote:
> Hi all,
> 
> I'm starting to see various very strange kinds of build failures in
> rawhide, that seem to have started with either of these updates (or a
> combination of them):
> 
> - annobin 9.21-1.fc33 → 9.22-1.fc33
> - binutils 2.34.0-6.fc33 → 2.34.0-7.fc33
> - elfutils 0.179-2.fc33 → 0.180-2.fc33
> - glibc 2.31.9000-13.fc33 → 2.31.9000-14.fc33
> 
> These rawhide updates all happened at roughly the same time, so it's
> difficult to say which one of them is to blame (if any of them).
> 
> One error I've seen in libreoffice is a gcc / annobin segfault:
> 
> [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> *** WARNING *** there are active plugins, do not report this as a bug
> unless you can reproduce it without enabling any plugins.
> Event| Plugins
> PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> PLUGIN_START_UNIT| annobin: Generate global annotations
> PLUGIN_ALL_PASSES_START  | annobin: Generate per-function annotations
> PLUGIN_ALL_PASSES_END| annobin: Register per-function end symbol
> /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> internal compiler error: Segmentation fault
>  1733 | join();
This sounds like a compiler bug.  Can you try adding 
"%define _lto_cflags %{nil}"

To the .spec file and see if that gets you over the hump?  I've seen one failure
of this nature in my LTO testing and haven't gotten around to producing a
bugreport suitable for upstream (but the affected package has LTO disabled to
keep it from failing its builds).  My tester reports that it's never got a clean
control build of libreoffice, so I've never dug into it for any LTO specific
failures.



>   |  ^
> 
> Other errors look like this one from switchboard-plug-onlineaccounts:
> 
> src/libonline-accounts.so.p/Authentification/Server.c: In function
> ‘online_accounts_server_on_bus_acquired’:
> src/libonline-accounts.so.p/Authentification/Server.c:498:2: error:
> function ‘__errno_location’ is initialized like a variable
>   498 |  gint errno = 0;
>   |  ^~~~
> 
> Where errno is neither __errno_location, nor a function, but a gint??
This is more likely related to the glibc update.

> 
> Other failures I've seen end up with linker failures, line these, from
> postgresql:
> 
> ld: undefined reference to `postgresql_subtrans__checkpoint__start_semaphore'
This is a known interaction between stap/dtrace probes and LTO.  I've already
fixed postgresql to avoid LTO until we fix this issue on the GCC side.

jeff
> 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Petr Pisar
On Fri, Jul 24, 2020 at 10:31:11AM +0200, Fabio Valentini wrote:
> Other failures I've seen end up with linker failures, line these, from
> postgresql:
> 
> ld: undefined reference to `postgresql_subtrans__checkpoint__start_semaphore'
>
.

-- Petr


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Fabio Valentini
On Fri, Jul 24, 2020 at 11:23 AM Hans de Goede  wrote:
>
> Hi,
>
> On 7/24/20 10:31 AM, Fabio Valentini wrote:
> > Hi all,
> >
> > I'm starting to see various very strange kinds of build failures in
> > rawhide, that seem to have started with either of these updates (or a
> > combination of them):
> >
> > - annobin 9.21-1.fc33 → 9.22-1.fc33
> > - binutils 2.34.0-6.fc33 → 2.34.0-7.fc33
> > - elfutils 0.179-2.fc33 → 0.180-2.fc33
> > - glibc 2.31.9000-13.fc33 → 2.31.9000-14.fc33
> >
> > These rawhide updates all happened at roughly the same time, so it's
> > difficult to say which one of them is to blame (if any of them).
> >
> > One error I've seen in libreoffice is a gcc / annobin segfault:
> >
> > [build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
> > *** WARNING *** there are active plugins, do not report this as a bug
> > unless you can reproduce it without enabling any plugins.
> > Event| Plugins
> > PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
> > PLUGIN_START_UNIT| annobin: Generate global annotations
> > PLUGIN_ALL_PASSES_START  | annobin: Generate per-function 
> > annotations
> > PLUGIN_ALL_PASSES_END| annobin: Register per-function end symbol
> > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
> > destructor 'virtual DemoWin::RenderThread::~RenderThread()':
> > /builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
> > internal compiler error: Segmentation fault
> >   1733 | join();
> >|  ^
> >
>
>
> I've been hitting something similar with dmraid:
>
> https://koji.fedoraproject.org/koji/getfile?taskID=47692725=DEFAULT=build.log=-4000
>
> Are you seeing this on s390x too ?
>
> I was hopening the new gcc build which was started yesterday would fix this,
> but that seems to be failing + hanging in its selftests on s390x :|   :
>
> https://koji.fedoraproject.org/koji/getfile?taskID=47682083=DEFAULT=build.log=-4000

Yes, this failure seems to be architecture independent.
For example, libreoffice also fails with the same gcc/annobin segfault
on all architectures ...

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Hans de Goede

Hi,

On 7/24/20 10:31 AM, Fabio Valentini wrote:

Hi all,

I'm starting to see various very strange kinds of build failures in
rawhide, that seem to have started with either of these updates (or a
combination of them):

- annobin 9.21-1.fc33 → 9.22-1.fc33
- binutils 2.34.0-6.fc33 → 2.34.0-7.fc33
- elfutils 0.179-2.fc33 → 0.180-2.fc33
- glibc 2.31.9000-13.fc33 → 2.31.9000-14.fc33

These rawhide updates all happened at roughly the same time, so it's
difficult to say which one of them is to blame (if any of them).

One error I've seen in libreoffice is a gcc / annobin segfault:

[build CXX] vcl/unx/gtk3/gtk3gtkinst.cxx
*** WARNING *** there are active plugins, do not report this as a bug
unless you can reproduce it without enabling any plugins.
Event| Plugins
PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
PLUGIN_START_UNIT| annobin: Generate global annotations
PLUGIN_ALL_PASSES_START  | annobin: Generate per-function annotations
PLUGIN_ALL_PASSES_END| annobin: Register per-function end symbol
/builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx: In
destructor 'virtual DemoWin::RenderThread::~RenderThread()':
/builddir/build/BUILD/libreoffice-6.4.5.2/vcl/workben/vcldemo.cxx:1733:18:
internal compiler error: Segmentation fault
  1733 | join();
   |  ^




I've been hitting something similar with dmraid:

https://koji.fedoraproject.org/koji/getfile?taskID=47692725=DEFAULT=build.log=-4000

Are you seeing this on s390x too ?

I was hopening the new gcc build which was started yesterday would fix this,
but that seems to be failing + hanging in its selftests on s390x :|   :

https://koji.fedoraproject.org/koji/getfile?taskID=47682083=DEFAULT=build.log=-4000

Regards,

Hans





Other errors look like this one from switchboard-plug-onlineaccounts:

src/libonline-accounts.so.p/Authentification/Server.c: In function
‘online_accounts_server_on_bus_acquired’:
src/libonline-accounts.so.p/Authentification/Server.c:498:2: error:
function ‘__errno_location’ is initialized like a variable
   498 |  gint errno = 0;
   |  ^~~~

Where errno is neither __errno_location, nor a function, but a gint??

Other failures I've seen end up with linker failures, line these, from
postgresql:

ld: undefined reference to `postgresql_subtrans__checkpoint__start_semaphore'

Does somebody have a clue what's going on here? It's currently
blocking rawhide composes because libreoffice fails to build /
install.

See also: https://pagure.io/releng/failed-composes/issue/1571

Thanks,
Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Fabio Valentini
On Fri, Jul 24, 2020 at 10:45 AM Stephan Bergmann  wrote:
> > Does somebody have a clue what's going on here? It's currently
> > blocking rawhide composes because libreoffice fails to build /
> > install.
>
> (The LibreOffice build failure is tracked at
>  "LibreOffice FTBFS
> with internal compiler error".)

I am aware, since I've been blamed for this problem for some reason.

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Very strange compiler/linker related build failures in rawhide

2020-07-24 Thread Stephan Bergmann

On 24/07/2020 10:31, Fabio Valentini wrote:

Other errors look like this one from switchboard-plug-onlineaccounts:

src/libonline-accounts.so.p/Authentification/Server.c: In function
‘online_accounts_server_on_bus_acquired’:
src/libonline-accounts.so.p/Authentification/Server.c:498:2: error:
function ‘__errno_location’ is initialized like a variable
   498 |  gint errno = 0;
   |  ^~~~

Where errno is neither __errno_location, nor a function, but a gint??


Note that, depending on what you include, errno may be a macro.


Does somebody have a clue what's going on here? It's currently
blocking rawhide composes because libreoffice fails to build /
install.


(The LibreOffice build failure is tracked at 
 "LibreOffice FTBFS 
with internal compiler error".)

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org