[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-25 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #5 from Marc  ---
Created attachment 15981
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15981&action=edit
Archive containing build of libadwaita with binutils 2.43.1

This archive contains a release and a debug build with all object files,
binaries and log files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-25 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #7 from Marc  ---
(In reply to Sam James from comment #1)
> Which binaries in the libadwaita package differ? Could you upload a bad and
> good tarball, where one is built w/ binutils-2.43.1, and one is built w/
> binutils-2.44?

I uploaded two archives containing all object files, binaries and log files.
The object files are identical in each build, but the resulting binaries are
different.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-25 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #8 from Marc  ---
(In reply to Sam James from comment #2)
> Also, does libadwaita's testsuite pass?

Yes, the testsuite passes successfully.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-26 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #6 from Marc  ---
Created attachment 15982
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15982&action=edit
Archive containing build of libadwaita with binutils 2.44

This archive contains a release and a debug build with all object files,
binaries and log files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-26 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #9 from Marc  ---
Created attachment 15983
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15983&action=edit
Stacktrace of the adwaita-demo-1 built with binutils 2.44

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-26 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #10 from Marc  ---
(In reply to Sam James from comment #3)
> >  they are not functional when executed.
> 
> Do they crash on startup? Look wrong? Otherwise malfunction (how)? Can you
> give a backtrace if they crash?

I added the stacktrace of the failed adwaita-demo-1 run.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-26 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

--- Comment #11 from Marc  ---
(In reply to Toolybird from comment #4)
> Hi, Arch Linux bug wrangler here. I've just rebuilt libadwaita with
> binutils-2.44, installed it on a Gnome desktop.. and don't see any problems
> whatsoever.
> 
> I suggest this report might be barking up the wrong tree.. and would
> encourage the reporter to jump into the Arch Linux support channels (Forum,
> IRC, etc) to seek some debugging assistance.

The reason I filed this bug here was because ArchLinux recommends filing bugs
that are not related to packaging issues with the corresponding project.

Here are the configure commands of the binutils 2.44 package, which did not
change when upgrading from version 2.43.1. Perhaps this is a clue as to why
your result is different.

https://gitlab.archlinux.org/archlinux/packaging/packages/binutils/-/blob/2.44-1/PKGBUILD?ref_type=tags#L64

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/32745] New: The ld in binutils 2.44 produces a malfunctioning libadwaita library

2025-02-25 Thread sourceware-bugzilla at hide dot mwcloud.eu
https://sourceware.org/bugzilla/show_bug.cgi?id=32745

Bug ID: 32745
   Summary: The ld in binutils 2.44 produces a malfunctioning
libadwaita library
   Product: binutils
   Version: 2.44
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: ld
  Assignee: unassigned at sourceware dot org
  Reporter: sourceware-bugzilla at hide dot mwcloud.eu
  Target Milestone: ---

After updating to version 2.44 of the binutils software, ArchLinux encountered
issues with the libadwaita library. While the library and demo binary can be
successfully built, they are not functional when executed. This issue is
specific to the library, as all binaries utilizing it encounter the same
failure when run, not only the demo application.

To illustrate the issue, I have prepared an example that can be found here:
https://github.com/marcbull/archlinux-binutils.

The issue was identified in ArchLinux and was traced back to a specific Docker
image that had undergone several package updates.Preliminary analysis indicates
a potential association with ld.

The last working Docker image was
archlinux/archlinux:base-devel-20250209.0.306672, and the first Docker image
that exhibited this issue was archlinux/archlinux:base-devel-20250210.0.306967.

If you build binutils 2.44 in ArchLinux and install it in /usr/local, and if
you then remove all existing binutils binaries provided by the package, it will
fail to build a functional libadwaita. However, if you remove all binaries
except ld, it will build libadwaita as expected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.