Randy McMurchy wrote: > Hi all, > > This question mostly directed to DJ, and FYI for everyone else. > > Is http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1090 still > a valid bug, or can this one be closed out? >
Dang it! Well now I remember and that was it. The last time this was brought up, the message was thought to be harmless but I bugged it for later. I can't remember the exact details but it still apears to be harmless in context, not to mention the offending code has been there for quite some time. There is no severity listed on the bug however the fix states trivial with a priority of P3. The problem is a real double fclose(). The correct fix is availible here: http://www.openoffice.org/nonav/issues/showattachment.cgi/21660/openoffice.org-1.9.69.doublefree.patch Rebuilding pscpp now... The nptl patch will probably be renamed glibc-2.3.4 and fix added there as it's not nptl specific...rather glibc's handling of the code. The old default was to simply bypass it....it can still be set to bypass instead of patching, but the patch looks correct. Oh yeah...the bug link might be nice... http://www.openoffice.org/issues/show_bug.cgi?id=40937 -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
