GNU bug report logs - #43023
clang++ in a {clang-toolchain + gcc-toolchain} environment

Previous Next

Full log

Message #8 received at 43023 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: Emmanuel Agullo <emmanuel.agullo <at> inria.fr>
Cc: 43023 <at> debbugs.gnu.org
Subject: Re: bug#43023: clang++ in a {clang-toolchain + gcc-toolchain}
 environment
Date: Thu, 22 Oct 2020 10:10:05 +0200

Hi Emmanuel,

Emmanuel Agullo <emmanuel.agullo <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.