From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] gettext missing symlink message
Date: Sun, 12 May 2013 21:57:39 -0400 [thread overview]
Message-ID: <20130513015739.GA8625@waltdnes.org> (raw)
I ran into this today while installing Gentoo on my new machine.
making executable: usr/lib64/preloadable_libintl.so
.[33;01m * .[39;49;00mQA Notice: Missing soname symlink(s):
.[33;01m * .[39;49;00m
.[33;01m * .[39;49;00m usr/lib64/libgnuintl.so.8 -> preloadable_libintl.so
.[33;01m * .[39;49;00m
https://bugs.gentoo.org/show_bug.cgi?id=374545 was opened in July of
2011 (YES!!!). I don't want to bug the developers. My questions are...
1) does it cause any problems?
2) is the appropriate workaround to...
cd /usr/lib64
ln -s preloadable_libintl.so libgnuintl.so.8
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next reply other threads:[~2013-05-13 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 1:57 Walter Dnes [this message]
2013-05-13 6:19 ` [gentoo-user] gettext missing symlink message Samuli Suominen
2013-05-13 6:21 ` Samuli Suominen
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=20130513015739.GA8625@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox