public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] dev-lang/v8 SONAME
Date: Wed, 27 Oct 2010 12:49:28 +0200	[thread overview]
Message-ID: <4CC803B8.5000005@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

There is one issue that keeps dev-lang/v8 in hard mask and prevents its
broader usage (I think www-client/chromium could start using it). I hope
you'll help me find the best solution.

Some context first. Upstream does not promise any binary compatibility
between releases, so each version has a different SONAME, if any.

Currently dev-lang/v8 does not use SONAME (I think that's the default),
because I'm not sure what's the best way to handle it.

When present, the SONAME will look like libv8-1.2.3.so, and the
resulting shared library will be named the same way, i.e. libv8-1.2.3.so.

Without SONAME, it's just libv8.so, so when linking it's sufficient to
pass -lv8 to the linker.

With the SONAME-d library, I guess I'd need to pass -lv8-1.2.3. I was
thinking about making a symlink libv8.so -> libv8-1.2.3.so, but I'm not
sure if that's the right thing to do.

What do you think? Do you need some more details?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2010-10-27 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 10:49 "Paweł Hajdan, Jr." [this message]
2010-10-27 11:05 ` [gentoo-dev] Re: dev-lang/v8 SONAME Diego Elio Pettenò
2010-10-29  9:02   ` "Paweł Hajdan, Jr."
2010-10-29 15:56     ` [gentoo-dev] " Diego Elio Pettenò
2010-10-27 18:59 ` [gentoo-dev] " James Rowe
2010-10-29  9:05   ` "Paweł Hajdan, Jr."
2010-10-29  9:33     ` James Rowe
2010-11-23 15:01       ` "Paweł Hajdan, Jr."

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=4CC803B8.5000005@gentoo.org \
    --to=phajdan.jr@gentoo.org \
    --cc=gentoo-dev@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