On Wed, Jan 07, 2026 at 04:16:42PM +0000, Ian McInerney wrote:
> Hi all,
> 
> I was looking into the Koschei-reported failure of the arpack package on
> F44 (https://koschei.fedoraproject.org/package/arpack?collection=f44), and
> it seems to have started failing immediately after the GCC update landed in
> rawhide.
> 
> The thing I can't understand is the failure is actually in a configure
> check for a header. It uses the eigen3 library (so installs eigen3-devel),
> and the configure check for that library has passed, but the subsequent
> check for the actual "Eigen/Sparse" header fails. The tests it does are
> standard autoconf macros (
> https://github.com/opencollab/arpack-ng/blob/f73592dd1e5e39c469ade3587db76794ddfa171d/configure.ac#L92),
> so I am perplexed why it seems this GCC update being merged has caused them
> to start failing when the eigen3 package hasn't changed at all.
> 
> I am not that experienced with autoconf, so does anyone have any thoughts
> on what might be causing this?

You'll need to get the 'config.log' file from a failed configure run,
and compare it to a previous successful configure run with GCC 15.
In these situations typically you'll find some historical bad assumption
in the way the autoconf check was written that has finally been invalidated
by the new GCC or glibc.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to