[llvm] r202486 - [docs] Add a big section with details about how to go about acquiring

Eric Christopher echristo at gmail.com
Tue Mar 4 14:14:59 PST 2014


On Tue, Mar 4, 2014 at 2:09 PM, Hal Finkel <hfinkel at anl.gov> wrote:
> ----- Original Message -----
>> From: "Chandler Carruth" <chandlerc at gmail.com>
>> To: "Hal Finkel" <hfinkel at anl.gov>
>> Cc: "Chandler Carruth" <chandlerc at gmail.com>, "Commit Messages and Patches for LLVM" <llvm-commits at cs.uiuc.edu>
>> Sent: Tuesday, March 4, 2014 3:14:26 PM
>> Subject: Re: [llvm] r202486 - [docs] Add a big section with details about how to go about acquiring
>>
>>
>>
>>
>>
>> On Tue, Mar 4, 2014 at 1:06 PM, Hal Finkel < hfinkel at anl.gov > wrote:
>>
>>
>>
>>
>> > Because Clang/LLVM 3.4 don't provide an installed-out-of-the-box
>> > well
>> > tested standard library implementation for Linux, and as mentioned
>> > at the start of the comment section, this is largely a Linux
>> > section.
>>
>> So the issue is just that libc++'s build system is wacky? I've never
>> built libc++ with cmake -- preferring instead my patched version of
>> the 'buildit' script ;) -- , but is the cmake setup from 3.4 usable?
>> Or is testing on Linux the major issue?
>> The build setup with cmake is getting better, but not perfect yet.
>> The testing on linux is also an issue. I think these are *all* show
>> stopper problems for recommending this as the one stop host
>> toolchain on Linux.
>
> Fair enough.
>
> Different issue, having done this (used gcc 4.8), is it worth warning people that, unless they also upgrade their gdb, they'll have trouble debugging the resulting binaries?
>

Eh? What problems have you run in to there?

-eric



More information about the llvm-commits mailing list