Date: Mon, 23 Jun 2014 10:59:06 -0700 From: falcon17@hushmail.com To: "Ian Lepore" <ian@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: build world cross compile Message-ID: <20140623175906.8AB87203AB@smtp.hushmail.com> In-Reply-To: <1403452699.20883.290.camel@revolution.hippie.lan> References: <20140622115633.E847320185@smtp.hushmail.com> <1403452699.20883.290.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Worked great. thanks! On June 22, 2014 at 8:58 AM, "Ian Lepore" wrote:On Sun, 2014-06-22 at 04:56 -0700, falcon17@hushmail.com wrote: > I would like to build 10-STABLE for arm on my amd64. I found some > instructions here > -https://wiki.freebsd.org/A_Brief_Guide_To_Cross_Compiling_FreeBSD(i > assume the third CPUTYPE example should be KERNCONF instead?) > all looks good, except that make.conf and src.conf examples do not say > a peep about arm! What are the right way of specifying these targets? > Do I need to build a special compiler before starting? > Thanks! Assuming that your /etc/make.conf and src.conf are empty, all you need to do to crossbuild for arm is: make builworld TARGET_ARCH=arm make buildkernel TARGET_ARCH=arm KERNCONF=whatever Use armv6 for the target arch if the target is a v6 or v7 chipset. There's no need to set CPUTYPE at all. -- Ian From owner-freebsd-arm@FreeBSD.ORG Mon Jun 23 22:44:29 2014 Return-Path: <owner-freebsd-arm@FreeBSD.ORG> Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7AF7C75; Mon, 23 Jun 2014 22:44:29 +0000 (UTC) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A05E2DAE; Mon, 23 Jun 2014 22:44:29 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id q59so7751174wes.40 for <multiple recipients>; Mon, 23 Jun 2014 15:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2PzU+UREL0fw6riva/9Ox7FINRm8T6mQLb2BoVjwLRY=; b=OAPtKOmpHPOEiaaa5bbsGQMP/iznyP2JsRIkEgOA9aTYGTPYTQCx0EgqlhFvcF/bX1 GMfJSWFvZ+kBirnelVg1f1yN+bPoJeg4j0QUpEbL8jCjWgz2EcSfvEvRl27T/bXNpwbf U0bgWRQRV1h6bs81R3ijn4Df8aBfdX2b1txPWiFwSYq1HInR23rs4tEbv3xfvKU+CJ2A BdvGAIfYhfIwY8YHRGAImV3cjK+fxb5A2G0kw59gRcrc38Zi+1dcDJG7Nt1/7UqhMBxH 3rFBvfF93/zLK6UQ2MRJDk31JzxuSLY7QoUbhT0/q4L7rAdAKc5vksQnqdHuKF0mIpsf 1wiw== MIME-Version: 1.0 X-Received: by 10.194.92.177 with SMTP id cn17mr18585857wjb.71.1403563467495; Mon, 23 Jun 2014 15:44:27 -0700 (PDT) Received: by 10.216.23.1 with HTTP; Mon, 23 Jun 2014 15:44:27 -0700 (PDT) In-Reply-To: <20140621140300.GO31367@funkthat.com> References: <CAHWWKwM_ETrPGZ1fPc451Hn=iCVEb9Z7qj2X0HEz-znwuR_k=w@mail.gmail.com> <1403193531.20883.269.camel@revolution.hippie.lan> <CAHWWKwNovBV7JouzquNK7kvw66ao9OtJ0uiQEsaftQa+DpbT5Q@mail.gmail.com> <20140621140300.GO31367@funkthat.com> Date: Tue, 24 Jun 2014 00:44:27 +0200 Message-ID: <CAHWWKwPS0LtvS1JXvug6DVYJuNH73h3ffZwGT25ffGyd4AEc7A@mail.gmail.com> Subject: Re: Strange slowdown of zlib. From: Magnus Nilsson <magnus.nilsson@gmail.com> To: John-Mark Gurney <jmg@funkthat.com>, freebsd-embedded@freebsd.org, freebsd-arm <freebsd-arm@freebsd.org> Content-Type: text/plain; charset=UTF-8 Cc: Ian Lepore <ian@freebsd.org> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>; List-Post: <mailto:freebsd-arm@freebsd.org> List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 23 Jun 2014 22:44:30 -0000 On Sat, Jun 21, 2014 at 4:03 PM, John-Mark Gurney <jmg@funkthat.com> wrote: > Magnus Nilsson wrote this message on Sat, Jun 21, 2014 at 14:13 +0200: >> While e.g. cat or md5 of an executable affects its speed, e.g. cp does not. >> Could there be some read access that's unaffected by your patches? > > I believe that cp uses mmap instead of the read syscall like cat and > md5... So this may be the case... > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." mmap() seems unaffected, well spotted. Not sure if it would be reasonable to use that fact for a workaround? I've done more patching and testing. Mark Tinguely's conservative, unofficial patch http://lists.freebsd.org/pipermail/freebsd-arm/2010-November/002635.html does not fix the issue. Grzegorz Bernacki's proof-of-concept patch http://lists.freebsd.org/pipermail/freebsd-arm/2010-March/002270.html /does/ fix the issue! But what's the potential downside? Debugging issues, as suggested in http://lists.freebsd.org/pipermail/freebsd-arm/2010-March/002290.html ? Performance issues? Something worse? I've looked at later releases (9.3) for backporting, but can't find anything that that handles PVF_EXEC as a special case like Mark and Grzegorz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140623175906.8AB87203AB>