unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add proxychains-ng.
Date: Mon, 15 Aug 2016 08:47:25 +0000	[thread overview]
Message-ID: <878tvya06a.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87popa1p6h.fsf@elephly.net>

Ricardo Wurmus <rekado@elephly.net> writes:

> ng0 <ng0@we.make.ritual.n0.is> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> 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.
>
> […]
>
> Thanks.  Looks like you need to set the “prefix” variable in
> #:make-flags – it is defined in the Makefile (along with “exec_prefix”,
> which you might also have to override).
>
> ~~ Ricardo
>

I did set prefix and exec_prefix in the make-flags, gets ignored.
it doesn't work, and I think I tried setting it in the make-flags before.
I will revert to the original patch and add a comment why it needs to be
configured like this. Second choice could be to substitute, but
./configure --options is shorter and apparently what the application
wants.
-- 
♥Ⓐ  ng0
For non-prism friendly talk find me on http://www.psyced.org

  reply	other threads:[~2016-08-15  8:47 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
2016-08-14 21:01       ` ng0
2016-08-15  7:12         ` Ricardo Wurmus
2016-08-15  8:47           ` ng0 [this message]
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=878tvya06a.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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 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).