Date: Mon, 24 Jun 2013 21:51:15 -0700 From: Tim Kientzle <tim@kientzle.com> To: "Jordan K. Hubbard" <jkh@turbofuzz.com> Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry pi not ready to self-host yet? Message-ID: <6A7EDC6F-7441-47D4-BAF4-661207C5E737@kientzle.com> In-Reply-To: <800732D1-B06A-40AE-AE69-F6170662B2AA@turbofuzz.com> References: <800732D1-B06A-40AE-AE69-F6170662B2AA@turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 24, 2013, at 7:55 AM, Jordan K. Hubbard wrote: > You see the same compilation error in basic_string.tcc in various = ports, like apr: Now that's odd. I built apr just a couple of weeks ago (part of building subversion from ports) and it compiled okay on BeagleBone. So this might be very recent breakage. > I do appreciate that it's a heck of a lot easier to cross-compile for = these things, and great work getting things to this point, but = self-hosting is still one of the magical milestones you always hope an = embedded target will get to someday, assuming it actually has enough = grunt to do so (and I think the PI does). :) A few months back, I was able to self-host on the BeagleBone, so our armv6 support was doing pretty well at that time. I think that with the Clang and EABI switches, we've regressed a bit since then. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6A7EDC6F-7441-47D4-BAF4-661207C5E737>