On 02/18/2014 03:25 PM, Arthur Radley wrote:
> Everything went smoothly. I only wanted to mention one new thing that
> happened and one old thing.
>
> The new thing: In section 6.17. GCC-4.8.2 when verifying that the new linker
> is being used with the correct search paths, the result had some extra lines
> for /lib32 which I haven't seen before and which are not in the book's
> example...
>
> bash-4.2# grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
> SEARCH_DIR("/usr/i686-pc-linux-gnu/lib32")
> SEARCH_DIR("/usr/local/lib32")
> SEARCH_DIR("/lib32")
> SEARCH_DIR("/usr/lib32")
> SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
> SEARCH_DIR("/usr/local/lib")
> SEARCH_DIR("/lib")
> SEARCH_DIR("/usr/lib");
>
I suppose it's 32 bit build, no? If so, then it's okay. I doubt any of
the devs did 32 bit build to notice that and no one ever reported it
till now.
> And the old thing: Again this time I had that single unexpected test failure
> for GCC regarding asan_test.C which your test logs don't have. I reported
> that also for LFS v7.4, but I went on to build my usual BLFS system and used
> it since then with no problems. The asan_test.C failure is apparently a
> recent known issue even though the LFS build-logs still don't show it
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55577)...
>
> === g++ Summary ===
>
> # of expected passes 53365
> # of unexpected failures 1
> # of expected failures 290
> # of unsupported tests 647
>
> /sources/gcc-build/gcc/testsuite/g++/../../xg++ version 4.8.2 (GCC)
>
> Anyway, all this is just FYI. Thanks again for all your effort to make this
> terrific OS available to us, the 1% of the 1%.
>
> Arthur
>
Should be fine, 1 unexpected failure shouldn't be a problem.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
