From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add proxychains-ng.
Date: Sun, 14 Aug 2016 19:16:13 +0200 [thread overview]
Message-ID: <87twen1db6.fsf@elephly.net> (raw)
In-Reply-To: <87k2fjy1ib.fsf@we.make.ritual.n0.is>
ng0 <ng0@we.make.ritual.n0.is> writes:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Fri, Aug 12, 2016 at 05:50:15PM +0000, ng0 wrote:
>>> * gnu/packages/networking.scm (proxychains-ng): New variable.
>>
>>> + (arguments
>>> + `(#:tests? #f
>>> + #:make-flags (list "CC=gcc")
>>> + #:phases
>>> + (modify-phases %standard-phases
>>> + ;; Needs to be configured through the configure script.
>>> + (replace 'configure
>>> + (lambda* (#:key outputs #:allow-other-keys)
>>> + (let ((out (assoc-ref outputs "out")))
>>> + (zero? (system* "./configure"
>>> + (string-append "--prefix=" out)))))))))
>>
>> Does #:configure-flags not work in this case?
>
> The previous message was too much. I just wanted to point out that
> configure-flags does not seem to work in this case, but in case I made a
> mistake I appended the patch with #:configure-flags in the previous
> message. For me, the version with system ./configure works, the one with
> #:configure-flags produces a failed build.
Could you show us the error message in case of using
“#:configure-flags”? This really should work, so if it fails I’d like
to fix this instead of working around it, if possible.
~~ Ricardo
next prev parent reply other threads:[~2016-08-14 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:50 [PATCH] gnu: Add proxychains-ng ng0
2016-08-12 18:13 ` Leo Famulari
2016-08-12 19:21 ` ng0
2016-08-14 12:32 ` ng0
2016-08-14 17:16 ` Ricardo Wurmus [this message]
2016-08-14 21:01 ` ng0
2016-08-15 7:12 ` Ricardo Wurmus
2016-08-15 8:47 ` ng0
2016-08-15 9:37 ` Ricardo Wurmus
2016-08-15 9:57 ` ng0
2016-08-15 10:17 ` Ricardo Wurmus
2016-08-15 9:02 ` ng0
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=87twen1db6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).