Date: Mon, 24 Jun 2013 13:58:32 -0600 From: Warner Losh <imp@bsdimp.com> To: Jordan Hubbard <jordan.hubbard@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry pi not ready to self-host yet? Message-ID: <96A5DFDF-6601-405B-BA2F-527C256C0424@bsdimp.com> In-Reply-To: <B4EF71AD-FA65-4D56-AB1D-AA4C25277324@mail.turbofuzz.com> References: <800732D1-B06A-40AE-AE69-F6170662B2AA@turbofuzz.com> <3B1B1A39-13AF-4718-A9D6-757D6FEFC27F@bsdimp.com> <B4EF71AD-FA65-4D56-AB1D-AA4C25277324@mail.turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 24, 2013, at 12:36 PM, Jordan Hubbard wrote: >=20 > On Jun 24, 2013, at 8:01 AM, Warner Losh <imp@bsdimp.com> wrote: >=20 >>=20 >> On Jun 24, 2013, at 8:55 AM, Jordan K. Hubbard wrote: >>=20 >>> Hi folks, >>>=20 >>> I followed the instructions in the repo at = https://github.com/daveish/freebsd-arm-tools.git and was able to create = a bootable SD image for my 512Mb PI in no time with very little hassle - = nice job there! >>>=20 >>> What I can't seem to manage, however, is to self-host after that. = I see someone has already filed = http://www.freebsd.org/cgi/query-pr.cgi?pr=3D178495 covering the failure = during buildworld, You see the same compilation error in = basic_string.tcc in various ports, like apr: >>>=20 >>> 0. Program arguments: /usr/bin/c++ -cc1 -triple = armv6-unknown-freebsd10.0 -S -disable-free -main-file-name cxx_db.cpp = -mrelocation-model pic -pic-level 2 -mdisable-fp-elim = -mconstructor-aliases -target-abi apcs-gnu -target-cpu arm1136jf-s = -msoft-float -mfloat-abi soft -target-feature +soft-float = -target-feature +soft-float-abi -target-feature -neon -coverage-file = /tmp/cxx_db-5qpGsC.s -resource-dir /usr/bin/../lib/clang/3.3 -D = _THREAD_SAFE -D PIC -I . -I ./../dist/.. -O2 -fdeprecated-macro = -fno-dwarf-directory-asm -fdebug-compilation-dir = /a/ports/databases/db42/work/db-4.2.52/build_unix -ferror-limit 19 = -fmessage-length 144 -mstackrealign -fno-signed-char = -fobjc-runtime=3Dgnustep -fobjc-default-synthesize-properties = -fcxx-exceptions -fexceptions -fsjlj-exceptions = -fdiagnostics-show-option -fcolor-diagnostics -backend-option = -vectorize-loops -o /tmp/cxx_db-5qpGsC.s -x c++ = ./../dist/../cxx/cxx_db.cpp=20 >>> 1. /usr/include/c++/4.2/bits/basic_string.tcc:978:43: current = parser token ';' >>> 2. /usr/include/c++/4.2/bits/basic_string.tcc:48:1 = <Spelling=3D/usr/include/c++/4.2/bits/c++config.h:76:38>: parsing = namespace 'std' >>> c++: error: unable to execute command: Segmentation fault (core = dumped) >>> c++: error: clang frontend command failed due to signal (use -v to = see invocation) >>=20 >> do you have enough swap? Clang is a memory pig dog... >=20 > [root@pi /usr/obj/a/src/sys/RPI-B]# swapinfo > Device 512-blocks Used Avail Capacity > /dev/mmcsd0s2b 4194304 168 4194136 0% > /dev/da0b 8192000 312 8191688 0% > Total 12386304 480 12385824 0% >=20 > I don't think I'm hitting any memory limits, though I'll also note = that kern.maxswzone is compiled a bit on the small side since my =F0=9F=8D= =87=CF=80 always complains that it can't utilize the swap it has: >=20 > warning: total configured swap (1548288 pages) exceeds maximum = recommended amount (761152 pages). > warning: increase kern.maxswzone or reduce amount of swap. That's ~3GB, plus ~300MB of RAM... Not a good ratio, but still should = be plenty. I have a 4GB system without swap that can do an amd64 = build... > I tried raising this in /boot/loader.conf but it didn't seem to have = any effect. I assumed that perhaps the boot path was different on the = Pi and didn't put too much work into that. >=20 >> I've self-hosted FreeBSD on an Atmel AT91SAM9620 recently (arm v5 = board)... Seems odd that cross compile and native built give different = results. Will look into it. Btw, whats uname -p say for you? >=20 > armv6 That looks right... > Others have pointed out that clang may not be ready for prime-time yet = on ARM. I don't have much to compare with since Apple is already on = clang/LLVM 5.0 and FreeBSD is back with 3.3 - I don't even really = remember what the state of ARM support was that long ago. :-) heh. I thought we were more up to date :) Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96A5DFDF-6601-405B-BA2F-527C256C0424>