DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39479>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39479 ------- Additional Comments From [EMAIL PROTECTED] 2006-06-09 13:10 ------- (In reply to comment #13) > Is that patch going in to 1.5.x upstream? Probably not, as it's not a proper fix but just unexposing the segfault; any other random change before 1.5.24 may re-expose it, so there is little point until we know more about what triggers the memory corruption (or are immediately releasing, so that such hacks are somewhat justifiable). I've been seeing similar failures in different circumstances, and collected a list of these mysterious issues, which are hopefully all due to the same bug; see this thread: http://lists.gnu.org/archive/html/autoconf/2006-05/msg00141.html and there is more, possibly helpful information in this thread for at least one of the item in the list: http://lists.gnu.org/archive/html/bug-autoconf/2006-06/msg00013.html I haven't had time to follow all the clues yet, nor look at ksh source. I suppose one proper workaround would be to use bash for configuring apr libtool when bash is available. This can be achieved by CONFIG_SHELL=/bin/bash # or whereever it is export CONFIG_SHELL $CONFIG_SHELL ./configure CONFIG_SHELL=$CONFIG_SHELL (Yes, the redundancy here is intended; kind of a workaround for a current Autoconf limitation plus future proofness.) Cheers, Ralf -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
