Bug#783205: clang-3.5: fatal error: 'sys/cdefs.h' file not found

[Jakub Wilk]

Package: clang-3.5
Version: 1:3.5-10
Severity: grave
User: debian-***@lists.debian.org
Usertags: s390x

On s390x, the compiler can't find standard C headers:

$ clang-3.5 -c test.c
In file included from test.c:1:
In file included from /usr/include/stdio.h:27:
/usr/include/features.h:374:12: fatal error: 'sys/cdefs.h' file not found
# include <sys/cdefs.h>
^
1 error generated.


-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: s390x

Kernel: Linux 3.2.0-4-s390x (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages clang-3.5 depends on:
ii binutils 2.25-5
ii libc6 2.19-18
ii libc6-dev 2.19-18
ii libclang-common-3.5-dev 1:3.5-10
ii libclang1-3.5 1:3.5-10
ii libedit2 3.1-20140620-2+b1
ii libffi6 3.1-2+b2
ii libgcc-4.9-dev 4.9.2-10
ii libgcc1 1:4.9.2-10
ii libllvm3.5 1:3.5-10
ii libobjc-4.9-dev 4.9.2-10
ii libstdc++-4.9-dev 4.9.2-10
ii libstdc++6 4.9.2-10
ii libtinfo5 5.9+20140913-1+b1
ii zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages clang-3.5 recommends:
pn llvm-3.5-dev <none>
ii python 2.7.9-1

[Sylvestre Ledru]

Hello,

Post by Jakub Wilk
Package: clang-3.5
Version: 1:3.5-10
Severity: grave
Usertags: s390x
$ clang-3.5 -c test.c
/usr/include/features.h:374:12: fatal error: 'sys/cdefs.h' file not found
# include <sys/cdefs.h>
^
1 error generated.

I am quite busy these days. I won't have the time to look at it before a few weeks.

We probably have to update this code:
http://sources.debian.net/src/llvm-toolchain-3.5/1:3.5-10/clang/lib/Driver/ToolChains.cpp/#L1396

Cheers,
Sylvestre

[Debian Bug Tracking System]

Your message dated Wed, 19 Aug 2015 09:46:24 +0100
with message-id <***@web171804.mail.ir2.yahoo.com>
and subject line
has caused the Debian Bug report #783205,
regarding clang-3.5: [s390x] fatal error: sys/cdefs.h file not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)