From owner-freebsd-questions@FreeBSD.ORG Wed Apr 2 00:22:23 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3A2896C for ; Wed, 2 Apr 2014 00:22:23 +0000 (UTC) Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 673D2EA0 for ; Wed, 2 Apr 2014 00:22:23 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id wp18so11843015obc.37 for ; Tue, 01 Apr 2014 17:22:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=bnNGymG54cUbKH7OQQIfhatRfWoxSgF2682biCKUEQ0=; b=oiQNXvxlNL6UqymopYPk7XVUNr8aJuw4kNhBtXlFncseZZ3JmaX3rlQ7EMmTn6bTWs Oa6GUzClH7+E+cXZmjBKq+L3vDtZxWv3TLxQuCNj5d09WV27vRf+rjXy2hAE2TdzJO7n XvbFlekm7Jo1JgClDnIrsXG3EOoNoMkuOa4wawGIORGa2sOP+nP/cxJx9/xW53mNvkMG 7hL3zVN7RsuJ/i4GzXgKrTm2nc4hcqSYFmn0PqYGjMnVtZx828CjI5HGw7uJg8xulgcH CM2dz0gpdsNhvffmpH/HD+lVKiBHI3qnn4bihtgmviTkg1yf+3/Mts9m5PUR7pMWDddy f5Zw== X-Received: by 10.60.155.35 with SMTP id vt3mr1363792oeb.32.1396398141953; Tue, 01 Apr 2014 17:22:21 -0700 (PDT) Received: from [192.168.1.64] (pool-71-170-112-253.dllstx.fios.verizon.net. [71.170.112.253]) by mx.google.com with ESMTPSA id cg5sm495937obc.9.2014.04.01.17.22.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Apr 2014 17:22:21 -0700 (PDT) References: <20140331201111.18f2688b@kalimero.tijl.coosemans.org> <2C2F5FA3-D5F3-4223-A163-F689DA5056BF@gmail.com> <20140331221329.5e795449@kalimero.tijl.coosemans.org> Mime-Version: 1.0 (1.0) In-Reply-To: <20140331221329.5e795449@kalimero.tijl.coosemans.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <40B749F5-EE6B-4963-A24D-C7A551190BF3@gmail.com> X-Mailer: iPad Mail (11D167) From: Matthew Pherigo Subject: Re: lang/nimrod issue: missing forward slash Date: Tue, 1 Apr 2014 19:22:23 -0500 To: Tijl Coosemans Cc: "freebsd-questions@freebsd.org" , Neal Nelson X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 00:22:23 -0000 Wow! That actually completely worked. Thank you so much! I'll forward this t= o the port maintainer. --Matt > On Mar 31, 2014, at 3:13 PM, Tijl Coosemans wrote: >=20 > On Mon, 31 Mar 2014 14:08:55 -0500 Matthew Pherigo wrote: >>>> On Mar 31, 2014, at 1:11 PM, Tijl Coosemans wrote:= >>>> On Mon, 31 Mar 2014 12:15:35 -0500 Matthew Pherigo wrote: >>>> I'm having a problem with lang/nimrod that's keeping me from doing any >>>> development at the moment. I think this is an issue created by the >>>> person who created the port (nimrod works fine on my arch linux VM), >>>> but I figured I'd check here in case anyone knows a fix. >>>>=20 >>>> When I try to compile anything from nimrod, the paths calls the compile= r >>>> with are incorrect. For example, here is the (successful) compilation >>>> output of a program that doesn't depend on any external Libs (besides >>>> system.nim): >>>=20 >>> Can you make these example program available somewhere so I can try to >>> reproduce this? >>=20 >> The programs themselves don't make any difference. But, here they are. >> The first one is simply >> echo("Hello, world!") >>=20 >> The program that has external dependencies is a very incomplete calculato= r >> program, as follows: >>=20 >> import strutils >> var a, b, c: float >> var buf: string >> echo("Enter your first number! \n> ") >> buf =3D readLine(stdin) >> a =3D ParseFloat(buf) >=20 > It seems that nimrod currently requires procfs to be mounted. I've > attached a patch to avoid that. You can place it in lang/nimrod/files > and then rebuild the port. You should also be able to remove > /etc/nimrod.cfg then. >