What's the recipe?

[Mark R V Murray]

On 1 Sep 2013, at 14:50, Tim Kientzle <tim at kientzle.com> wrote:

> 
> On Sep 1, 2013, at 4:07 AM, Takeshi Taguchi <taguchi949 at gmail.com> wrote:
> 
>> On Sat, 31 Aug 2013 13:37:04 -0400
>> George Mitchell <george+freebsd at m5p.com> 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?
>> there are no secrets ;-)
>> 
>>> 1. What system did you do the build on?  If it was an i386 or amd64,
>>> what svn version was it built with?
>> amd64 on virtualbox.
>> # uname -a
>> FreeBSD amd64-01 10.0-CURRENT FreeBSD 10.0-CURRENT #10 r255093M: Sat Aug 31
>> 21:41:10 JST 2013     root at amd64-01:/usr/obj/usr/src/sys/VIRTUALBOX  amd64
>> 
>>> 
>>> 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 use same make|src.conf for pi and amd64.
>> % egrep -v ^# /etc/make.conf
>> COPTFLAGS= -O -pipe
>> TOP_TABLE_SIZE= 101
>> 
>> WITH_PKGNG=YES
>> NO_WERROR=
>> WERROR=
>> PERL_VERSION=5.14.4
>> WITH_NEW_XORG=yes
>> 
>> % egrep -v ^# /etc/src.conf
>> MALLOC_PRODUCTION=YES
>> 
>> i think we stil need MALLOC_PRODUCTION. because jemalloc issue
>> does not fixed yet.
> 
> Note that Crochet has
> 
>  SRCCONF=/dev/null
>  __MAKE_CONF=/dev/null
> 
> by default.  You can override those in your Crochet configuration file
> if you wish.

Thanks!

I've spent the weekend trying to get a crochet build for Raspberry Pi going by various means. My build box is CURRENT as of Sept 1 2013, and is an AMD86. The only things in /etc/(make|src).conf are to remove stuff like CTM, LPR and other things of little relevance.

CURRENT + crochet cannot build u-boot because it looks like the antique CURRENT/GCC-xdev can't handle a couple of command-line options that u-boot wants (-fstack-usage, the other is hiding), but if I remove those it eventually fails with redefinitions of things like __packed, __pure and so on (this is GCC "armv6-freebsd-gcc", not CLANG).

I tried to hack up a u-boot port using the Beaglebone Black u-boot port as an example; that needs devel/arm-eabi-gcc which fails because of redefinition of some functions during the build.

I'm pretty stuck here without going on a major debugging mission - has anyone got a reliable build going, please?

M
-- 
Mark R V Murray

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 353 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20130902/a9aeaab4/attachment.sig>