[cfe-dev] another try: lastest ubuntu 14.10 + gcc4.9.1 can't build clang

[Marc J. Driftmeyer]

You can never have too much RAM.

The FX-8350 with 32GB Ram just screams on builds.

- Marc

On 02/10/2015 06:26 AM, Dennis Luehring wrote:
>> you're getting "ld terminated with signal 9 [Killed]" instead.
>> which suggests that you don't have enough ram (maybe you're using a 
>> 32-bit
>> linux?
>
> i've got an ubuntu 14.10 x64 VM with 4GB of RAM(3GBs free for compile)
>  - before your post ~2GBs - more RAM is currenlty not possible
> that amount of RAM let me compile more then before but still stops 
> with ld terminated with signal 9
>
> what amount of RAM is currently needed for building clang head? it 
> wasn't that much before
>> I believe the ::max_align_t problem was fixed in
>> http://llvm.org/viewvc/llvm-project?rev=201729&view=rev which is part of
>> clang 3.5 (but not 3.4). So if you're using a recent clang, you 
>> shouldn't
>> see this problem. It sounds like you're indeed not seeing this 
>> problem with
>> clang head;
>
> not with gcc4.9.1 but it seems with gcc4.9.2 
> (https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+build/6539169)
> i will retest if i get more RAM for my tests
>
>
> Am 09.02.2015 um 16:55 schrieb Nico Weber:
>> I believe the ::max_align_t problem was fixed in
>> http://llvm.org/viewvc/llvm-project?rev=201729&view=rev which is part of
>> clang 3.5 (but not 3.4). So if you're using a recent clang, you 
>> shouldn't
>> see this problem. It sounds like you're indeed not seeing this 
>> problem with
>> clang head; you're getting "ld terminated with signal 9 [Killed]" 
>> instead.
>> Searching for this error message finds
>> http://stackoverflow.com/questions/5682854/why-is-the-linker-terminating-on-me-when-i-build-clang 
>>
>> which suggests that you don't have enough ram (maybe you're using a 
>> 32-bit
>> linux?)
>>
>> > libstdc++ is designed to work with gcc only. So if you want to avoid
>> > these issues, you either need to patch libstdc++ or use libcxx 
>> instead.
>>
>> While it is true that libstdc++ is developed in parallel with gcc, clang
>> explicitly tries to be able to parse it. If it doesn't, that's a 
>> clang bug.
>> Patching your system headers isn't the right thing to do.
>>
>>
>> On Mon, Feb 9, 2015 at 5:03 AM, Markus Trippelsdorf 
>> <markus at trippelsdorf.de>
>> wrote:
>>
>> >
>> >
>> > On 2015.02.09 at 13:59 +0100, Dennis Luehring wrote:
>> > > is this patch always needed for gcc 4.9.2 / ubuntu 14.04 support
>> > > or should the usage be fixed in the llvm/clang svn source?
>> >
>> > libstdc++ is designed to work with gcc only. So if you want to avoid
>> > these issues, you either need to patch libstdc++ or use libcxx 
>> instead.
>> >
>> > --
>> > Markus
>> >
>> > _______________________________________________
>> > cfe-dev mailing list
>> > cfe-dev at cs.uiuc.edu
>> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>> >
>>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

-- 

Marc J. Driftmeyer

email:mjd at reanimality.com <mailto:%27mjd at reanimality.com%27>
www:www.reanimality.com <http://www.reanimality.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150210/5a7d8213/attachment.html>