From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: kdevelop broken (llvm slot issue)
Date: Sun, 19 Aug 2018 18:49:09 +0300 [thread overview]
Message-ID: <plc3dj$cie$1@blaine.gmane.org> (raw)
In-Reply-To: <1789602.QsFXGFdZvD@prometheus>
On 19/08/18 18:21, Alexander Puchmayr wrote:
> After recent upgrades of mesa, llvm, clang etc kdevelop does not work anymore.
> It crashes immediately after start with errors
> [...]
>
> It seems as if multiple slots of llvm cause the problems. mesa pulls in llvm:
> 5, while other programs pull in llvm:6 (via clang:6)
>
> Does anyone have an idea how to get a working kdevelop again?
Have you tried disabling the llvm USE flag of mesa? AFAIK it's only used
for the software rendering backend, which you probably don't need. Try
disabling it, and then do:
emerge -auDN --changed-deps --with-bdeps=y @world
followed by:
emerge -a --depclean
which should unmerge llvm:5.
next prev parent reply other threads:[~2018-08-19 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 15:21 [gentoo-user] kdevelop broken (llvm slot issue) Alexander Puchmayr
2018-08-19 15:49 ` Nikos Chantziaras [this message]
2018-08-19 15:57 ` Andrew Udvare
2018-08-19 16:24 ` Alexander Puchmayr
2018-08-19 15:58 ` Andrew Udvare
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='plc3dj$cie$1@blaine.gmane.org' \
--to=realnc@gmail.com \
--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