<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 15, 2016 at 10:14 PM, Bruce Dubbs <span dir="ltr"><<a href="mailto:bruce.dubbs@gmail.com" target="_blank">bruce.dubbs@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Bruce Dubbs wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thierry Nuttens wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Check for /tools/include/c++/6.2*/algori<wbr>thm  It should have been<br>
installed<br>
in pass1.<br>
</blockquote></blockquote>
<br>
It seems to be installed by libstdc++ as it's a c++ lib.<br>
<a href="http://downloads.nutyx.org/logs/development/x86_64/chroot/libstdc++.log" rel="noreferrer" target="_blank">http://downloads.nutyx.org/log<wbr>s/development/x86_64/chroot/<wbr>libstdc++.log</a><br>
and passing<br>
--with-gxx-include-dir=/tools/<wbr>$LFS_TARGET/include/c++/$versi<wbr>on<br>
to gcc_pass2 didn't help. Do you see anything in gcc_pass1 that<br>
algorithm header file is install ?<br>
</blockquote>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Any way I will check again on gcc 6.1 when this file is installed. I<br>
will findout I hope<br>
</blockquote>
<br>
<br>
It's not clear whether the file is not installed or just not found.  If<br>
not<br>
found try setting C_INCLUDE_PATH and/or CPLUS_INCLUDE_PATH.<br>
<br>
<br>
   -- Bruce<br>
<br>
</blockquote>
I guess I'im reach the limits of my knowledge in this.<br>
<br>
In gcc_pass2:<br>
I tried passing CPLUS_INCLUDE_PATH=/tools/x86_<wbr>64-lfs-linux-gnu/include<br>
to the ./configure<br>
<br>
same error<br>
<br>
I tried rsync -a /tools/x86_64-lfs-linux-gnu/in<wbr>clude/c++/<br>
/tools/include/c++/<br>
<br>
same error<br>
</blockquote>
<br>
I built gcc-6.2.0-RC-20160815 using the blfs instructions and it completed<br>
OK but took 98 minutes (only c, c++).  Starting the test now.<br>
</blockquote>
<br>
The tests took 128 minutes (about 74 SBU, 130 SBU total).  The gcc tests had the following files fail with various build combinations.<br>
<br>
gcc.dg/guality/pr41616-1.c<br>
gcc.dg/guality/pr45882.c<br>
gcc.dg/guality/pr54200.c<br>
gcc.dg/guality/pr54519-1.c<br>
gcc.dg/guality/pr54519-2.c<br>
gcc.dg/guality/pr54519-3.c<br>
gcc.dg/guality/pr54519-3.c<br>
gcc.dg/guality/pr54519-4.c<br>
gcc.dg/guality/pr54519-5.c<br>
gcc.dg/guality/pr68860-1.c<br>
gcc.dg/guality/vla-1.c<br>
<br>
Most had the option -flto.<br>
<br>
                === gcc Summary ===<br>
<br>
# of expected passes            121026<br>
# of unexpected failures        52<br>
# of unexpected successes       22<br>
# of expected failures          318<br>
# of unsupported tests          1763<br>
<br>
                === g++ tests ===<br>
<br>
Running target unix<br>
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40<br>
FAIL: g++.dg/guality/pr55665.C   -O3 -g  line 23 p == 40<br>
XPASS: g++.dg/tls/thread_local-order2<wbr>.C  -std=c++11 execution test<br>
XPASS: g++.dg/tls/thread_local-order2<wbr>.C  -std=c++14 execution test<br>
<br>
                === g++ Summary ===<br>
<br>
# of expected passes            105417<br>
# of unexpected failures        2<br>
# of unexpected successes       2<br>
# of expected failures          318<br>
# of unsupported tests          3776<br>
<br>
                === libatomic Summary ===<br>
<br>
# of expected passes            54<br>
<br>
                === libgomp Summary ===<br>
<br>
# of expected passes            1806<br>
# of unsupported tests          155<br>
<br>
                === libitm Summary ===<br>
<br>
# of expected passes            42<br>
# of expected failures          3<br>
# of unsupported tests          1<br>
<br>
<br>
                === libstdc++ Summary ===<br>
<br>
# of expected passes            11246<br>
# of expected failures          66<br>
# of unsupported tests          280<span class=""><font color="#888888"><br>
<br>
</font></span></blockquote><div>This seems to have been seen in the test suite results posted today:<br><br><a href="https://gcc.gnu.org/ml/gcc-testresults/2016-08/msg01633.html">https://gcc.gnu.org/ml/gcc-testresults/2016-08/msg01633.html</a><br><a href="https://gcc.gnu.org/ml/gcc-testresults/2016-08/msg01609.html">https://gcc.gnu.org/ml/gcc-testresults/2016-08/msg01609.html</a><br><a href="https://gcc.gnu.org/ml/gcc-testresults/2016-08/msg01594.html">https://gcc.gnu.org/ml/gcc-testresults/2016-08/msg01594.html</a> <br></div></div><br></div><div class="gmail_extra">Note that i686 seems to be in even worse shape.<br><br></div><div class="gmail_extra">I have been looking for the commit that could've caused these, but I can't seem to find it.<br></div></div>