linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Lurndal <scott.lurndal@3leafsystems.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-numa@vger.kernel.org
Subject: Re: Library versioning issues II
Date: Wed, 10 Feb 2010 11:28:07 -0800	[thread overview]
Message-ID: <20100210192807.GA31773@pendragon.3leafnetworks.com> (raw)
In-Reply-To: <20100210124512.GI2777@one.firstfloor.org>

On Wed, Feb 10, 2010 at 01:45:12PM +0100, Andi Kleen wrote:
> 
> As a addendum (after looking at the documentation) it seems like
> glibc has already anticipated that problem and 
> your user simply needs to switch to dlvsym() and specify the expected
> version.

Thanks Andi,

   I'll convey this to the vendor.  They may be reluctant to use a
non-posix interface, but c'est la vie.

scott

      reply	other threads:[~2010-02-10 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 21:48 Library versioning issues Scott Lurndal
2010-02-10  7:34 ` Andi Kleen
2010-02-10 12:45   ` Library versioning issues II Andi Kleen
2010-02-10 19:28     ` Scott Lurndal [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=20100210192807.GA31773@pendragon.3leafnetworks.com \
    --to=scott.lurndal@3leafsystems.com \
    --cc=andi@firstfloor.org \
    --cc=linux-numa@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).