From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 16 06:15:31 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AFC9106566C; Tue, 16 Nov 2010 06:15:31 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from out-0.mx.aerioconnect.net (out-0-20.mx.aerioconnect.net [216.240.47.80]) by mx1.freebsd.org (Postfix) with ESMTP id EEE4F8FC14; Tue, 16 Nov 2010 06:15:30 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id oAG6FTY6022240; Mon, 15 Nov 2010 22:15:29 -0800 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 8FEBB2D6011; Mon, 15 Nov 2010 22:15:28 -0800 (PST) Message-ID: <4CE22182.7090008@freebsd.org> Date: Mon, 15 Nov 2010 22:15:30 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Garrett Cooper References: <4CA4C63F.4070503@icyb.net.ua> <20101116.022422.921.1@DEV> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: rank1seeker@gmail.com, freebsd-hackers@freebsd.org Subject: Re: Unhappy with cross-worlding X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 06:15:31 -0000 On 11/15/10 7:35 PM, Garrett Cooper wrote: > On Mon, Nov 15, 2010 at 6:24 PM, wrote: >> So, I have Core 2 Duo, runing as i386. >> I decided to go for amd64 (it's name, is so deceiving, that I've just >> recently, accidentaly figured out, that it can be used, with intel CPUs, >> too) :P >> >> 8.1 cross build i386 -> amd64 has failed >> World completes successfully, but kernel fails: >> >> mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE >> -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq - >> I/usr/obj/amd64/usr/src/sys/GENERIC >> /usr/src/sys/modules/amr/amr_linux/../../../dev/amr/amr_linux.c >> /usr/src/sys/modules/amr/amr_linux/../../../dev/amr/amr_linux.c:43:36: >> error: machine/../linux/linux.h: No such file or directory >> /usr/src/sys/modules/amr/amr_linux/../../../dev/amr/amr_linux.c:44:42: >> error: machine/../linux/linux_proto.h: No such file or directory >> mkdep: compile failed >> *** Error code 1 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 2 errors >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> >> Then, I've snapped and took an USB stick and did a binary 8.1 amd64 install >> on it. >> Booted from it and kernel compiled flawlessly >> >> PS: >> Core 2 Duo - 8.1 GENERIC >> Kernel build time: >> 10:30 --> i386 >> 08:30 --> amd64 >> >> Yes, without caching! >> >> >> PORTS: >> ------ >> > From i386, when created USB amd64, I wanted to compile some ports(i386 -> >> amd64), for that USB stick, on my own. >> Especially because of port's patches ... >> >> DESTIR has been set, as usual, but TARGET, was a no go! >> Looking into documentation, only /usr/src, supports TARGET, used for cross >> world compilation. >> Also, after throwing an eye into /usr/ports/Mk ..., I've concluded that >> ports, simply can't be cross world compiled, as they don't support it. >> >> This 2 problems should be fixed. > The best way to work with this is to create a chroot, set the > appropriate variables (OSVERSION, UNAME_m, UNAME_r, etc), mount the > /usr/ports via nullfs (if you dare) and then call chroot to access the > chroot and build to your heart's content. There's an entry in the > handbook somewhere that better describes how to do it from scratch, > but my search skills are failing me and I don't have the full docs > tree checked out. > But yes, building amd64 on i386 probably won't work too well :)... It's supposed to but hasn't for years. > HTH, > -Garrett > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >