Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Alex Waugh
In message <[EMAIL PROTECTED]> Sascha Schumann <[EMAIL PROTECTED]> wrote: > On Thu, 2 Jan 2003, Alex Waugh wrote: > > > In message <[EMAIL PROTECTED]> > > Sascha Schumann <[EMAIL PROTECTED]> wrote: > > > > > > You can; I cross compile it regularly. > > > > > > What is your

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Sascha Schumann
On Thu, 2 Jan 2003, Alex Waugh wrote: > In message <[EMAIL PROTECTED]> > Sascha Schumann <[EMAIL PROTECTED]> wrote: > > > > You can; I cross compile it regularly. > > > > What is your target/host platform then? > > Building on Linux, targetting RISC OS. Are our defaults directly

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Alex Waugh
In message <[EMAIL PROTECTED]> Sascha Schumann <[EMAIL PROTECTED]> wrote: > > You can; I cross compile it regularly. > > What is your target/host platform then? Building on Linux, targetting RISC OS. Alex -- Alex Waugh [EMAIL PROTECTED] RISC OS software from ht

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Alex Waugh
In message <[EMAIL PROTECTED]> Wez Furlong <[EMAIL PROTECTED]> wrote: > 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

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Sascha Schumann
> You can; I cross compile it regularly. What is your target/host platform then? - Sascha -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Alex Waugh
In message <[EMAIL PROTECTED]> Sascha Schumann <[EMAIL PROTECTED]> wrote: > On Thu, 2 Jan 2003, Wez Furlong wrote: > > > But how can you reliably detect a system with a broken libc when > > cross-compiling? > > I don't think that you can successfully cross-compile PHP > anyway,

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Sascha Schumann
On Thu, 2 Jan 2003, Wez Furlong wrote: > But how can you reliably detect a system with a broken libc when > cross-compiling? I don't think that you can successfully cross-compile PHP anyway, so the point is moot anyway. - Sascha -- PHP CVS Mailing List (http://www.php.net/) To unsu

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Wez Furlong
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 Reth

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Derick Rethans
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. "br

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Wez Furlong
Sure, but would should the default option be? 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. I don'

Re: [PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-02 Thread Alex Waugh
In message "Wez Furlong" <[EMAIL PROTECTED]> wrote: > wez Wed Jan 1 04:58:17 2003 EDT > > Modified files: > /php4 acinclude.m4 configure.in > /php4/mainstreams.c > Log: > Workaround for glibc 2.2.9x and la

[PHP-CVS] cvs: php4 / acinclude.m4 configure.in /main streams.c

2003-01-01 Thread Wez Furlong
wez Wed Jan 1 04:58:17 2003 EDT Modified files: /php4 acinclude.m4 configure.in /php4/main streams.c Log: Workaround for glibc 2.2.9x and later "a+" bug that does not seek to EOF for files fopen()ed with that mode. Index: php4/acinclude.