Closed celaus closed 7 years ago
Found the issue - for some reason ring uses the g++ compiler (which isn't installed in the docker container) for compiling a .cc file. I will raise an issue there :)
For anyone hitting the same bump, this is a workaround. Make will use the environment variable to bootstrap its compiler definitions:
docker run -i --rm -e CXX=arm-linux-gnueabihf-gcc-with-link-search -v $(pwd):/source dlecan/rust-crosscompiler-arm:stable
Hi, thank you for reporting this issue. I'm happy you have found a workaround, but I don't understand:
CC
and CXX
variables are defined to use shell scripts, located here:
Each of them use Linaro gcc and g++ compilers (arm-linux-gnueabihf-gcc and arm-linux-gnueabihf-g++).
In your workaround, you override CXX
with the same value as for CC
, and it works. Great ! But I don't understand why !
Any idea ?
hmm yes, Ring's Makefile used (they seem to have removed them now) CXX
by default to compile .cc files and Environment variables override makefile variables usually; and for some reason it could not find g++ at the time. Using gcc was a good fix, since the .cc file does not require C++ features anyway and it was found :)
This might have been fixed now, since ring
seemed to have removed the Makefiles in the meantime :)
Hi,
I have noticed that compiling ring the g++ compilation (or linking?) step fails with "permission denied"
Steps to reproduce:
cargo init t --bin
Replace
Cargo.toml
with this version:Then
(to make sure, I was doing that in
/tmp
and even tried chmod 777 and re-compiled)Results:
Any advice?