From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Switching C++ Compilers with xbps-alternatives
Date: Tue, 22 Oct 2019 22:54:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15714@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
New issue by schmidh on void-packages repository
https://github.com/void-linux/void-packages/issues/15714
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* c++ --version:
*c++ (GCC) 9.2.0*
*Copyright (C) 2019 Free Software Foundation, Inc.*
*This is free software; see the source for copying conditions. There is NO*
*warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.*
* gcc-9.2.0_1:
*clang-9.0.0_2*
### Expected behavior
I would love to set the default C++ compiler to clang++ using xbps-alternatives.
### Actual behavior
Trying to set alternative C++ compilers is not possible as there is no alternative group for c++.
/usr/bin/c++ is not a link and actually a regular file being part of the gcc package. There is an alternative group for cc. Many build tools like e.g. CMake use cc and c++ to compile source code.
### Steps to reproduce the behavior
next reply other threads:[~2019-10-22 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 20:54 voidlinux-github [this message]
2019-10-22 21:19 ` voidlinux-github
2019-10-22 21:56 ` [ISSUE] [CLOSED] " voidlinux-github
2019-10-22 21:56 ` voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15714@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).