-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
glibc: update to glibc-2.25 #1616
Conversation
I'll test this PR with this additional commit: http://sprunge.us/dPVR If that works OK, then I'll include it in this PR. |
I see you also unset LD_LIBRARY_PATH (I'm still building with). For this to be sure it is ok we need to build all projects from scratch. Maybe something would pop up :) |
the Addons should built, too. |
All the projects (RPi, RPi2, Generic, imx6, Odroid_C2, WeTek_*) have built for me with LE master + #1612 + #1616, so dropping/unsetting "LD_LIBRARY_PATH" doesn't seem to be a problem. I've run-time tested RPi/RPi2/Generic, and no obvious issues. I also rebuilt the same addons I tested in #1612, and no new issues: Generic::
RPi/RPi2:
I've updated the libnfs patch using the upstream fix sahlberg/libnfs@5b28ab5 @InuSasha: Hopefully with these updates (PR1612+PR1616) the jump to gcc-7.1 should be less painful, though maybe wait for gcc-7.2? There's a gcc-6.3 bump available which might be another option. If anyone wants to update gcc in a separate PR, feel free! |
PS. all add-ons and binary add-ons should be bumped using the |
Build was fine here too. Run-time test will follow. |
Sounds like a script to do that would come in handy... Is it just a matter of iterating over addons and |
@MilhouseVH
|
Ok will take a look and add a commit to this PR |
glibc: don't build and install programs fontconfig: fix build with glibc-2.25 libnfs: fix build with glibc-2.25
|
I've removed |
In relation to gcc-7.1, message from @stefansaraev (seo) on #irc:
|
Continuing discussion from #1612 (comment)
glibc-2.25 changelog: https://sourceware.org/ml/libc-alpha/2017-02/msg00079.html
The trailing colon added to LD_LIBRARY_PATH is breaking the glibc build. Also llvm will create unusable
llvm-config-host
causing mesa to fail. These issues were first raised in #1086 (thanks @InuSasha).Question is: should we simply
unset LD_LIBRARY_PATH
, is prefixing with $TOOLCHAIN/lib required at all? More testing needed...