From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH] gnu: Add proxychains-ng. Date: Sun, 14 Aug 2016 19:16:13 +0200 Message-ID: <87twen1db6.fsf@elephly.net> References: <87ziohc1wo.fsf@we.make.ritual.n0.is> <20160812181308.GB14494@jasmine> <87k2fjy1ib.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52940) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYz1P-0001eK-Ei for guix-devel@gnu.org; Sun, 14 Aug 2016 13:16:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bYz1K-0004jw-Dn for guix-devel@gnu.org; Sun, 14 Aug 2016 13:16:26 -0400 Received: from sender163-mail.zoho.com ([74.201.84.163]:24910) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYz1K-0004jr-5X for guix-devel@gnu.org; Sun, 14 Aug 2016 13:16:22 -0400 In-reply-to: <87k2fjy1ib.fsf@we.make.ritual.n0.is> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ng0 Cc: guix-devel@gnu.org ng0 writes: > Leo Famulari 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