Re: LLVM 6.0.1p8 fails to compile on 6.4-stable/loongson

Brian Callahan writes:

> On 12/12/18 2:51 AM, Xiyue Deng wrote:
>> Jeremie Courreges-Anglas writes:
>>
>>> On Mon, Dec 10 2018, Xiyue Deng <manphiz@gmail.com> wrote:
>>>
>>> [...]
>>>
>>>> Sounds great! It will be great to have it backported to -stable as
>>>> well.
>>> "will"
>>>
>>> Please keep in mind that development happens on -current. Backporting
>>> diffs from -current to -stable is not always straightforward.
>>>
>>> If you 6.4 users want a backport then why not Do It Yourself? :)
>> Well, this attempt failed with an ICE. The build log is attached. I
>> wonder whether it is because of "out of memory". I did have a 5G swap
>> besides the 1G memory though (with infinity settings in /etc/logins.conf).
>>
>
> If you're just looking to use clang and clang++ on loongson, you might
> be better off installing -current, which now includes /usr/bin/clang and
> /usr/bin/clang++ (and /usr/bin/ld.lld, though I haven't found it to be
> very useful atm). It'll be much faster than having to debug g++ problems
> and then actually build llvm.
>
> ~Brian

Thanks Brian, though I'd still like to stay at -stable because as I can
tell the snapshot packages for loongson are actually for -release. BTW,
should they also be copied to 6.4/packages as well?

Also, as you mentioned, /usr/bin/clang{,++} are available on loongson
-current, does that mean that loongson has also migrated to clang in
6.5? (If so that's fantastic news! :)

--
manphiz