From: Alexander Puchmayr <alexander.puchmayr@linznet.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] kdevelop broken (llvm slot issue)
Date: Sun, 19 Aug 2018 17:21:16 +0200 [thread overview]
Message-ID: <1789602.QsFXGFdZvD@prometheus> (raw)
Hi there,
After recent upgrades of mesa, llvm, clang etc kdevelop does not work anymore.
It crashes immediately after start with errors
: CommandLine Error: Option 'help-list' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
This issue is covered by bug https://bugs.gentoo.org/651658, which is open
since March 2018 and no progress since also March 2018.
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?
Regards
Alex
next reply other threads:[~2018-08-19 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 15:21 Alexander Puchmayr [this message]
2018-08-19 15:49 ` [gentoo-user] Re: kdevelop broken (llvm slot issue) Nikos Chantziaras
2018-08-19 15:57 ` [gentoo-user] " 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=1789602.QsFXGFdZvD@prometheus \
--to=alexander.puchmayr@linznet.at \
--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