From owner-freebsd-arm@FreeBSD.ORG Tue Sep 17 04:07:32 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 6B718447 for ; Tue, 17 Sep 2013 04:07:32 +0000 (UTC) (envelope-from taguchi.ch@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4188327D6 for ; Tue, 17 Sep 2013 04:07:32 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id hz10so6236157pad.16 for ; Mon, 16 Sep 2013 21:07:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GP9JzCJj4OH0aFcuUZntsPuvAK/tei2CbWjRp9gXvUI=; b=Ro2h/LJHBRgo4cIFX+8qyBdqGmtIsm/BiQn7qkSA0u4QJmtOKfMmvMerK3oSDLhrG/ PcPLocqN+Dqldg3s9uZGCzUT+ZZEdmb8T5K6wiVOtlllDk8koeWMGOeDIG4MDV/LiKRW 61jUziXgGFf2FDkAMJaUUphv1YjqBcbHdpUAqShJkhOCR7ostLV1w5i4uEHAjrDsPXAt xHHT9vvTuMB2vl2ALIS9/olG1IL+AxWleffe73kn8vethdKirNCd5z1Hk6lweUzqdUsC dE54PTlbVNkWyP+68xVvXW2q4Z3A+gjIaMSncbFhKNafTtueyRGNM/9gzqfCv65aYVaT W4Yw== X-Received: by 10.68.191.193 with SMTP id ha1mr5499457pbc.166.1379390851938; Mon, 16 Sep 2013 21:07:31 -0700 (PDT) Received: from [10.0.1.203] (48.178.30.125.dy.iij4u.or.jp. [125.30.178.48]) by mx.google.com with ESMTPSA id wd6sm42701686pab.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Sep 2013 21:07:31 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: What's the recipe? From: Chie Taguchi In-Reply-To: <5237BC28.8030709@m5p.com> Date: Tue, 17 Sep 2013 13:07:28 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: <8B750CD2-53BB-478A-8C7E-369226AA9997@gmail.com> References: <522229C0.5030504@m5p.com> <5235D207.5070400@m5p.com> <6AE316FC-8B08-4F5D-B918-7F97C8C4CB60@gmail.com> <5237BC28.8030709@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.1508) 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 04:07:32 -0000 It will cause following issue in building devel/glib20: /bin/mkdir -p '/usr/local/include/glib-2.0/gio/' : jemalloc_arena.c:380: Failed assertion: "p[i] =3D=3D 0" Abort trap (core dumped) This is a very annoy problem, and glib20 ignore this error. As a result, glib20 fail to install some header files. This workaround is rebuild your image with "MALLOC_PRODUCTION=3Dyes". Thanks. C.Taguchi On 2013/09/17, at 11:19, George Mitchell wrote: > On 09/16/13 22:00, Chie Taguchi wrote: >> Have you tried ports/181140? >>=20 >> C.Taguchi >=20 > 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: >=20 > ... > .if ! {PORT_OPTIONS:MSIMD} > CONFIGURE_ARGS+=3D --disable-vmx --disable-arm-simd > .if ! {MACHINE_CPU:Mmmx} > CONFIGURE_ARGS+=3D --disable-mmx > .endif > .if ! {MACHINE_CPU:Msse2} > CONFIGURE_ARGS+=3D --disable-sse2 > .endif > .endif >=20 > .if ${ARCH} =3D=3D arm || ${ARCH} =3D=3D armv6 > CONFIGURE_ARGS+=3D --disable-arm-neon > .endif > ... >=20 > (The patch had "${MACHINE_CPU:Mmmx}" and "${MACHINE_CPU:Msse2}", but > make didn't like the dollar signs.) >=20 > 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 >=20 >>=20 >> On 2013/09/16, at 0:28, George Mitchell = wrote: >>=20 >>> 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? >>>>=20 >>>> 1. What system did you do the build on? If it was an i386 or = amd64, >>>> what svn version was it built with? >>>=20 >>> 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.) >>>>=20 >>>> 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? >>>=20 >>> I finally bit the bullet and went to clang. /etc/src.conf is empty; >>> /etc/make.conf contains "WITH_PKGNG=3Dyes". >>>>=20 >>>> 3. What svn version of /usr/src did you use in building the RPi = image? >>>>=20 >>> Same as above (r255361M). >>>=20 >>>> 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 >>>=20 >>>>=20 >>>> 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 >>>=20 >>> 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. =46rom 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: >>>=20 >>> http://www.m5p.com/~george/pi/DSCN1282.JPG >>>=20 >>> 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.) >>>=20 >>> Once, instead of the fatal kernel mode prefetch abort, I got: >>>=20 >>> 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] >>>=20 >>> (Sorry for the transcription by hand; I have an AdaFruit serial = cable >>> on order.) >>>=20 >>> My current problem is that x11/pixman fails to build: >>>=20 >>> =3D=3D=3D> 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)' >>> [...]