From: Antero Mejr via Guix-patches via <guix-patches@gnu.org>
To: Eric Bavier <bavier@posteo.net>
Cc: 60266@debbugs.gnu.org
Subject: [bug#60266] [PATCH] gnu: Add form.
Date: Thu, 16 Mar 2023 01:15:51 +0000 [thread overview]
Message-ID: <871qlpzebc.fsf@mailbox.org> (raw)
In-Reply-To: <92910915624cad61de6c1fc75cbe6ac2b8c6fe27.camel@posteo.net> (Eric Bavier's message of "Mon, 09 Jan 2023 18:01:33 +0000")
Eric Bavier <bavier@posteo.net> writes:
>> x86_64 only due to test failures on other platforms. Developers
>> say other platforms are not "tier 1" supported:
>> https://github.com/vermaseren/form/issues/426
>
> This may be better as a comment near the `supported-systems` field,
> along with a short summary of which tests fail on other systems.
Added comments in v2.
> This commit is downstream from the 4.3.0 release, so we should include
> in a comment the rationale for not using just the 4.3.0 release
> tarball.
Added rationale.
>> + (snippet #~(substitute* "check/examples.frm"
>> + (("#pend_if valgrind\\?")
>> + "#pend_if 0")))))
>
> This snippet appears to be related to the specifics of this package
> build? E.g. if someone were to grab the source with `guix build -S
> form`, they would not be able to have valgrind support, correct? If
> that's the case, perhaps it would be better to apply this substitution
> in a build phase.
No, it's disabling a failing test that has a known problem (memory
leak). Added a comment with the explanation.
> For some other maths packages that have both a serial and MPI versions,
> we've usually provided two packages. See e.g. `petsc` and `petsc-
> openmpi`. This can be useful if someone does not need a full MPI-
> capable version of form, and the separation is easily achieved.
Moved the openMPI version to the parform package.
> Also, I see the default compilation flags include `-march=native`,
> which will most likely cause a problem with build farm substitutes or
> `guix challenge`. Could you figure out have to override these flags?
> Guix usually assumes `SSE2` capabilities for x86_64 targets, iirc.
> Bonus points for enabling a "tunable" package (c.f. "Package
> Transformation Options").
Disabled --march=native in v2.
> Maybe we should use https://www.nikhef.nl/~form/ instead? This is the
> URL specified in the included manpage.
I used the other homepage so people can skip the weird "license
agreement" page at https://www.nikhef.nl/~form/. But I changed it to
your suggestion in v2.
Thanks for the review.
next prev parent reply other threads:[~2023-03-16 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 1:15 [bug#60266] [PATCH] gnu: Add form Antero Mejr via Guix-patches via
2023-01-09 18:01 ` Eric Bavier
2023-03-16 1:15 ` Antero Mejr via Guix-patches via [this message]
2023-03-16 5:23 ` Liliana Marie Prikler
2023-03-21 18:53 ` Antero Mejr via Guix-patches via
2023-03-22 4:54 ` bug#60266: " Eric Bavier
2023-02-19 22:42 ` [bug#60266] Algebra Andreas Enge
2023-03-16 1:07 ` [bug#60266] [PATCH v2 1/2] gnu: Add form Antero Mejr via Guix-patches via
2023-03-16 1:07 ` [bug#60266] [PATCH v2 2/2] gnu: Add parform Antero Mejr via Guix-patches via
2023-03-21 18:39 ` [bug#60266] [PATCH v3 1/2] gnu: Add form Antero Mejr via Guix-patches via
2023-03-21 18:39 ` [bug#60266] [PATCH v3 2/2] gnu: Add parform Antero Mejr via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qlpzebc.fsf@mailbox.org \
--to=guix-patches@gnu.org \
--cc=60266@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=bavier@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.