Hi,
I just want to confirm if there is any known issue about using clang on SL5. Specially regarding the headers.
Thanks,
Miguel
Hi,
I just want to confirm if there is any known issue about using clang on SL5. Specially regarding the headers.
Thanks,
Miguel
http://stackoverflow.com/questions/7276828/
libc is buggy, clang stage 2 fails to build. This issue is fixed in SL6.
Dmitri
Dimitri,
Is the libc buggy in sl5 itself or the interaction with clang?
By stage two do you mean preprocesing?
Thanks,
Miguel
Is the libc buggy in sl5 itself or the interaction with clang?
libc expects different semantics from some C constructs. System gcc
implements them as expected by libc, so it was unnoticed.
By stage two do you mean preprocesing?
By stage 2 I mean second stage during bootstrap.
Dmitri
Hi Miguel,
I just want to confirm if there is any known issue about using clang on SL5. Specially regarding the headers.
I assume that SL5 is Scientific Linux 5, compatible with RHEL/CentOS 5
We're using clang 3.2 on CentOS 5, it builds fine with stock GCC 4.1.2, and is able to build itself after adding '-fgnu89-inline' to CFLAGS
However, we had to build GDB 7.5.1 to debug clang-compiled binaries, stock one gives the following error:
Dwarf Error: Cannot handle DW_FORM_flag_present in DWARF reader
Hope this helps.