-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update gcc to 10.1 and turn C++ support on #31
Conversation
It sounds like there is an issue around sysroot -- see https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html ? There might be useful information in https://elinux.org/images/1/15/Anatomy_of_Cross-Compilation_Toolchains.pdf and https://www.linuxfromscratch.org/lfs/view/stable/chapter05/glibc.html ? |
There is some talk about how libstdc++ and stuff need to be deferred as part of cross compiling at https://www.linuxfromscratch.org/lfs/view/stable/chapter05/gcc-libstdc++-pass1.html |
gcc-10 and above flipped a default from -fcommon to -fno-common. SH version of newlib has duplicate symbols after compiling with GCC 10.1.
For some reason the upload hangs, but all other jobs passed. Merging, I suspect a github hiccup here |
These changes update gcc to 10.1 and add C++ support for gcc with newlib.
This addresses #25.
Simply adding
c++
to--enable-lanaguages
does not work, as libstdc++-v3 compilation fails (example in run#3559265510).Relevant error
Updating
--prefix
config option helps and fixes compilation process.Unfortunately it doesn't run properly.
conda-build
rewrites the internal paths to get rid of the build prefix, but then gcc fails to locate necessary files. We can investigate that further in the next step.Adding
build/detect_binary_files_with_prefix: False
value to gcc/newlib/meta.yaml partially fixes the problem.gcc and g++ work correctly now, but simple
strings
execution reveals, that paths from build process are still present in the binaries.It doesn't seem to affect the gcc functionality though.