| Summary: | Patch: Clang does not honor -dN | ||
|---|---|---|---|
| Product: | uClibc | Reporter: | Jeffrey Walton <noloader> |
| Component: | Other | Assignee: | unassigned |
| Status: | NEW --- | ||
| Severity: | normal | CC: | uclibc-cvs |
| Priority: | P5 | ||
| Version: | 0.9.33.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
Please see http://uclibc.org/developing#contrib As for using a C++ compiler, NAK. Given how icc behaved last time i tried, thinking about piping our C-code through icpc and expecting any non-error output is just not realistic. Anyway. Please submit proper patches if you want them to be applied. TIA and cheers, (In reply to comment #1) > As for using a C++ compiler, NAK. :) |
$ diff -uN extra/scripts/gen_bits_syscall_h-orig.sh extra/scripts/gen_bits_syscall_h.sh --- extra/scripts/gen_bits_syscall_h-orig.sh 2013-02-27 22:43:03.053750592 -0500 +++ extra/scripts/gen_bits_syscall_h.sh 2013-02-27 22:39:38.160734579 -0500 @@ -18,6 +18,7 @@ INCLUDE_OPTS="-nostdinc -I${KERNEL_HEADERS}" case $CC in +*clang*) CC_SYSNUM_ARGS="-dM" ;; *icc*) CC_SYSNUM_ARGS="-dM" ;; *) CC_SYSNUM_ARGS="-dN" ;; esac Also, 'icc' is Intel's C compiler. To pick up the Intel C++ compiler, the project might want to add a case for 'icpc'.