-
-
Notifications
You must be signed in to change notification settings - Fork 679
Bug: unsupported -v option by cosmocc #1316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The issue is I don't know what to put in there.
We can't supply a lot of that information in our frontend. What information does your configure script try to parse out? |
Thread model: ... |
I also stumbled upon this. My project build system extracts compiler brand (GCC / Clang / possibly TCC etc) and version via It then dumps target triplet via Currently this is how it looks when trying to build RVVM with $ make bin CC="cosmocc" 11:57:29
[INFO] Assuming target OS=Linux, set explicitly if cross-compiling
[INFO] Assuming target ARCH=x86_64, set explicitly if cross-compiling
Detected OS: Linux
Detected CC: Unknown 14.1.0
Target arch: x86_64
Version: RVVM 0.7-c0225c9-dirty
This is how it works when supplying all the info manually, but point is that I'd prefer my build system to figure it automatically at least for known targets: $ make bin CC="cosmocc" ARCH=x86_64_arm64 OS=Cosmopolitan CC_BRAND=gcc
Detected OS: Cosmopolitan
Detected CC: GCC 14.1.0
Target arch: x86_64_arm64
Version: RVVM 0.7-c0225c9-dirty |
Contact Details
ivmai/bdwgc#666
What happened?
Hello,
cosmocc does not recognize "-v" option (extended version info). Such information could be used during configure of 3rd-party packages (e.g. bdwgc), e.g. to determine threads API, e.g. like this.
Not a bug, but a kind of missing functionality compared to gcc/clang.
Both gcc and clang output such info at least: compiler version, target and thread model, e.g.:
Version
cosmocc (GCC) 14.1.0
What operating system are you seeing the problem on?
Linux
Relevant log output
The text was updated successfully, but these errors were encountered: