From: Sqvid <Sqvid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] clang17 does not include header files
Date: Fri, 09 Feb 2024 13:45:57 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48621@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
New issue by Sqvid on void-packages repository
https://github.com/void-linux/void-packages/issues/48621
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.16_1 x86_64 AuthenticAMD uptodate rrFFFFF
### Package(s) Affected
clang17
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Installing clang should pull in the standard library headers so that you can actually compile programs. However `clang17` does not do this (one would need `clang17-devel`).
### Actual behaviour
Clang17 pulls in no headers and as a result cannot be used to compile C/C++ programs. Clang15 is unaffected.
Observe the difference between `xbps-query -Rf clang17` and `xbps-query -Rf clang15`
### Steps to reproduce
1. Install `clang17`
2. Paste the following in `main.c`:
```C
#include <stdio.h>
int main(void) {
printf("Hello, World!\n");
return 0;
}
```
3. run `clang main.c`
4. Obtain the error:
```C
In file included from test.c:1:
/usr/include/stdio.h:33:10: fatal error: 'stddef.h' file not found
33 | #include <stddef.h>
| ^~~~~~~~~~
1 error generated.
```
5. Cry.
next reply other threads:[~2024-02-09 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 12:45 Sqvid [this message]
2024-02-09 12:53 ` chrysos349
2024-02-10 4:24 ` Calandracas606
2024-02-12 21:59 ` Calandracas606
2024-02-12 22:43 ` [ISSUE] [CLOSED] " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48621@inbox.vuxu.org \
--to=sqvid@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).