| Summary: | mail-client/thunderbird-60.7.0:0/0::gentoo Build failed | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | ad PC <adpc> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
ad PC
2019-05-24 06:26:10 UTC
Confirmed, same problem. Do we have an upstream report? This elfhack is a pos, no error messages, no --help options. This post recommends --disable-elf-hack, but I haven't tried it yet. https://blfs-dev.linuxfromscratch.narkive.com/lKXcx8UI/error-building-firefox-63-0#post8 This is an exceedingly bizarre bug. It only seems to happen when the program is run as root. Further, both gdb 8.1 and 8.3 it crash when attempting to debug it. I re-built elfhack with -O0 and -g3. As soon as I try to run the callq to the Elf::Elf(std::basic_ifstream<char, std::char_traits<char> >&), gdb blows up with a segfault. 0x0000555555569601 1200 Elf elf(file); 1: x/2i $rip => 0x555555569601 <do_file(char const*, bool, bool)+112>: callq 0x5555555568e2 <Elf::Elf(std::basic_ifstream<char, std::char_traits<char> >&)> 0x555555569606 <do_file(char const*, bool, bool)+117>: lea -0x490(%rbp),%rax (gdb) stepi Segmentation fault I wonder if --disable-elf-hack is the simplest way to work-around this. Thank you for the report. Please recompile and *attach* the complete logfiles and paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket The logs must be part of the ticket, but not on external websites. We need to have all information at hand before ticket assignment, so that the maintainer can look after it in one session with minimal number of callbacks. Please reopen this ticket (Status:unconfirmed) afterwards. @4: The build log has a size of 16 MB. Hence it cannot be attached due to the size limit of this bug tracker. ad PC: kindly reopen the bug, please don't close it as WONTFIX when it affects more than one user. Else I have to create a new bug, which only means more wrangling work for maintainers. (In reply to ad PC from comment #5) Nevermind ad PC, I've opened #686760. I'm almost certain that building without -g will work-around this issue, although I don't quite get the underlying cause and why upstream isn't getting this. Thanks to D.S. for the logfiles in #686760 *** This bug has been marked as a duplicate of bug 686760 *** |