<div dir="ltr"><div class="">On 03/03/15 07:49, Sedat Dilek wrote:<br>
</div>
<blockquote cite="mid:CA+icZUXZ9FGymyFWJmrnsjLiJJP7rPFrQDyNXybF86vFC2Pxvg@mail.gmail.com" type="cite">
<pre>BTW, LLVM project is offering prebuilt-binaries for modern (Linux) OS
on the download-page.</pre>
</blockquote>Yes. We are well aware of that.<br>
<br>
<blockquote cite="mid:CA+icZUXZ9FGymyFWJmrnsjLiJJP7rPFrQDyNXybF86vFC2Pxvg@mail.gmail.com" type="cite">
<pre>Ubuntu/precise (12.04) is no more supported, but Ubuntu/trusty (14.04) [2].
Both are Ubuntu LTS releases with 5 years support.</pre>
</blockquote>
The packages on <a href="http://llvm.org">llvm.org</a> for Ubuntu and debian are now available via
Xorg-edgers ppa (for Ubuntu) and I believe in sid (for debian).
Sylvestre Ledru (of Debian) builds all these packages.<br>
<br>
For Ubuntu:<br>
<br>
<a href="https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa">https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa</a><div><br></div><div>I actually just use these packages since Sylvestre updates them very regularly. I haven't had to build stable nor tip versions of clang for a few months now.<br>
<br>
<blockquote cite="mid:CA+icZUXZ9FGymyFWJmrnsjLiJJP7rPFrQDyNXybF86vFC2Pxvg@mail.gmail.com" type="cite">
<pre>Do you happen to know if LLVM/Clang has all bits to build a Linux-kernel now?</pre>
</blockquote>
Essentially. Though there are still things we need fixed (hence the open
LLVM bugs that we work around with kernel patches) clang 3.6 should
mostly just work.<br>
<br>
<blockquote cite="mid:CA+icZUXZ9FGymyFWJmrnsjLiJJP7rPFrQDyNXybF86vFC2Pxvg@mail.gmail.com" type="cite">
<pre>( If this is the case, people can now focus on the Linux "clang" patches. )</pre>
</blockquote>
That's essentially been the case for the last while. That's been most of our focus recently.<br>
<br>
Behan<br>
<pre class="" cols="72">--
Behan Webster
<a href="mailto:behanw@converseincode.com">behanw@converseincode.com</a></pre></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 3, 2015 at 7:49 AM, Sedat Dilek <span dir="ltr"><<a href="mailto:sedat.dilek@gmail.com" target="_blank">sedat.dilek@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Mar 2, 2015 at 10:59 AM, Daniel Sanders<br>
<<a href="mailto:Daniel.Sanders@imgtec.com">Daniel.Sanders@imgtec.com</a>> wrote:<br>
> Hi,<br>
><br>
> I'm not 100% certain but I don't think the manual build instructions are intended to be a reflection of what the Makefiles do. They're just instructions that will get you a bootable kernel.<br>
><br>
> Either way, the only difference between --enable-assertions and --disable-assertions is how debug-able the compiler is. It has no effect on the resulting kernel.<br>
><br>
<br>
</span>Not sure if I understood you correct.<br>
<br>
Which Makefile are you speaking of?<br>
llvmlinux, llvm, clang, linux, etc.?<br>
<br>
I rely on what the experts recommend on the clang website [1].<br>
Why should llvmlinux go a different way?<br>
Not clear to me.<br>
<br>
In the early days before there was "llvmlinux" project I encouraged<br>
that team to provide one toolchain to users/customers.<br>
So, if interested party is building his/her toolchain we might have a<br>
problem outside of llvmlinux in the toolchain area.<br>
Normally, I like to play with upstream, but in the case of llvmlinux I<br>
would like to see "stable" toolchain releases against stable releases<br>
of toolchain and LTS Linux-kernels.<br>
<br>
BTW, LLVM project is offering prebuilt-binaries for modern (Linux) OS<br>
on the download-page.<br>
Ubuntu/precise (12.04) is no more supported, but Ubuntu/trusty (14.04) [2].<br>
Both are Ubuntu LTS releases with 5 years support.<br>
<br>
Do you happen to know if LLVM/Clang has all bits to build a Linux-kernel now?<br>
This is more interesting to me.<br>
( If this is the case, people can now focus on the Linux "clang" patches. )<br>
<br>
- Sedat -<br>
<br>
[1] <a href="http://clang.llvm.org/get_started.html" target="_blank">http://clang.llvm.org/get_started.html</a><br>
[2] <a href="http://llvm.org/releases/3.6.0/clang+llvm-3.6.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz" target="_blank">http://llvm.org/releases/3.6.0/clang+llvm-3.6.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz</a><br>
<div class="HOEnZb"><div class="h5"><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:llvmlinux-bounces@lists.linuxfoundation.org">llvmlinux-bounces@lists.linuxfoundation.org</a> [mailto:<a href="mailto:llvmlinux-">llvmlinux-</a><br>
>> <a href="mailto:bounces@lists.linuxfoundation.org">bounces@lists.linuxfoundation.org</a>] On Behalf Of Sedat Dilek<br>
>> Sent: 27 February 2015 09:29<br>
>> To: llvmlinux<br>
>> Subject: Re: [llvmlinux] Website: Manual_Build_Instructions<br>
>><br>
>> Ping!?<br>
>><br>
>> - Sedat -<br>
>><br>
>> On Wed, Feb 4, 2015 at 12:54 AM, Sedat Dilek <<a href="mailto:sedat.dilek@gmail.com">sedat.dilek@gmail.com</a>><br>
>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> > I am planning to build a llvm-toolchain v3.6.0-rc2 on my own.<br>
>> ><br>
>> > Gasping at [1] shows a wrong configure-parameter...<br>
>> > ...<br>
>> > ./configure --prefix=$(echo ~/llvm4linux)/out/llvm --enable-optimized<br>
>> > --disable-assertions --targets=x86,x86_64,arm<br>
>> > ...<br>
>> ><br>
>> > Looking at the source of llvmlinux-git says...<br>
>> ><br>
>> > $ grep able-assertions -nr ./<br>
>> > ./toolchain/clang/clang-from-source.mk:99:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/x86_64/checkpoints/v3.14/config.mk:7:LLVM_OPTIMIZED<br>
>> > = --enable-optimized --enable-assertions<br>
>> > ./targets/x86_64/checkpoints/kernel-3.10-<br>
>> rc7/config.mk:7:LLVM_OPTIMIZED<br>
>> > = --enable-optimized --enable-assertions<br>
>> > ./targets/x86_64/checkpoints/kernel-3.13-<br>
>> rc4/config.mk:7:LLVM_OPTIMIZED<br>
>> > = --enable-optimized --enable-assertions<br>
>> > ./targets/x86_64/checkpoints/v3.3/config.mk:7:LLVM_OPTIMIZED<br>
>> > = --enable-optimized --enable-assertions<br>
>> > ./targets/nexus7/checkpoint/ckp1.mk:7:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/nexus7/checkpoint/ckp3.mk:8:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/nexus7/checkpoint/ckp2.mk:7:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/rpi/checkpoint/ckp1.mk:7:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/rpi/checkpoint/ckp3.mk:11:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/rpi/checkpoint/ckp4.mk:11:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/rpi/checkpoint/ckp2.mk:8:LLVM_OPTIMIZED =<br>
>> > --enable-optimized --enable-assertions<br>
>> > ./targets/x86_64_tiny/checkpoints/llvm3.3-<br>
>> linux040a0a3/config.mk:7:LLVM_OPTIMIZED<br>
>> > = --enable-optimized --enable-assertions<br>
>> ><br>
>> > So, this should be changed from "--disable-assertions" to<br>
>> > "--enable-assertions" on the website.<br>
>> ><br>
>> > Regards,<br>
>> > - Sedat -<br>
>> ><br>
>> > [1] <a href="http://llvm.linuxfoundation.org/index.php/Manual_Build_Instructions" target="_blank">http://llvm.linuxfoundation.org/index.php/Manual_Build_Instructions</a><br>
>> > -> "Checkout LLVM and clang"<br>
>> _______________________________________________<br>
>> LLVMLinux mailing list<br>
>> <a href="mailto:LLVMLinux@lists.linuxfoundation.org">LLVMLinux@lists.linuxfoundation.org</a><br>
>> <a href="https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux</a><br>
_______________________________________________<br>
LLVMLinux mailing list<br>
<a href="mailto:LLVMLinux@lists.linuxfoundation.org">LLVMLinux@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Behan Webster<div><a href="mailto:behanw@converseincode.com" target="_blank">behanw@converseincode.com</a></div></div>
</div>