Le 22/02/2020 à 18:33, Tadeus Prastowo via lfs-dev a écrit : > On Sat, Feb 22, 2020 at 6:17 PM Douglas R. Reno via lfs-dev > <[email protected]> wrote: >> >> >> On 2/22/20 11:14 AM, Tadeus Prastowo via lfs-dev wrote: >>> On Fri, Feb 21, 2020 at 9:54 PM Pierre Labastie via lfs-dev >>> <[email protected]> wrote: >>>> Actually, glibc has all the bells and whistles it would have in a native >>>> build. The problem at this stage is libgcc.a, which comes with gcc, not >>>> with >>>> glibc... And this one has no support for threads. >>> For sure, libgcc.a (not glibc) is a better explanation. >>> >>>> OTOH, I've not tried without this option for a while, maybe now it is not >>>> needed anymore. >>> No, it is not needed anymore. But, were it needed before? Any >>> recollection to which GCC version needed it? Thanks. >> >> If we're going off an 'svn blame', it was done at r10226. That would've >> been GCC-4.8.0: >> >> http://wiki.linuxfromscratch.org/lfs/browser/trunk/BOOK/chapter05/libstdc%2B%2B.xml?annotate=blame > > Thank you very much for the pointer. I see that the change was > committed by Pierre.
I'm almost sure the option was needed at the time. gcc-4.8.0 was the first gcc to be written in C++, hence the need for adding C++ support in pass1. > So, by writing "Since we have not yet built the > C threads library", Pierre really means "Since we have not yet built > the [libgcc library with] threads [support]". So, I think the > description really has to be updated so as not to be misleading. > Thanks. > Agreed Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
