On Sat, Dec 01, 2018 at 10:23:11PM +0000, Ken Moffat via blfs-support wrote: > On Sat, Dec 01, 2018 at 08:00:20PM +0000, Ken Moffat via blfs-support wrote: > > Concentrating now on trying to update glibc (one CVE, one "assert > on invocation rather than segfault on exit", one "regression - > slowness in string operations - in certain haswells" which might > affect mine : the change implies new firmware might make the fix > irrelevant, but the problem was seen even in fedora. > > Still testing (only having 4GB for /tmp, and filling that up with > past builds and DESTDIRs, blew out my first attempt), but I've > dusted off my "upgrade glibc" script in the hope this will work. >
Dropped the "assert on invocation" patch - its test fails when applied to 2.28 (specifically, all 5 parts of the test expect a value of -6 but get a value of 6). Passes in glibc-master, so it must depend on something else there. But master is where the pythonization of glibc is taking place, so I'm not looking at previous changes there, I suspect the early stages of using python might break things in LFS. Is grumpiness contagious ? ĸen -- I'm saving up 22 shillings and 10 pence (almost a pound!) per week to buy an ARM-13. http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
