Date: Thu, 1 Aug 2013 23:19:03 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Mark R V Murray <mark@grondar.org> Cc: "freebsd-arm@freebsd.org" <arm@freebsd.org> Subject: Re: RFC: sysutils/u-boot-beaglebone-eabi Message-ID: <EC0A43F1-D24F-4D00-837E-E4E46C962CE3@freebsd.org> In-Reply-To: <1D89CA5C-4C52-4669-8239-935CE3904469@grondar.org> References: <A8C10E4A-3577-4334-A916-381E69688137@freebsd.org> <1D89CA5C-4C52-4669-8239-935CE3904469@grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_5222E83A-AA62-44D2-A20A-92F681234C86
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=us-ascii
On Aug 1, 2013, at 12:14 AM, Mark R V Murray wrote:
>
> On 1 Aug 2013, at 04:45, Tim Kientzle <kientzle@freebsd.org> wrote:
>
>> P.S. By the way, to make this work, I had to add real ARM cross-compiler
>> ports. We now have devel/arm-eabi-binutils and devel/arm-eabi-gcc
>
> Hi Tim,
>
> Does Clang/LLVM still not do this properly?
Nothing wrong. Clang/LLVM compiles U-Boot just fine
as far as I can tell. That's what I've been doing for months.
But I couldn't figure out how to make that work for the U-Boot port:
1) I need a cross-compiler the u-boot port can depend on.
I don't know a particularly clean way to depend on
the xdev tools that I was using before. It seemed much
easier to depend on another port.
2) Our port tree already had some basic framework for cross-GCC.
(Remember this is typically being cross-compiled for ARM
on i386 or amd64.) I had to fix that support a little to make it
work correctly, but the outline was already there.
3) I didn't see anything already in ports for cross-clang.
4) The base clang has some cross-build abilities, but
it's not really useful without ARM libc or binutils.
Is there some other approach that I overlooked?
Tim
--Apple-Mail=_5222E83A-AA62-44D2-A20A-92F681234C86
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
iQEcBAEBAgAGBQJR+09YAAoJEGMNyGo0rfFBAgMH/3ZiRepufzuhtDMOrfSbQoDn
ZsNzl8tIaMfKX/nhc5ExGDXP5jLR3rxgc/4styJgVQF5PSEzIErlyGAQG6uqWrhv
twGYP52OIFfKLVWunounTbX81wny3OPpGJpbTfEih9tyGg6lgcTvzDOpVPRpVuDy
iz1VvTzxMD7dluFszBN9XMl4fjo3XBxNOi0wQPxl7P85IQV+3Gf6ru2oQJ6jGGdQ
aTcXtAqmyuE2mnaAiutpH+HEUjnlSJ9jzwBBTfP4iva1zVij8flgSmVFXQM4ZusR
Q3v6nTVraFY51cw9OzuvsvvZgYlKfyTlbuNP6ivVa0SPI/e/ZBUVIhNoCywyUL4=
=at/I
-----END PGP SIGNATURE-----
--Apple-Mail=_5222E83A-AA62-44D2-A20A-92F681234C86--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC0A43F1-D24F-4D00-837E-E4E46C962CE3>