-
Notifications
You must be signed in to change notification settings - Fork 5
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
darwin-xtools-1-1-0 fails to build on 10.5.8 with gcc7 #6
Comments
@iains I actually got the same error using newly-built gcc10. I guess I do something wrong at configure stage?
|
OK So there are two sources of build failure here, both of which result from modernisation of GCC (the 1-1-0 branch was originally built with gcc-5).
I've fixed these two - and the branch builds with gcc-5-4, gcc7-5 and gcc-10-3-ppc. BUT there are still some things to do - because we have a problem with conflicts between the GCC-installed libstdc++.dylib and /usr/lib/libstdc++ (this is not specific to xtools, it's a general problem). There are ways to work around it - but those involve building the other dependencies. So - some additional work is needed (I will see what can be done - but it's not going to be quick). |
Thank you so much! Once built, are these xtools to be used as replacements for Apple ones, or how to employ them for the good?
I will build whatever needed according to your guidelines (when you will get time to deal with this matter). P. S. It won’t hurt if I install these into 10A190 too, right? After building on 10.5.8 PPC as universal succeeds on my end, I wanna try building as ppc32 for 10.6 PPC (or if native build fails, pre-building on 10.5.8 probably works anyway). I know @kencu is very skeptical of 10.6, but I want to improve it and see where it may lead. So far only ppc64 support appears to be a major issue on it – but it is problematic even on 10.5.8: for example, none of python3* builds correctly for ppc+ppc64 by Macports (actually they didn’t build at all, I have made patches to them, and now they build through completion, but some modules remain unusable). |
First: However I do use the standard as / ld on every Darwin platform where possible - so for building GCC etc there is no need for xtools.
Some more time will be needed .
Same comment as above, use the tools from Xcode unless there is a problem.***
My main interest is in improving ppc64 (I have several ppc32 machines, but they are really too slow for the modern compilers - my oldest AGP G4 takes ≈ 1 week to build and test GCC)... ==== |
I am having problems with Apple ld linker time to time, especially when trying to build ports on 10.5.8 as universal. LLVM, even as ancient as 3.3, fails to build for ppc64 with some ranlib errors. One big thing I was trying to accomplish is make Stan work. I am yet to try new gcc10 with it. Hopefully it improves things, since with gcc7 I was able to build required libraries and even install Rstan after one of its developers made a custom version that didn't require libv8 (which fails on ppc), but model compilation failed.
Do you think it may be feasible to bring back support of ppc64 into 10A190? Porting some components from 10.5.8 (which was released after 10A190) and rebuilding from sources other.
Sure! Making gcc10 build was the best New year gift already. I will be patient. |
please could we try moving general discussion on what is possible / methods for doing things etc. to a central place - I think stuff will get lost in the issues. here: https://github.com/iains/darwin-toolchains-start-here/discussions So maybe we want topics on ppc, ppc64, llvm on ppc etc. |
Would be awesome, yes. I bookmarked that page, and we can move all info to there. |
@iains From what I understood, P. S. Again, asking not out of curiosity: if |
The text was updated successfully, but these errors were encountered: