From owner-freebsd-current@FreeBSD.ORG Tue Sep 18 16:42:39 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5DA716A419 for ; Tue, 18 Sep 2007 16:42:39 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.freebsd.org (Postfix) with ESMTP id B3BEA13C46E for ; Tue, 18 Sep 2007 16:42:39 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.0.68] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id l8IGgUcQ018491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Sep 2007 09:42:31 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <46EFFF96.1040101@FreeBSD.org> Date: Tue, 18 Sep 2007 09:40:54 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Dmitry Morozovsky References: <20070914124630.D14000@woozle.rinet.ru> <46EEC481.5010503@FreeBSD.org> <20070918011258.L96165@woozle.rinet.ru> In-Reply-To: <20070918011258.L96165@woozle.rinet.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: i386 package building on an amd64 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Sep 2007 16:42:40 -0000 Dmitry Morozovsky wrote: > On Mon, 17 Sep 2007, Maxim Sobolev wrote: > > MS> > possibly stupid question: it there a way to fool jail (real, not > MS> > "tinderbox" one) that it's working under i386 kernel? This would be > MS> > extremely useful for local package building. > MS> > > MS> > Quick googling does not reveal anything, or did I miss something obvious? > MS> > > MS> > Thanks in advance. > MS> > MS> Works here like a charm. The only thing is that you need to set UNAME_p=i386 > MS> UNAME_m=i386 and CPUTYPE=i686 variables in the chroot/jail. > > I know aboot uname tricks ;-) > > What about sysctls revealing amd64 system internals? Did you compare packages > built by this jailed system with native? Any package that uses some sysctls from build machine to somehow alter build process should be considered b0rken. -Maxim