From owner-freebsd-ports Sun Sep 8 9:13:28 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FB4E37B400 for ; Sun, 8 Sep 2002 09:13:26 -0700 (PDT) Received: from procyon.firepipe.net (procyon.firepipe.net [198.78.66.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED39C43E72 for ; Sun, 8 Sep 2002 09:13:25 -0700 (PDT) (envelope-from will@csociety.org) Received: by procyon.firepipe.net (Postfix, from userid 1000) id 5C5012143F; Sun, 8 Sep 2002 09:13:15 -0700 (PDT) Date: Sun, 8 Sep 2002 09:13:15 -0700 From: Will Andrews To: David Syphers Cc: ports@FreeBSD.ORG Subject: Re: sed -i Message-ID: <20020908161315.GB37225@procyon.firepipe.net> Mail-Followup-To: David Syphers , ports@FreeBSD.ORG References: <200209062332.54123.dsyphers@uchicago.edu> <200209070017.09053.dsyphers@uchicago.edu> <20020908045641.54899254.corecode@corecode.ath.cx> <200209080931.14018.dsyphers@uchicago.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209080931.14018.dsyphers@uchicago.edu> User-Agent: Mutt/1.4i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Sep 08, 2002 at 09:31:14AM -0500, David Syphers wrote: > As I said in an email that was bounced from ports@ because "Message content > rejected", I am running my package builds in a sandbox. The sandbox is > 4.6.2-R, because that's the environment of the machine I'm installing these > programs on. My computer, on the other hand, is running -stable. I have to > use a sandbox because 'make package' irritatingly needs to install a package > to build it, and many of the packages I'm trying to build are already > installed on my machine. I'm sorry this isn't a supported configuration, but > there is a hack that works - install sed_inplace manually, remove > /usr/bin/sed, and replace it with a link to /usr/local/bin/sed_inplace. > > Thanks for helping me understand why my configuration caused this problem to > be particularly nasty. > > Now I just hope this message isn't rejected :) If by a "sandbox" you mean a chroot or similar, that's the cause of the problem. The uname(2) syscall depends on the kernel to provide it. We do exactly the same thing for the package build clusters. Except that, instead of doing something ugly like you mention here, we simply hack uname(1) instead. That works fine as long as the underlying kernel isn't too far out of sync with the userland used in the chroot. It makes sense as well, since it is the greatest common denominator solution. regards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message