DJ Lucas wrote: > Well it looks easy enough to fix. Is it as simple as I think it > is....replacing the fopen to point at the different filename...better if > the open call to exec-shield-randomize fails, then go for > randomize_va_space...assuming the data contained in each is the same. > Or check for the file first, but better is to reverse the > previous...check for RVS first and let RH deal with the second fopen if > it's needed (or they can fix their kernel to match the mainstream).
Yes, everything he said :-) But seriously, seeing as GCC-4.x appears OK, maybe it doesn't matter much that the wrong sysctl name is used. But reading the comments in the patch, it does worry me a bit :-( Feel free to take a stab at enhancing the patch then attach it to 14400 in the GCC bugzilla for review. Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
