From owner-freebsd-stable@FreeBSD.ORG Thu May 10 07:19:07 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 03A851065674 for ; Thu, 10 May 2012 07:19:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 458AE8FC08 for ; Thu, 10 May 2012 07:19:05 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA01705; Thu, 10 May 2012 10:19:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SSNeS-0000jk-4Z; Thu, 10 May 2012 10:19:04 +0300 Message-ID: <4FAB6BE7.9060500@FreeBSD.org> Date: Thu, 10 May 2012 10:19:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: Alfred Bartsch References: <4FAA3912.3030801@dssgmbh.de> <4FAA4A11.808@FreeBSD.org> <4FAA5E70.7030508@dssgmbh.de> <4FAA83BD.2030204@FreeBSD.org> <4FAB6A7B.9050500@dssgmbh.de> In-Reply-To: <4FAB6A7B.9050500@dssgmbh.de> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 8 i386 gptboot corrupt - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2012 07:19:07 -0000 on 10/05/2012 10:12 Alfred Bartsch said the following: > I got this stupid idea of a "16k limit" during testing. It was unobvious to > me that the build process in a standard environment (i386) simply produces > invalid code. In i386 (32-bit) hardware, we don't use zfs at all, so I > can't tell anything about gptzfsboot. For now, modifying > /sys/boot/i386/gptboot/Makefile completely solves this actual build > problem. > > IMHO the compiler should always know perfectly well in which hardware > environment it runs and for which target environment it produces code. So > the build environment should be modified to fix this. I would certainly > give it a try, but unfortunately this is far beyond my knowledge. :-( That's an interesting theory. What kind of hardware do you have? Is it something non-mainstream or sufficiently old? As far as I can tell, our base GCC uses i686 target arch if none is explicitly requested. -- Andriy Gapon