From owner-freebsd-arm@FreeBSD.ORG Wed Dec 12 10:16:36 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA27015D for ; Wed, 12 Dec 2012 10:16:36 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from smtp4.clear.net.nz (smtp4.clear.net.nz [203.97.37.64]) by mx1.freebsd.org (Postfix) with ESMTP id 8A64F8FC08 for ; Wed, 12 Dec 2012 10:16:35 +0000 (UTC) Received: from mxin3-orange.clear.net.nz (lb2-srcnat.clear.net.nz [203.97.32.237]) by smtp4.clear.net.nz (CLEAR Net Mail) with ESMTP id <0MEW00GGXXVG9D40@smtp4.clear.net.nz> for freebsd-arm@freebsd.org; Wed, 12 Dec 2012 23:16:28 +1300 (NZDT) Received: from 202-0-48-19.paradise.net.nz (HELO localhost) ([202.0.48.19]) by smtpin32.paradise.net.nz with ESMTP; Wed, 12 Dec 2012 23:16:27 +1300 Date: Wed, 12 Dec 2012 23:16:14 +1300 From: Andrew Turner Subject: Re: ARM EABI patch In-reply-to: <6D652C6AB162489E8C06D17141AF0178@ad.peach.ne.jp> To: Daisuke Aoyama Message-id: <20121212231614.20c9a8f0@fubar.geek.nz> MIME-version: 1.0 X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; i386-portbld-freebsd8.1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Pirate: Arrrr References: <20121209160721.571186d8@fubar.geek.nz> <3DE6764415F645FCA29CD18BA51762F8@ad.peach.ne.jp> <20121212081833.47127fd0@fubar.geek.nz> <6D652C6AB162489E8C06D17141AF0178@ad.peach.ne.jp> 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: Wed, 12 Dec 2012 10:16:36 -0000 On Wed, 12 Dec 2012 08:08:30 +0900 "Daisuke Aoyama" wrote: > >> I found cross-build problem of the EABI patch. I'm trying to use it > >> for Raspberry Pi. > >> According to machine/_types.h, wchar_t is unsigned int when EABI. > >> This patch solve "error: array of inappropriate type initialized > >> from string constant" when use L"foo". > > > > Can you send me a full log of the cross-build (off list is fine) > > that shows the failure. I haven't seen the issue so would like to > > find out how to trigger it. > > Sorry, I used modified source tree for RPI. > If check out new one, it should be OK. > I'm using following commands in amd64 2vCPU VM on ESXi5.1. > > export SRCROOT=/usr/src > export TARGET_ARCH=armv6 > export KERNCONF=RPI-B-testXXX > make -C $SRCROOT kernel-toolchain > make -C $SRCROOT KERNCONF=$KERNCONF WITH_FDT=yes buildkernel > make -j4 -C $SRCROOT MALLOC_PRODUCTION=yes buildworld > I tried this on a clean tree with just the patch applied. I didn't get the problem you're describing above. Can you check the patch applied cleanly. Can you run the failing command under script to get the build log? For example: $ script build.log make -j4 -C $SRCROOT MALLOC_PRODUCTION=yes buildworld will do a buildworld and save the output to the file build.log Andrew