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
fix gcc5 build #55
fix gcc5 build #55
Conversation
Any chance we could update our GCC fork, instead of maintaining this old version? (ping @artart78) |
There is more to fix than just this gcc 5.1.0 issue actually. The produced static libraries don't export the _link symbol, which in turn makes every application that links to the libc / libstdc++ part of those fail to build. A makeshift way of getting this sorted is to add a dummy _link syscall to the source before building, a sample patch has been posted here: |
@MrColdbird the patch you point out doesn't change anything, _link is already defined here in newlib 1.20.0:
|
Then we need an explanation why this particular piece isn't getting linked in as a separate symbol. |
got it, it's because of the patch, _link is found in newlib/libc/sys/psp/libcglue.c:
and F__link is not defined anywhere
|
Sweet. Hope to see a commit on your github with it soon then so I can pull it in via your Arch package later today. |
unfortunately i get an error caused by multiple references to _link at final build |
see #56, it's another unrelated issue |
@artart78, @uppfinnarn, this one can be merged now, along with #56 |
Nicely done. |
@uppfinnarn, I tried to update the patch to the latest binutils / gcc versions, but IIRC binutils changed to much for the patch to be adapted. Some parts of it probably would need to be rewritten from scratch, and I don't think it's worth it. Thanks for the fixes @xantares ! |
gcc 4.6.4 must be patched in order to compile with gcc 5.1.0:
DragonFlyBSD/DPorts#136