On Tue, Nov 12, 2024 at 9:01 AM Andreas Enge <andr...@enge.fr> wrote: > > Hello Greg, > > Am Tue, Nov 05, 2024 at 03:43:31PM -0500 schrieb Greg Hogan: > > flint fails to build for me with the following error unless I include > > as an input a newer gcc version. > > out of curiosity, what is your exact build architecture and processor > line? The package builds without problems on my rather old laptop, and > on the Guix build farms.
AWS r7a, AMD EPYC (4th Gen) 9R14 > I have asked someone who knows the flint code well, and they said it > means that gcc has trouble realising how to expand the assembly code > into load and stores and computation on machines with less than 8 > registers. Apparently it is a combination of compiler versions and > processor specifics. > > Apart from that, I think we can apply your patch without worries, but > I am just curious about what is happening. > > What is mildly worrying is that we already use the "--disable-assembly" > configure flag; this could be a bug in the flint configuration. > > Andreas Thanks for investigating this issue and pointing me in the right direction. Turns out the flint package builds successfully when upgrading GCC from 11.4 to 11.5. It looks like the processor was too new. When considering reproducible builds, this is a bug when building on future, unknown hardware. For a time-bomb we can set back the clock, and here we would need processor emulation? Marking as done since the fix is to update a core package. Greg
