From owner-freebsd-ports@FreeBSD.ORG Sun May 19 16:38:07 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A9483C4D for ; Sun, 19 May 2013 16:38:07 +0000 (UTC) (envelope-from pierre@geobsd.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0FCFB9 for ; Sun, 19 May 2013 16:38:06 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Ue6cY-0004Vv-0C for freebsd-ports@freebsd.org; Sun, 19 May 2013 09:38:06 -0700 Date: Sun, 19 May 2013 09:38:05 -0700 (PDT) From: GeoBSD To: freebsd-ports@freebsd.org Message-ID: <20130519163751.GA1910@geobsd.com> In-Reply-To: <20130517214341.5147989b@bureau> References: <20130517083358.GB63515@geobsd.com> <5195FB7D.8040002@gwdg.de> <1368801413862-5812449.post@n5.nabble.com> <20130517214341.5147989b@bureau> Subject: Re: QGIS With Grass Plugin doesn't build (kpty.cpp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 16:38:07 -0000 Perfect ! This patch works also good for me. Many thanks. -- View this message in context: http://freebsd.1045724.n5.nabble.com/QGIS-With-Grass-Plugin-doesn-t-build-kpty-cpp-tp5812385p5813188.html Sent from the freebsd-ports mailing list archive at Nabble.com. From owner-freebsd-ports@FreeBSD.ORG Sun May 19 16:48:14 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4D42BF99 for ; Sun, 19 May 2013 16:48:14 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 21EBBFF5 for ; Sun, 19 May 2013 16:48:14 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id 10so12221980ied.19 for ; Sun, 19 May 2013 09:48:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3e6oqN2JGwbmCFP/bNqDK5E3sxRmFYqkeqKx6VA6GZ0=; b=Z7u2QkV5q+aDM5JqBAL6ASUtGILHO8yJGfcgH4wZUWTBacBc8BbaIF8N4nYJ0KzvI2 rhhb/dJdcoaPbyNhh5Fu9Pt3QU8XctR0Yt0MhX3SAmD+1jq6tU2sNsFolvGEBvawmvOt 5EVNMJvwVyjorThwLm38n4ibL/JpddEXSrRIA7dVEpO5I133uzqFyZyAUe+AHKNaJdFq +v/ngIT97n6NTSpEjkHp+q0rAJLX5aEtt6HFgzpwd34FtFsz6hr6fkLAYrVeoabvR6dP KxXoUe+ogL96EcCLYoQDf8CiThD4PIONfhCxGCa9FEjK+32gqLQNH69YmUfnJHjvsor7 TrpA== MIME-Version: 1.0 X-Received: by 10.50.120.68 with SMTP id la4mr3032109igb.49.1368982093891; Sun, 19 May 2013 09:48:13 -0700 (PDT) Received: by 10.64.77.51 with HTTP; Sun, 19 May 2013 09:48:13 -0700 (PDT) Received: by 10.64.77.51 with HTTP; Sun, 19 May 2013 09:48:13 -0700 (PDT) In-Reply-To: <20130519115232.49f52d01@scorpio> References: <20130519115232.49f52d01@scorpio> Date: Sun, 19 May 2013 17:48:13 +0100 Message-ID: Subject: Re: Why does Samba requires 777 permissions on /tmp From: Chris Rees To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 16:48:14 -0000 On 19 May 2013 16:52, "Jerry" wrote: > > On Sun, 19 May 2013 09:57:52 -0500 > sindrome articulated: > > > I checked everywhere (in .cshrc etc..) as well as "echo $PATH" > > and /tmp is not in there. I'm not sure where it's picking up /tmp in > > the path > > Same here. I have no idea where it is getting "tmp" from. At least it > doesn't appear to be causing any problems. Is that with portupgrade too? Chris