unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Emmanuel Agullo <emmanuel.agullo@inria.fr>
Cc: 43023@debbugs.gnu.org
Subject: bug#43023: clang++ in a {clang-toolchain + gcc-toolchain} environment
Date: Thu, 22 Oct 2020 10:10:05 +0200	[thread overview]
Message-ID: <87v9f2u1eq.fsf@gnu.org> (raw)
In-Reply-To: <109069324.10892414.1598276637610.JavaMail.zimbra@inria.fr> (Emmanuel Agullo's message of "Mon, 24 Aug 2020 15:43:57 +0200 (CEST)")

Hi Emmanuel,

Emmanuel Agullo <emmanuel.agullo@inria.fr> skribis:

> A typical "hello world" C++ fails in an environment with both
> `gcc-toolchain' and `clang-toolchain', apperently due to the setup of
> the `CPLUS_INCLUDE_PATH' environment variable (used because of the
> `#include <iostream>' instruction), when compiling with `clang++'.

Did you want to have both toolchains in the environment, or was the goal
to use Clang, but GCC just happened to be already there (being the
default toolchain)?

In the latter case, the new ‘--with-c-toolchain’ option may help: it
allows you to select ‘clang-toolchain’ instead of the default GCC tool
chain.  Note “instead of” rather than “in addition to”, which means that
there’s only one tool chain in the environment, so no risk of
interference.

  https://guix.gnu.org/manual/devel/en/html_node/Package-Transformation-Options.html

Now, if you really want the two toolchains in the same environment,
we’ll have to investigate, though I’m not sure it’s even fixable as it
breaks assumptions behind uses of #include_next in libstdc++ and
elsewhere.

Thanks,
Ludo’.




      reply	other threads:[~2020-10-22  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 13:43 bug#43023: clang++ in a {clang-toolchain + gcc-toolchain} environment Emmanuel Agullo
2020-10-22  8:10 ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9f2u1eq.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=43023@debbugs.gnu.org \
    --cc=emmanuel.agullo@inria.fr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).