public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] Packaging changes in LLVM 10
Date: Mon, 16 Mar 2020 09:23:49 +0100	[thread overview]
Message-ID: <c5b9a888f28f3a5eb6892a5b89f63fc9e6ee9536.camel@gentoo.org> (raw)

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

Hi,

Since 10.0.0 final is around the corner, I'd like to take a minute to
inform developers of packaging changes in Gentoo that affect its
revdeps.  Following frequently repeated requests from Gentoo developers
and users, LLVM 10 is stopping to use BUILD_SHARED_LIBS=ON, i.e. split
shared libraries.  Instead, we'll be using the 'dylib' model recommended
upstream.

This means that sys-devel/{llvm,clang} no longer install those small
libLLVM*.so and libclang*.so files.  Instead, one big libLLVM-${ver}.so
and libclang-cpp.so.${sover} are installed (yes, I know this historical
inconsistency sucks).  Also note that Clang continues installing
libclang.so which is a *C* (not C++) library.

Most of LLVM revdeps should not have problem with LLVM dylib, as it was
the de-facto standard on other distros.  llvm-config handles it
transparently.  If you're dealing with a custom build system that
doesn't handle it, it's as simple as trying '-lLLVM' first (note that
you will '-L' due to slotting).

Clang revdeps may have trouble with clang-cpp library since it's
a fairly recent addition.  Again, the solution is simple: '-lclang-cpp'
(repeating: do not confuse it with -lclang which is a different library
for historical reasons).

sys-devel/lld does not install any libraries anymore.  If you ever need
them, please ping me and we'll try to come up with something upstream.

dev-util/lldb installs liblldb.so.  However, I'm not familiar with that
library and I don't know if it has any consumers.

If you need any help, please don't hesitate to ping me.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2020-03-16  8:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c5b9a888f28f3a5eb6892a5b89f63fc9e6ee9536.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.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