From: Maxime Devos <maximedevos@telenet.be>
To: "Nicolas Goaziou" <mail@nicolasgoaziou.fr>, 路辉 <luhux76@gmail.com>
Cc: 53319@debbugs.gnu.org
Subject: [bug#53319] [PATCH] gnu: Add n2n.
Date: Tue, 22 Feb 2022 12:36:24 +0100 [thread overview]
Message-ID: <c691ad56a7cd5c32b53487ba661d2d9881a589f6.camel@telenet.be> (raw)
In-Reply-To: <87r18stbll.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Nicolas Goaziou schreef op vr 28-01-2022 om 11:10 [+0100]:
> > + (add-before 'configure 'fix-configure
> > + (lambda* (#:key inputs #:allow-other-keys)
> > + (substitute* "configure"
> > + (("/bin/sh") (which "sh"))))))
>
> Instead of using `which', you can use `search-input-file':
>
> (("/bin/sh") (search-input-file inputs "/bin/sh"))
'configure' is run during build, so for cross-compilation, a sh from
'native-inputs' shoud be used instead of 'inputs':
(("/bin/sh") (search-input-file (or native-inputs inputs) "/bin/sh"))
or simpler:
(("/bin/sh") (which "sh"))
Also, this package definition packages version 2.8. Why not package
the latest version instead? In the latest version, 'autogen.sh' does
not run "./configure" and hence 'move-configure' and 'fix-configure'
should not be necessary.
Also, looking at
<https://github.com/ntop/n2n/blob/472a9878f72299466ddbce2a232ea9e081159fa9/configure.seed#L94>,
it seems that n2n might not be bit-for-bit reproducible.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-22 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 14:47 [bug#53319] [PATCH] gnu: Add n2n 路辉
2022-01-28 10:10 ` Nicolas Goaziou
2022-02-22 11:36 ` Maxime Devos [this message]
2022-02-22 18:49 ` Nicolas Goaziou
2022-03-20 12:20 ` 路辉
2022-02-22 11:20 ` bug#53319: " Nicolas Goaziou
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=c691ad56a7cd5c32b53487ba661d2d9881a589f6.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53319@debbugs.gnu.org \
--cc=luhux76@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/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).