But how can you reliably detect a system with a broken libc when cross-compiling?
I leave this for someone else to decide, although a more-or-less reasonable default is to for "have_broken_glibc_fopen_append=no" and hope that no-one files a problem report :) --Wez On Thu, 2 Jan 2003, Derick Rethans wrote: > On Thu, 2 Jan 2003, Wez Furlong wrote: > > > Defaulting to assuming that the target has a broken libc can cause race > > conditions (as the append operation is no-longer atomic). > > > > Default to assuming a working libc will cause "a+" operations to fail > > when the target actually has a broken libc. > > "broken glibc" << doesn't that imply that this define only need to be > disabled for known broken systems and thus we can make the default not > to define this thing. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
