GSoC: Making ports work with clang
roam at ringlet.net
Mon May 3 09:22:39 UTC 2010
On Sun, May 02, 2010 at 11:51:52PM +0300, Andrius Mork??nas wrote:
> On Sun, 02 May 2010 10:25:22 +0300, Yuri <yuri at rawbw.com> wrote:
> > Having tried clang++ I have a feeling that it's not quite ready to be a
> > generic c++ compiler.
> > Very immature.
> Many problems that C++ ports have with clang is not related to it being
> immature, they're related to the fact that clang isn't gcc and that
> those ports aren't written in standard C++.
> > You will just keep stumbling upon various problems with various ports
> I've mentioned that I've been involved with ports+clang since last
> October. "Stumbling upon various problems" is what I do. I'm still here,
> even doing a GSoC project, so it doesn't look like "various problems"
> will scare me off. And as I've mentioned above, just because some ports
> don't compile, it doesn't affect this project too much.
Well said, well meant. Kudos. Thanks for your work so far, and thanks
for taking up that GSoC project.
Peter Pentchev roam at ringlet.net roam at space.bg roam at FreeBSD.org
PGP key: http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
I am the meaning of this sentence.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 834 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20100503/1f3a98e0/attachment.pgp
More information about the freebsd-ports