sniper Tue Mar 25 08:43:13 2003 EDT
Modified files:
/php4 configure.in acinclude.m4
Log:
Made "--with-pear" "--disable-all"-aware. Plus some cosmetics fixes.
Index: php4/configure.in
diff -u php4/configure.in:1.432 php4/configure.in:1.433
--- php4/configu
wez Mon Mar 17 08:40:46 2003 EDT
Modified files:
/php4 acinclude.m4 configure.in
/TSRM tsrm_virtual_cwd.c
/php4/main main.c safe_mode.c
Log:
Fix for Bug #21310, based on a patch by [EMAIL PROTECTED]
Index: php4/acinclude.m4
diff -
> See bug #22556 for one problem.
You should reference fixed bugs in the commit message.
In this case, instead of addressing the core issue, you threw
the baby out with the bath water. I'll look into fixing it
later.
- Sascha
--
PHP CVS Mailing List (http://www.php.net
On Mon, 10 Mar 2003, Sascha Schumann wrote:
>On Mon, 10 Mar 2003, Jani Taskinen wrote:
>
>> sniper Mon Mar 10 09:32:48 2003 EDT
>>
>> Modified files:
>> /php4acinclude.m4 configure.in
>> Log:
>> - Always use the shtool mkdir.
>
>This commit is pointless - it does no
On Mon, 10 Mar 2003, Jani Taskinen wrote:
> sniperMon Mar 10 09:32:48 2003 EDT
>
> Modified files:
> /php4 acinclude.m4 configure.in
> Log:
> - Always use the shtool mkdir.
This commit is pointless - it does not address any problems
nor does it add any functi
sniper Mon Mar 10 09:32:48 2003 EDT
Modified files:
/php4 acinclude.m4 configure.in
Log:
- Always use the shtool mkdir.
Index: php4/acinclude.m4
diff -u php4/acinclude.m4:1.229 php4/acinclude.m4:1.230
--- php4/acinclude.m4:1.229 Wed Mar 5 17:00:45
sniper Mon Feb 10 12:09:50 2003 EDT
Modified files:
/php4 acinclude.m4 configure.in ltmain.sh
Log:
- Updated libtool to 1.4.3 which has test for the sed problem..
Index: php4/acinclude.m4
diff -u php4/acinclude.m4:1.225 php4/acinclude.m4:1.226
--- php4
zeevSun Jan 19 16:37:41 2003 EDT
Modified files:
/php4 acinclude.m4 configure.in
Log:
relabel
Index: php4/acinclude.m4
diff -u php4/acinclude.m4:1.224 php4/acinclude.m4:1.225
--- php4/acinclude.m4:1.224 Fri Jan 3 17:05:12 2003
+++ php4/acinclud
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
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
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
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
> 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
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,
iliaa Thu Jan 2 14:20:57 2003 EDT
Modified files:
/php4 configure.in acinclude.m4
Log:
Raise required OpenSSL version to 0.9.6.
Index: php4/configure.in
diff -u php4/configure.in:1.410 php4/configure.in:1.411
--- php4/configure.in:1.410 Wed Jan
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
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
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
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'
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
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.
sas Wed Nov 13 20:09:46 2002 EDT
Added files:
/php4/ext/ircg ircg_dummy.c ircg_thttpd.c
Modified files:
/php4 acinclude.m4 configure.in
/php4/ext/ircg config.m4 ircg.c
/php4/sapi/cli config.m4
Log:
- Remov
On Thu, 24 Oct 2002, Sascha Schumann wrote:
> sas Thu Oct 24 08:21:07 2002 EDT
>
> Modified files:
> /php4 acinclude.m4 configure.in
> /php4/ext/standardconfig.m4 math.c
> Log:
> Make PHP compile out-of-the-box with uClibc
>
>
> PHP_FUNCT
sas Thu Oct 24 08:21:07 2002 EDT
Modified files:
/php4 acinclude.m4 configure.in
/php4/ext/standard config.m4 math.c
Log:
Make PHP compile out-of-the-box with uClibc
Index: php4/acinclude.m4
diff -u php4/acinclude.m4:1.215 php4/acinclude.m4:1.
sniper Sun Oct 20 23:12:27 2002 EDT
Added files:
/php4/sapi/cgi config9.m4
Removed files:
/php4/sapi/cgi config.m4
Modified files:
/php4 acinclude.m4 configure.in
Log:
- Moved CGI specific lines from
On Sun, 20 Oct 2002, Jon Parise wrote:
>On Mon, Oct 21, 2002 at 03:12:27AM -, Jani Taskinen wrote:
>
>> - # Add /usr/xpg4/bin/sed as it is typically found on Solaris
>># along with /bin/sed that truncates output.
>
>Did you originally intend to remove both of these lines?
Yes. :)
On Mon, Oct 21, 2002 at 03:12:27AM -, Jani Taskinen wrote:
> - # Add /usr/xpg4/bin/sed as it is typically found on Solaris
># along with /bin/sed that truncates output.
Did you originally intend to remove both of these lines?
--
Jon Parise ([EMAIL PROTECTED]) :: The PHP Project (http:/
helly Wed Oct 2 08:52:54 2002 EDT
Modified files:
/php4 acinclude.m4 configure.in
Log:
Check for C99 conformance of snprintf.
#This way we force using internal version if a broken library is used.
#E.g. length parameter is broken, return value or def
28 matches
Mail list logo