Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jan 2009 09:30:40 -0600 (CST)
From:      "Sean C. Farley" <scf@FreeBSD.org>
To:        Pegasus Mc Cleaft <ken@mthelicon.com>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?)
Message-ID:  <alpine.BSF.2.00.0901150917440.1930@thor.farley.org>
In-Reply-To: <9225949D37F24E01AA5FC01169A256F2@PegaPegII>
References:  <de2964020901141507m5a30c466ta1e05694d220ce0b@mail.gmail.com><20090115084515.GA91157@freebsd.org> <496F0D1D.7080505@andric.com> <6c51dbb10901150344s409cd834p3cd8fae189e42a68@mail.gmail.com> <9225949D37F24E01AA5FC01169A256F2@PegaPegII>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Jan 2009, Pegasus Mc Cleaft wrote:

*snip*

> I dont know clang, llvm, pcc, etc. very well, but.. Would this solve 
> our problem where we will still need an assembler, linker, archiver, 
> et al?

For assembler, Yasm looks like a possibility, but I have only glanced at 
it.  I think pcc can use it.  There is also Fasm.  Both are 
BSD-licensed.  Actually, Yasm is mostly BSD-licensed.  It depends on the 
bitvect library which is Artistic/GPL/LGPG-licensed.  Yasm may support 
more platforms, and it does accept Gas syntax.

For an archiver, what about tar (bsdtar)?  tar tf /usr/lib/libc.a works 
for me.  :)  Actually, there is some development[1] to replace those 
utilities with BSD-licensed versions.  ar has already been replaced in 
HEAD.

Sean
   1. http://wiki.freebsd.org/ElfToolChain
-- 
scf@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0901150917440.1930>