[RFC] external compiler support

[Brooks Davis]

On Tue, Feb 26, 2013 at 07:04:57PM -0800, Alfred Perlstein wrote:
> On 2/26/13 4:35 PM, Brooks Davis wrote:
> > Below (and at http://people.freebsd.org/~brooks/patches/xcc.diff) you
> > can find an initial patch with proposed commit for external compiler
> > support.  It relies on the existing cross binutils as I'm finding that
> > the two are fairly separable.  With this patch I've been able to build
> > from amd64 to arm, amd64, and i386 using clang from the lang/clang-devel
> > port.  I've also compiled the tree with a customized clang being
> > developed at the University of Cambridge.
> >
> > The patch is untested with gcc.
> >
> > Does this seem like a reasonable approach?  I do plan to look at external
> > binutils support, but it's not on the critical path for our current work
> > so I've opted to avoid it for now.
> >
> > As a bonus for those who don't need an external compiler, but do run
> > make buildworld frequently, the XCC, XCXX, and XCPP variables can be set
> > to the location of the installed base system compiler to avoid building
> > the compiler twice during buildworld.
> 
> This is very cool work and it's non-invasive.  Are there any downsides 
> to bringing it in?  (I can't see any).

Other than an increasing pile of code to set up the cross build
environment, I don't see a downside.  It should be a no-op for most
users.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20130227/de71f1f4/attachment.sig>