Build failure - error: bits/c++config.h: No such file or directory

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Build failure - error: bits/c++config.h: No such file or directory

Robert Jones-2
I've built various versions of Gcc many times on different machines, with
no problems. I have a script to record my learnings, so I'm pretty sure
I'm doing what I always do, but this time round I've hit a problem.

This happens building Gcc 8.2 and 6.4, so it's not anything specific to
latest
version(s)

My native C++ compiler reports

g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23.0.1)

Operating system is

Linux [...] 4.1.12-124.19.7.el6uek.x86_64 #2 SMP Sat Sep 29 17:30:15 PDT
2018 x86_64 x86_64 x86_64 GNU/Linux

And the machine is a VM.

My first error are

error: bits/c++config.h: No such file or directory
error: ‘_GLIBCXX_END_NAMESPACE’ does not name a type

Any idea how to fix these?

Kind Regards

Rob.
Reply | Threaded
Open this post in threaded view
|

Re: Build failure - error: bits/c++config.h: No such file or directory

Jonathan Wakely-4
Hi Rob,

On Tue, 30 Oct 2018 at 10:19, Robert Jones wrote:

>
> I've built various versions of Gcc many times on different machines, with
> no problems. I have a script to record my learnings, so I'm pretty sure
> I'm doing what I always do, but this time round I've hit a problem.
>
> This happens building Gcc 8.2 and 6.4, so it's not anything specific to
> latest
> version(s)
>
> My native C++ compiler reports
>
> g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23.0.1)
>
> Operating system is
>
> Linux [...] 4.1.12-124.19.7.el6uek.x86_64 #2 SMP Sat Sep 29 17:30:15 PDT
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> And the machine is a VM.
>
> My first error are
>
> error: bits/c++config.h: No such file or directory

Something went very wrong. There must be an earlier error that says
why it didn't create this file.

Without knowing how you configured it I can't say more.

> error: ‘_GLIBCXX_END_NAMESPACE’ does not name a type

That's just a consequence of <bits/c++config.h> not being found.