From: Robert Hancock <hancockrwd@gmail.com>
To: Wayne Pollock <pollock@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make xconfig fails on Fedora 10 for 2.6.30
Date: Fri, 10 Jul 2009 23:12:41 -0600 [thread overview]
Message-ID: <4A581F49.9090601@gmail.com> (raw)
In-Reply-To: <4A57BD9B.4030405@acm.org>
On 07/10/2009 04:15 PM, Wayne Pollock wrote:
> The "make xconfig" command tried to link to "libXi.so".
> I think this is actually a kernel bug; the binary this
> make command builds should try to link to some "soname"
> such as "libXi.so.6" instead, shouldn't it?
No, applications are generally supposed to link to the plain name, and
the resulting binary will end up linked to the version-specific name
because of the symlink. Applications don't generally need to know what
version of the library they're linking against, if they care they can
usually figure it out from the headers they are including.
>
> The work-around was to manually create the missing symlink
> for "libXi.so". I suspect other distro's install that
> symlink automatically so maybe that's why the bug was
> not discovered. But I believe it is correct to say all
> applications should use a soname (including the major
> version number), and not just the "linker" name (the
> name ending in ".so" with no version numbers).
>
> Or am I missing something?
Not a bug, the symlink is supposed to be there. (Could be you need to
install some devel package to get it..)
prev parent reply other threads:[~2009-07-11 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 22:15 make xconfig fails on Fedora 10 for 2.6.30 Wayne Pollock
2009-07-10 22:31 ` David Rees
2009-07-11 5:12 ` Robert Hancock [this message]
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=4A581F49.9090601@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pollock@acm.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