Gilles Espinasse wrote: > ----- Original Message ----- > From: "Bruce Dubbs" <[email protected]> > To: "LFS Developers Mailinglist" <[email protected]> > Sent: Saturday, February 05, 2011 6:02 PM > Subject: LFS SVN-20110204 error report > > >> On my most recent automated build, I have errors in four packages. >> >> gcc: >> libmudflap.c++/pass41-frag.cxx >> libmudflap.c/fail31-frag.c >> libmudflap.c/pass45-frag.c >> libmudflap.c/pass46-frag.c >> >> These types of errors have been around a long time. libmudflab is a >> library to help developers test for things like array out of bounds. I >> have looked at the problematic programs, but cannot tell why they are >> failing. They can be ignored by lfs users. >> > Maybe note in the book that libmudflap is optional and could be disabled at > configure time. > That will cost less time on build and test, and on support as there will be > less errors reported ;-)
Sorry for the null message I just sent... I think we should build a relatively complete system for c,c++. Avoiding an error message by not building a portion of the package is not the way to go. Reporting problems is sufficient. > Mostly similary, is really openmp required for everyone? openmp is "An API for multi-platform shared-memory parallel programming in C/C++ and Fortran." I don't know where this comes into gcc. >> glibc: > > Did you have a random result at during glibc .configure with this test > checking whether ranlib is necessary... I have 'no' and haven't noticed it before. Perhaps it is dependent on the host system. > I have sometime no, sometime yes result with glibc-2.11.3 > That create a bit of noise when creating a diff from log files. > I add libc_cv_ranlib_necessary=no at configure when I want minimal noise in > log. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
