all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Patrascu, Madalin Ionel" <MadalinIonel.Patrascu@mdc-berlin.de>
Cc: "56999-done@debbugs.gnu.org" <56999@debbugs.gnu.org>
Subject: [bug#56999] [ext] bug#56999: Acknowledgement (Add phyml package tools.)
Date: Mon, 8 Aug 2022 12:35:28 +0200	[thread overview]
Message-ID: <871qtr2f3n.fsf@mdc-berlin.de> (raw)
In-Reply-To: <d03f5f3979974bffa133260aa135df40@mdc-berlin.de>

I modified the package definition like this:

- build all tools in the same package by using separate build phases
- remove any mention of PhyTime from the description
- add texlive-* packages to build and install the PDF manual
- remove the pre-built PDF manual from the sources
- remove -march=native
- set only x86_64 as supported

An upstream bug (https://github.com/stephaneguindon/phyml/issues/173)
made it impossible to remove -march=native completely, so I hope this is
sufficient.

-- 
Ricardo




  reply	other threads:[~2022-08-08 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  9:14 [bug#56999] Add phyml package tools MadalinIonel.Patrascu
     [not found] ` <handler.56999.B.165969091927817.ack@debbugs.gnu.org>
2022-08-05  9:29   ` [bug#56999] [ext] bug#56999: Acknowledgement (Add phyml package tools.) MadalinIonel.Patrascu
2022-08-08 10:35     ` Ricardo Wurmus [this message]
2022-10-31 20:47       ` bug#56999: Add phyml package tools Ricardo Wurmus
2022-08-05  9:33 ` [bug#56999] [PATCH 1/4] gnu: Add phyml Mădălin Ionel Patrașcu
2022-08-05  9:33   ` [bug#56999] [PATCH 2/4] gnu: Add phyml-mpi Mădălin Ionel Patrașcu
2022-08-05  9:33   ` [bug#56999] [PATCH 3/4] gnu: Add phyml-phyrex Mădălin Ionel Patrașcu
2022-08-05  9:33   ` [bug#56999] [PATCH 4/4] nu: Add phyml-rf Mădălin Ionel Patrașcu
2022-08-08  8:09   ` [bug#56999] [PATCH 1/4] gnu: Add phyml Ricardo Wurmus

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=871qtr2f3n.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=56999@debbugs.gnu.org \
    --cc=MadalinIonel.Patrascu@mdc-berlin.de \
    /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.