[Bug libdw/32548] musl/error-standalone incompatibility (error.h)

2025-01-27 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=32548

Mark Wielaard  changed:

   What|Removed |Added

   Last reconfirmed||2025-01-27
 Ever confirmed|0   |1
   See Also||https://bugs.gentoo.org/sho
   ||w_bug.cgi?id=948878
 Status|UNCONFIRMED |NEW

--- Comment #2 from Mark Wielaard  ---
Proposed patch:
https://inbox.sourceware.org/elfutils-devel/mqaizvceef2tFKFrBHPGSZExJhSERDqyoyjiI57ISUX4GQjQMpNak4BDd4AXalptrWjXdZ-brBacci0OmIrGZNd3gjQa5AZfv26pXDCqEM4=@protonmail.com

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

Re: [PATCH] Link against standalone error library if available

2025-01-27 Thread Mark Wielaard
Hi,

On Mon, Jan 27, 2025 at 05:23:15AM +, parona wrote:
> Background for this patch is https://bugs.gentoo.org/948878 where
> are user had installed a standalone error implementation for a
> different package leading to a build failure.

There is also some discussion in this elfutils bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=32548

My main question/confusion is where the error.h include comes from.
elfutils does support libcs like musl who don't provide error.h but do
provide err.h. Then the build should provide its own error function
through lib/system.h.

So maybe our configure check is wrong and it should just test whether
there is an error.h but also if you can link the result?

> Decided to automagically link to it instead of forcing it as a
> dependency as its only packaged on Gentoo.
> 
> https://hacktivis.me/git/error-standalone/
> https://repology.org/project/error-standalone/versions
> 
> Followed the approach that was used for argp and fts to my best ability.

I think that should work. But it would be slightly nicer if we only
had to change the configure test (and maybe the include guards) so
that the error from lib/system.h is used.

But I might misunderstand the situation and such configure magic is
too magic :)

Cheers,

Mark


☺ Buildbot (Sourceware): elfutils - build successful (main)

2025-01-27 Thread builder
A restored build has been detected on builder elfutils-fedora-ppc64le while 
building elfutils.

Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/55/builds/379

Build state: build successful
Revision: dda7144c3696fae8f71c29ca720da4fe0438b6f9
Worker: fedora-ppc64le
Build Reason: (unknown)
Blamelist: Aaron Merey , Michael Pratt 

Steps:

- 0: worker_preparation ( success )

- 1: set package name ( success )

- 2: git checkout ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/2/logs/stdio

- 3: autoreconf ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/3/logs/stdio

- 4: configure ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/4/logs/stdio
- config.log: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/4/logs/config_log

- 5: get version ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/5/logs/stdio
- property changes: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/5/logs/property_changes

- 6: make ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/6/logs/stdio
- warnings (3): 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/6/logs/warnings__3_

- 7: make check ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/7/logs/stdio
- test-suite.log: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/7/logs/test-suite_log

- 8: prep ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/8/logs/stdio

- 9: build bunsen.cpio.gz ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/9/logs/stdio

- 10: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/10/logs/stdio

- 11: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/11/logs/stdio

- 12: pass .bunsen.source.* ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/12/logs/stdio

- 13: upload to bunsen ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/13/logs/stdio

- 14: clean up ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/14/logs/stdio

- 15: make distclean ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#/builders/55/builds/379/steps/15/logs/stdio