This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Interaction between first stage build with g++ and $PATH
- From: Ian Lance Taylor <iant at google dot com>
- To: Gary Funck <gary at intrepid dot com>
- Cc: Gcc Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 15 Aug 2012 22:26:08 -0700
- Subject: Re: Interaction between first stage build with g++ and $PATH
- References: <20120816051718.GE6869@intrepid.com>
On Wed, Aug 15, 2012 at 10:17 PM, Gary Funck <gary@intrepid.com> wrote:
>
> 1. I have "." on $PATH.
>
> 2. In one build of the latest GCC trunk, I specify
> CC=/usr/bin/gcc and CXX=/usr/bin/g++ and everything
> works.
>
> 3. In another build, I don't specify CC or CXX.
> Therefore they default to 'gcc' and 'g++'.
> This fails:
> g++: error trying to exec 'cc1plus': execvp: No such file or directory
>
> If I remove "." from $PATH then the configuration in 3 will build.
>
> The problem is that there is a g++ executable under the
> built gcc directory, but cc1plus and other g++ component
> parts haven't been built yet.
>
> I can file a bug reported if necessary, but am wondering
> if it is a known requirement not to have "." on $PATH
> or to explicitly set CC and CXX?
it's a bug.
Ian