-
Failed to compile:
/usr/bin/ld: /tmp/cc8KfO2F.o: in function `main':
:(.text.startup+0x188): undefined reference to `sqrt'
collect2: error: ld returned 1 exit status
Exited with error status 1
…
-
Today, I saw this warnings while clean build:
```
bash-5.2$ builddriver make
builddriver executing: 'make'
Compilation SUCCEED in 48.287564 seconds
Number of warnings: 30
WarningErrorEntry(path=…
-
![brave_WtmoIuaBky](https://github.com/user-attachments/assets/2e3f4e13-a9c2-47d5-95e5-bf51cec7f197)
![cmd_Q5muz7UIcA](https://github.com/user-attachments/assets/60fc511d-16a0-4c93-aeb4-2d819302d8a…
-
When you don't use tox, you see this in the build log:
```
gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC -I/opt/hostedtoolcache/Python/3.12.0/x64/lib/python3.12/site-packages…
pllim updated
1 month ago
-
show "Failed to find C compiler. Please specify via CC environment variable . ", use sageatten
-
Hi guys, i have this problem to install:
![image](https://github.com/user-attachments/assets/5bbcf8dd-e8e6-4979-b998-cbb44484169a)
-
On FreeBSD cargo-c uses the "cc" executable, which is at odds with the ports' ability to override the C and C++ compilers.
How to make cargo-c to always use the CC environment variable?
-
Fix past goof with #21968
```
@clin1234 ➜ /workspaces $ venv/bin/pip install -U --pre --no-build-isolation git+https://github.com/scipy/scipy
Collecting git+https://github.com/scipy/scipy
Clon…
-
raise RuntimeError("Failed to find C compiler. Please specify via CC environment variable.")
RuntimeError: Failed to find C compiler. Please specify via CC environment variable.
-
### What happened?
The `Main distribution (Linux for Arm64)` step (calling `build_tools/github_actions/build_dist.py main-dist`) in the `Build Release Packages` workflow fails as `ConfigTrackingCanon…