<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 30/03/13 15:30, Joe Groff wrote:<br>
</div>
<blockquote
cite="mid:CALz=kuhf2uu5QQckX5+7mbTJOQU6Q61csge387mHtdxMt=_LUA@mail.gmail.com"
type="cite">
<div dir="ltr">On Sat, Mar 30, 2013 at 5:46 AM, Ikey Doherty <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:ikey@solusos.com" target="_blank">ikey@solusos.com</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">So
I tried building various other components with Clang.
Notable (and well known) failures include GLibc and the
kernel. I find it more insulting that the standard
components put forth by GNU (such as glibc) rely on their
own non-standard extensions. Simply put: If you want to
use one, you must use all. The case extends to binutils,
gcc, etc.<br>
</blockquote>
<div><br>
</div>
<div style="">Mainline Linux and glibc are likely to depend
on GCC for the foreseeable future, but you may be
interested in investigating the LLVMLinux project, which
has a fork of the kernel that compiles with clang: <a
moz-do-not-send="true"
href="http://llvm.linuxfoundation.org/index.php/Main_Page">http://llvm.linuxfoundation.org/index.php/Main_Page</a></div>
<div style=""><br>
</div>
<div style="">-Joe</div>
</div>
</div>
</div>
</blockquote>
Thank you Joe, definitely looks like something I'll be wanting. I'll
get a clean sysroot put together and try that one out in Qemu. I
guess the easiest compromise would be to resort to GCC only when
absolutely required, meaning over the lifetime of SolusOS 2 we could
wean out GCC-built packages and replace them with Clang-built ones.<br>
<br>
With that in mind, at least you'll gain a new set of testers for
feedback and bug reporting with Clang/llvm :)<br>
</body>
</html>