Hi, Marius Bakke <mba...@fastmail.com> skribis:
> "B. Wilson" <x...@wilsonb.com> writes: > >> Hello, >> >> I recently installed vim-full (8.0.1207) and it's throwing some linker (?) >> warnings at me on startup. The gory details are below, and any help getting >> to >> the bottom of this would be much appreciated. >> >> >> ## Errors >> >> $ vim -u NONE -esc # `-u NONE' disables .vimrc, `-esc q' quits immediately >> vim: Relink >> `/gnu/store/66bqq32pq33r3vz53kiwv36b7fqqprpy-libpng-1.6.29/lib/libpng16.so.16' >> with >> `/gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25/lib/libpthread.so.0' >> for IFUNC symbol `longjmp' >> vim: Relink >> `/gnu/store/xmsn5afiyqi206i5gm6qn4gab0aij80b-freetype-2.8/lib/libfreetype.so.6' >> with >> `/gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25/lib/libpthread.so.0' >> for IFUNC symbol `longjmp' > > Hello, > > This is a known problem in glibc that has recently been fixed AFAICT. > > https://sourceware.org/bugzilla/show_bug.cgi?id=21041 > > It was also "backported" to the 2.26 release branch: > > https://sourceware.org/git/?p=glibc.git;a=commit;h=88758c4ad3f046d050bc2c3ae0f172b6524ca6c2 > > We currently have 2.26 in 'core-updates' which hasn't started building > yet. Perhaps we should include this fix, thoughts? I’m unclear on the consequences of the bug, but merging the fix sounds like a good idea. Ludo’.
