From owner-freebsd-current@FreeBSD.ORG Wed May 25 17:03:11 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B76BF106564A; Wed, 25 May 2011 17:03:11 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 60ECB8FC13; Wed, 25 May 2011 17:03:11 +0000 (UTC) Received: by iwn33 with SMTP id 33so9912821iwn.13 for ; Wed, 25 May 2011 10:03:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6P5IetMiruo8FNRWhCmkYESeCDwvjSqwpcdfBTMGQQM=; b=Mq6lo1lUnWzwFk/sRzz0rdorxKIEJnI+5DjPYeGuFfjBmwJjYv17SFKsOX7tqaUPks HSycPP+z4EDxBWeCzcq4hFB2Tpj3Q2DfkBpUf9NYjFv6G/07UZZS6ucnw9pcckKJMrar ZqG3E2f7Fy8UnTAPcEfsEpwLUePJFVnOzYukQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oiluHBDbafM5bCMETUsLyZJ6ZiokTfiNtPHZMNlFudk0DQ63KNWMHVKN+ESWerJhYQ b058L57+2TVxqLNuQq0LuuRXH/GT4Djh/kGGl9clquweZ0xPRbovgOWXhgZi2QcMRIdi +GRUKbrDnPvaLH5QfGP0uvDDKCRUioxCK7jx4= MIME-Version: 1.0 Received: by 10.42.117.137 with SMTP id t9mr12514589icq.277.1306342990715; Wed, 25 May 2011 10:03:10 -0700 (PDT) Received: by 10.42.177.10 with HTTP; Wed, 25 May 2011 10:03:10 -0700 (PDT) In-Reply-To: <201105251228.32399.jhb@freebsd.org> References: <1306267772-31084-1-git-send-email-lacombar@gmail.com> <201105250943.15362.jhb@freebsd.org> <201105251228.32399.jhb@freebsd.org> Date: Wed, 25 May 2011 13:03:10 -0400 Message-ID: From: Arnaud Lacombe To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Dimitry Andric Subject: Re: [PATCH] Fix CFLAGS overwrite by Makefile 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: Wed, 25 May 2011 17:03:11 -0000 Hi, On Wed, May 25, 2011 at 12:28 PM, John Baldwin wrote: > On Wednesday, May 25, 2011 11:34:29 am Arnaud Lacombe wrote: >> Hi, >> >> On Wed, May 25, 2011 at 9:43 AM, John Baldwin wrote: >> >> The original trouble I met, is that building for an i586 target in a >> >> 32bits jail, on top of an amd64 system[0] (I do not have control over >> >> that setup) produces incorrect binaries. The current fix I've got is >> >> to define MACHINE_ARCH=3Di386 and CPUTYPE=3Di586. This enforces >> >> `-march=3Di586' to be passed to the compiler, for all except the >> >> bootloader (because it overwrites CFLAGS). With this, binaries >> >> produced works fine (ie. /bin/sh no longer SIGILL when bringing up th= e >> >> system). So I suspect that gcc default to i686 in this setup and >> >> corrupt all the binaries, thus the attached patch. >> > >> > Wait. =A0You must have something wrong in your jail if you can't do a > buildworld >> > with CPUTYPE set to none and have it do the right thing. =A0You need t= o find >> > your root problem. =A0Forcing CPUCFLAGS for the boot code is a band-ai= d, > it's >> > not the right solution to your problem. >> > >> Unless error of my part, I never mentioned it was using `buildworld', >> which it is not. The system uses bare calls to make(1) in the >> sys/boot/ directory. As the jail is 32bits, it was expected not to be >> an issue, but the jail compiler uses /lib/libstand.a to link the >> loader, and it obviously contains i686-only instructions, which >> trigger a reset of an i586-only CPU. >> >> The more broad issue with the setup is that gcc within that >> environment, without being told -march=3Di586, produces i686 >> instructions which are incompatible with the target CPU. > > Huh? =A0GCC does not generate i686 instructions by default on FreeBSD/i38= 6. =A0It > generates i486 instructions but that is all. something is odd somewhere. > Are you sure you aren't running > the 64-bit gcc (which will generate i686 instructions by default)? > yes. # which gcc /usr/bin/gcc # file /usr/bin/gcc /usr/bin/gcc: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 7.1, statically linked, FreeBSD-style, stripped # gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] # uname -a FreeBSD build 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 The fact that /usr/bin/gcc is statically linked made me think we may have built internally, but it is also statically linked on a 8.2 machine from release packages. - Arnaud