On 06/17/2018 08:15 AM, Jean-Marc Pigeon wrote:
Hello,
Weird problem within GCC and I don't know if it is "mine", "lfs"
or "upstream".
- the problem:
I am successful to compile cmake.
AND (everything almost equal)
I am not successful to compile cmake:
[snip]
error: 'mutex' in namespace 'std' does not name a type
std::mutex Mutex_;
I have just started a new build. I will check this out early.
[snip]
- Debugging
The default is proved to be coming from
/usr/include/c++/8.1.0
there is files present in gcc second generation (example stdc++.h)
missing from the first.
I'm not 100% clear on what you are doing. The gcc in BLFS is only there
if you are upgrading gcc in an existing system or want to build one of
the components we do not build in LFS (e.g. gfortran). This is
something I rarely do.
Obviously the second generation ./configure
(building gcc again with all chapter 6 components) is
injecting the "malfunction"
both GCC (first and second generation) make -k check report
OK.
Note: TCL, expect and dejagnu should be part of chapter6, as
currently runtest is the one from /tools when testing
(it should use a runtest within "basic system")
Only g++ seems in trouble.
I noticed BLFS-2018-06-15 is still using/compiling GCC-7.3.0
is this by purpose???
No. The editor that usually does that has not been available for a while.
Am I missing something obvious?
Is someone in this list able to duplicate my finding?
Can you summarize what you are doing again. The best I can tell is that
you are doing:
1. LFS
2, Build GCC a 2nd time (using LFS, not BLFS, procedures)
3. Build GCC a 3rd time (using LFS, not BLFS, procedures)
4. Build cmake
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
