From owner-freebsd-arm@FreeBSD.ORG Tue Sep 17 02:19:28 2013 Return-Path: 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 ESMTP id 2B40840B for ; Tue, 17 Sep 2013 02:19:28 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D6FEC21E3 for ; Tue, 17 Sep 2013 02:19:27 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r8H2JKc6024588; Mon, 16 Sep 2013 22:19:25 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <5237BC28.8030709@m5p.com> Date: Mon, 16 Sep 2013 22:19:20 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130716 Thunderbird/17.0.7 MIME-Version: 1.0 To: Chie Taguchi Subject: Re: What's the recipe? References: <522229C0.5030504@m5p.com> <5235D207.5070400@m5p.com> <6AE316FC-8B08-4F5D-B918-7F97C8C4CB60@gmail.com> In-Reply-To: <6AE316FC-8B08-4F5D-B918-7F97C8C4CB60@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Mon, 16 Sep 2013 22:19:26 -0400 (EDT) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Sep 2013 02:19:28 -0000 On 09/16/13 22:00, Chie Taguchi wrote: > Have you tried ports/181140? > > C.Taguchi Yes; google pointed me there a little earlier today. But the syntax of the patch appears to be slightly off. Here's what works for me: ... .if ! {PORT_OPTIONS:MSIMD} CONFIGURE_ARGS+= --disable-vmx --disable-arm-simd .if ! {MACHINE_CPU:Mmmx} CONFIGURE_ARGS+= --disable-mmx .endif .if ! {MACHINE_CPU:Msse2} CONFIGURE_ARGS+= --disable-sse2 .endif .endif .if ${ARCH} == arm || ${ARCH} == armv6 CONFIGURE_ARGS+= --disable-arm-neon .endif ... (The patch had "${MACHINE_CPU:Mmmx}" and "${MACHINE_CPU:Msse2}", but make didn't like the dollar signs.) My next problem is that my devel/glib20 build somehow didn't populate /usr/local/include/glib-2.0/gio, so devel/gobject-introspection couldn't build. I'm rerunning the devel/glib20 build to see if it works better the second time. -- George > > On 2013/09/16, at 0:28, George Mitchell wrote: > >> On 08/31/13 13:37, George Mitchell wrote: >>> Have you built a working Raspberry Pi image recently? If so, for the >>> benefit of the rest of us, could you share a few secrets? >>> >>> 1. What system did you do the build on? If it was an i386 or amd64, >>> what svn version was it built with? >> >> Built on amd64, svn version r255361M. (Two changes: I still distrust >> SCHED_ULE, and there's a patch [attached] required for the ARM xdev >> build to complete.) >>> >>> 2. What did you have in /etc/src.conf and /etc/make.conf, both for >>> building the build system itself and for building the RPi? >> >> I finally bit the bullet and went to clang. /etc/src.conf is empty; >> /etc/make.conf contains "WITH_PKGNG=yes". >>> >>> 3. What svn version of /usr/src did you use in building the RPi image? >>> >> Same as above (r255361M). >> >>> 4. Did you use crochet? If so, what was the last commit in your git >>> log? >> commit b154a2f1252eaa5f4d821439d0d9005cea94e580 >> Merge: a6f4cc5 8d03c23 >> Author: Tim Kientzle >> Date: Sat Aug 17 12:00:52 2013 -0700 >> >>> >>> When I say "working," I'm hoping for the ability to run stably for a >>> number of days, running NFS and CUPS. I've been doing this since >>> January with a precompiled image I downloaded then which worked >>> wonderfully with one of my printers, but not the other one. Now >>> there's a patch that enables both printers to work, and I would love >>> to build a new image. So I've been thrashing around trying to find >>> the answers to the questions above without success. Thanks for any >>> help you can give! -- George >> >> This build is marginally stable. I've been working for a week to get >> a complete build of print/cups and I'm not quite there. From the RPi, >> /usr/ports is an NFS mount from another machine with version 326306 of >> the ports tree (just before the iconv incident). The RPi likes to get >> messages of this sort: >> >> http://www.m5p.com/~george/pi/DSCN1282.JPG >> >> primarily during the period that portmaster is discovering everybody's >> dependencies. (Oddly, if I make it to the build stage, the build >> completes about 90% of the time. devel/glib20 built, including its >> dependencies on perl and python, in one overnight session.) >> >> Once, instead of the fatal kernel mode prefetch abort, I got: >> >> panic: __rw_wlock_hard: recursing but non-recursive rw pmap pw @ /usr/src/sys/arm/arm/pmap-v6.c:1406 >> KDB: enter: panic [ thread pid 906 tid 100076 ] >> stopped at $d: ldrb r15, [r15, 15, ror r15] >> >> (Sorry for the transcription by hand; I have an AdaFruit serial cable >> on order.) >> >> My current problem is that x11/pixman fails to build: >> >> ===> Building for pixman-0.30.0 >> [...] >> CC pixman-arm-neon.lo >> CPPAS pixman-arm-neon-asm.lo >> /usr/include/float.h: Assembler messages: >> /usr/include/float.h:43: Error: bad instruction `extern int __flt_rounds(void)' >> [...]