On May 5, 2016 2:31:52 AM CDT, Pierre Labastie <pierre.labas...@neuf.fr> wrote:
>On 05/05/2016 03:48, DJ Lucas wrote:
>>
>>
>> On 05/04/2016 04:05 PM, Pierre Labastie wrote:
>>
>>>
>>> I confirm that GCC-6 is not easy to work with: OpenJDK would not
>build with
>>> it. I do not have CLANG and have no motivation to build it.
>Furthermore, for
>>> OpenJDK, the variables CC and CXX are not honoured! What I have done
>(as root):
>>>
>>> mv /usr/bin/gcc{,.orig}
>>> cat >/usr/bin/gcc << EOF
>>> #!/bin/bash
>>> gcc -std=c99 "\$@"
>>> EOF
>>> mv /usr/bin/g++{,.orig}
>>> cat >/usr/bin/g++ << EOF
>>> #!/bin/bash
>>> gcc -std=c99 "\$@"
>>> EOF
>>>
>>> But that's not enough. The compilation goes to completion, but all
>the
>>> compiled executables segfault
>>>
>>
>> http://hg.openjdk.java.net/jdk9/dev/rev/9d77f922d694
>>
>> That's for jdk9, but should backport easily enough. Looks like you
>need
>> -std=gnu++98, -fno-delete-null-pointer-checks, and -fno-lifetime-dse
>to make
>> it play nicely...can probably force it to work at configure time if
>you don't
>> want to redo auto* files, but that's the correct way (assuming that
>it
>> actually works).
>>
>> --DJ
>>
>>
>Thanks, will give it a try. Why do they have those big chunks of empty
>lines?
>
Honestly, I haven't the slightest clue. I hesitate to say that it's just a
mistake. Maybe it's nice to have a bit of play in auto files when digging
between different trees. :-/
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
