unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Greg Hogan <code@greghogan.com>
Cc: bavier@posteo.net, Sharlatan Hellseher <sharlatanus@gmail.com>,
	74216@debbugs.gnu.org
Subject: bug#74216: [science team] flint build failure
Date: Tue, 12 Nov 2024 15:01:00 +0100	[thread overview]
Message-ID: <ZzNfnK4Y3TiAUAE8@jurong> (raw)
In-Reply-To: <CA+3U0ZkVMvTXAsJ+JTGizNxCVCNEVNZkaTPgNoThMyXjs+DEWA@mail.gmail.com>

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.

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





  parent reply	other threads:[~2024-11-12 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 20:43 bug#74216: [science team] flint build failure Greg Hogan
2024-11-05 20:47 ` bug#74216: [PATCH science-team] gnu: flint: Update gcc version Greg Hogan
2024-11-12 14:01 ` Andreas Enge [this message]
2024-11-12 19:19   ` bug#74216: [science team] flint build failure Greg Hogan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZzNfnK4Y3TiAUAE8@jurong \
    --to=andreas@enge.fr \
    --cc=74216@debbugs.gnu.org \
    --cc=bavier@posteo.net \
    --cc=code@greghogan.com \
    --cc=sharlatanus@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).