From: Marius Bakke <mbakke@fastmail.com>
To: "B. Wilson" <x@wilsonb.com>, 29113@debbugs.gnu.org
Subject: bug#29113: Warnings when starting vim: Relink <libpng/libfreetype> with <libpthread> for IFUNC symbol `longjmp'
Date: Wed, 22 Nov 2017 19:34:15 +0100 [thread overview]
Message-ID: <87po8ap3h4.fsf@fastmail.com> (raw)
In-Reply-To: <20171102051501.37coaia27mrpb5xg@lang>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
"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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-11-22 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 5:15 bug#29113: Warnings when starting vim: Relink <libpng/libfreetype> with <libpthread> for IFUNC symbol `longjmp' B. Wilson
2017-11-02 13:58 ` ng0
2017-11-22 18:34 ` Marius Bakke [this message]
2017-11-24 13:25 ` Ludovic Courtès
2017-11-25 16:38 ` Leo Famulari
2019-02-26 3:18 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po8ap3h4.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=29113@debbugs.gnu.org \
--cc=x@wilsonb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.