> In my experience when you see  strings of parse errors like this it is
> due to  a missing  header file.   Is there a  warning about  a missing
> header before the errors start?

not really here's a bit more before the errors:

i686-pc-linux-gnu/bin/ -B/opt/i686-pc-linux-gnu/lib/ -isystem 
/opt/i686-pc-linux-gnu/include -isystem /opt/i686-pc-linux-gnu/sys-include" 
"CFLAGS=-O2 -O3 -march=i686 " "CXXFLAGS=-O3 -march=i686  -D_GNU_SOURCE" 
"CFLAGS_FOR_BUILD=-O3 -march=i686" "CFLAGS_FOR_TARGET=-O2 -O3 -march=i686 " 
"INSTALL=/bin/install -c" "INSTALL_DATA=/bin/install -c -m 644" 
"INSTALL_PROGRAM=/bin/install -c" "INSTALL_SCRIPT=/bin/install -c" "LDFLAGS=" 
"LIBCFLAGS=-O2 -O3 -march=i686 " "LIBCFLAGS_FOR_TARGET=-O2 -O3 -march=i686 " 
"MAKE=make" "MAKEINFO=/home/gcc-4.2.1/missing makeinfo --split-size=5000000 
--split-size=5000000 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" 
"RUNTESTFLAGS=" "exec_prefix=/opt" "infodir=/opt/info" "libdir=/opt/lib" 
"includedir=/opt/include" "prefix=/opt" "tooldir=/opt/i686-pc-linux-gnu" 
"gxx_include_dir=/opt/include/c++/4.2.1" "AR=ar" "AS=/home/gcc-build/./gcc/as" 
"LD=/home/gcc-build/./gcc/collect-ld" "RANLIB=ranlib" 
"NM=/home/gcc-build/./gcc/nm" "NM_FOR_BUILD=" "NM_FOR_TARG
 ET=nm" "DESTDIR=" "WERROR=" all-recursive
make[3]: Entering directory `/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
Making all in include
make[4]: Entering directory 
`/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include'
if [ ! -d "./i686-pc-linux-gnu/bits/extc++.h.gch" ]; then \
  mkdir -p ./i686-pc-linux-gnu/bits/extc++.h.gch; \
fi; \
home/gcc-build/./gcc/xgcc -shared-libgcc -B/home/gcc-build/./gcc -nostdinc++ 
-L/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src 
-L/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src/.libs 
-B/opt/i686-pc-linux-gnu/bin/ -B/opt/i686-pc-linux-gnu/lib/ -isystem 
/opt/i686-pc-linux-gnu/include -isystem /opt/i686-pc-linux-gnu/sys-include 
-Winvalid-pch -Wno-deprecated -x c++-header -O3 -march=i686  -D_GNU_SOURCE 
-I/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu 
-I/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include 
-I/home/gcc-4.2.1/libstdc++-v3/libsupc++ -O2 -g 
/home/gcc-4.2.1/libstdc++-v3/include/precompiled/extc++.h -o 
i686-pc-linux-gnu/bits/extc++.h.gch/O2g.gch
In file included from 
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/bitmap_allocator.h:43,
                 from 
/home/gcc-4.2.1/libstdc++-v3/include/precompiled/extc++.h:38:
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/concurrence.h: In 
constructor '__gnu_cxx::__recursive_mutex::__recursive_mutex()':
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/concurrence.h:169: 
error: expected primary-expression before '.' token
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/concurrence.h:169: 
error: expected primary-expression before '{' token
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/concurrence.h:169: 
error: expected `}' before '{' token
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/concurrence.h:169: 
error: expected ',' or ';' before '{' token
/home/gcc-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/concurrence.h:170: 
error: '__tmp' was not declared in this scope
make[4]: *** [i686-pc-linux-gnu/bits/extc++.h.gch/O2g.gch] Error 1

MAC



-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to