unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 28423@debbugs.gnu.org
Subject: [bug#28423] gnu: Add imb-openmpi.
Date: Thu, 28 Sep 2017 22:09:45 +0200	[thread overview]
Message-ID: <87wp4ik2k6.fsf@gnu.org> (raw)
In-Reply-To: <877ex4ysk1.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 12 Sep 2017 15:06:54 +0200")

Ping!  :-)

ludo@gnu.org (Ludovic Courtès) skribis:

> Heya,
>
> Dave Love <fx@gnu.org> skribis:
>
>> From eed7aaac597248505d0ad0609810f7af5caac720 Mon Sep 17 00:00:00 2001
>> From: Dave Love <fx@gnu.org>
>> Date: Sat, 9 Sep 2017 11:10:29 +0100
>> Subject: [PATCH] gnu: Add imb-openmpi.
>>
>> * mpi.scm (gnu, imb): New function.
>>   (imb-openmpi): New package.
>
> [...]
>
>> +    (inputs
>> +     `((,(package-name mpi) ,mpi)))
>
> Rather:
>
>   `(("mpi" ,mpi))
>
>> +         (replace 'build
>> +           (lambda* _
>> +             (let ((mpi-home (dirname (dirname (which "mpicc")))))
>
> I'd suggest:
>
>   (lambda* (#:key inputs #:allow-other-keys)
>     (let ((mpi (assoc-ref inputs "mpi")))
>       ...))
>
>> +               (zero?
>> +                ;; Not safe for parallel build
>> +                (system
>> +                 (format #f "make -C imb/src -f make_mpich SHELL=sh MPI_HOME=~a"
>> +                         mpi-home))))))
>
> Rather use ‘system*’ to avoid going through the shell.
>
>> +                 (system
>> +                  (string-append
>> +                   "cd imb/src && install -m755 IMB-IO IMB-EXT IMB-MPI1 IMB-NBC IMB-RMA "
>> +                   bin)))
>> +                (zero?
>> +                 (system
>> +                  (string-append
>> +                   "cd imb && cp -r license " doc))))))))))
>
> Likewise, use ‘copy-file’ and ‘copy-recursively’ rather than shelling
> out.
>
>> +    (synopsis (format #f "Intel MPI Benchmarks, ~a version" (package-name mpi)))
>> +    (description (format #f "\
>> +A set of MPI performance measurements for point-to-point and global
>> +communication, and file, operations for a range of message sizes.
>> +The generated benchmark data fully characterize:
>> +@itemize
>> +@item
>> +Performance of a cluster system, including node performance, network latency,
>> +and throughput;
>> +@item
>> +Efficiency of the MPI implementation.
>> +@end itemize
>> +This is the ~a version." (package-name mpi)))
>
> Please avoid constructing synopsis/description strings as this prevents
> i18n.
>
> My suggestion would be to either leave them unchanged, which should be
> good enough anyway, or to just modify the synopsis but then arrange to
> have the whole string translated.
>
> Could you send an updated patch?
>
> Thanks,
> Ludo’.

  reply	other threads:[~2017-09-28 20:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 20:40 [bug#28423] gnu: Add imb-openmpi Dave Love
2017-09-11 20:47 ` Dave Love
2017-09-12 13:06   ` Ludovic Courtès
2017-09-28 20:09     ` Ludovic Courtès [this message]
2017-10-02 20:45       ` Dave Love
2017-10-03 12:47         ` Ludovic Courtès
2017-10-03 16:57           ` Dave Love
2017-10-03 19:51             ` Ludovic Courtès
2017-10-04 15:32               ` Dave Love
2017-10-05  9:24                 ` bug#28423: " Ludovic Courtès

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=87wp4ik2k6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28423@debbugs.gnu.org \
    --cc=fx@gnu.org \
    /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).