Hi,
Indeed, binaries (including libs) compiled with gcc 3.x aren't
compatible to
binaries compiled with gcc 2.95. The behaviour you discovered cannot be
classified a php bug, it is rather a limitation of the new
compiler version.
I was under the impression that while your
Where can I get the source or binaries for 4.07? I think I've discovered a
bug , but want to make sure with latest build. The bug has to do with Gnu
GCC 3.0.1 libraries. It's incompatible! Trust me it is! And I even tried to
trick PHP by creating a symbolic link referring to the older
Hi,
Where can I get the source or binaries for 4.07? I think I've discovered a
bug , but want to make sure with latest build. The bug has to do with Gnu
GCC 3.0.1 libraries. It's incompatible! Trust me it is! And I
even tried to
trick PHP by creating a symbolic link referring to the older
On Wed, 19 Sep 2001, Andre Christ wrote:
Hi,
Where can I get the source or binaries for 4.07? I think I've discovered a
bug , but want to make sure with latest build. The bug has to do with Gnu
GCC 3.0.1 libraries. It's incompatible! Trust me it is! And I
even tried to
trick PHP by
: [PHP-QA] Re: [PHP-DEV] 4.0.6
On Friday 22 June 2001 19:19, Liz wrote:
Cool, thanks..
I have a question, has the ISAPI version been stabalised
enough that
it wont crash works IIS 5 server?? Last time I put it on
it screwed
it over and my bosses got real mad.. But, I'd rather
I've now packaged up the Windows Installer version for 4.0.6 (including crypt
support) and posted it to
http://www.dialsolutions.com/phil/php/php406-installer.exe
It would be good it a few people could test it before Andi goes public with
the release. It would be particularly useful to me if
Cool, thanks..
I have a question, has the ISAPI version been stabalised enough that it wont
crash works IIS 5 server?? Last time I put it on it screwed it over and my
bosses got real mad.. But, I'd rather have it as ISAPI.. but.. I'll have my
but kicked if I install it and it wipes out my
http://www.php.net/~andi/php-4.0.6.tar.gz
Tomorrow I'll commit it to the phpweb CVS and we'll announce it on Friday.
Please in the meanwhile make sure that no show stoppers have crept in.
Show stoppers == something is completely broken in the core or a terrible
security hole which needs to be
On Wednesday 20 June 2001 17:22, Andi Gutmans wrote:
I suggest in order to get 4.0.6 out of the door I will package it today
(the release), post it to php-devphp-qa and we can announce it on Friday.
Sounds good. For the last release, in order to synchronise the release of the
source and the
http://www.php.net/~andi/php-4.0.6.tar.gz
Tomorrow I'll commit it to the phpweb CVS and we'll announce it on Friday.
Please in the meanwhile make sure that no show stoppers have crept in.
Show stoppers == something is completely broken in the core or a terrible
security hole which needs to
I'd like to see Zeev's fix to #11590 in 4.0.6
The same to #11589 .. in my project it's very important.
Ok, it's just my project :( but when i need to hardode
class names instead of just specifinig parent:: - it make's
things more complex than they should be.
lenar.
I just tested it, and it
I'd like to see this fix tested a bit more before it gets released. I
think that going off with 4.0.6 as it was packaged and starting the 4.0.7
release process soon afterwards makes the most sense.
Zeev
At 15:54 21/6/2001, Rasmus Lerdorf wrote:
http://www.php.net/~andi/php-4.0.6.tar.gz
At 05:54 AM 6/21/2001 -0700, Rasmus Lerdorf wrote:
http://www.php.net/~andi/php-4.0.6.tar.gz
Tomorrow I'll commit it to the phpweb CVS and we'll announce it on Friday.
Please in the meanwhile make sure that no show stoppers have crept in.
Show stoppers == something is completely broken
At 09:03 AM 6/21/2001 +0100, Phil Driscoll wrote:
On Wednesday 20 June 2001 17:22, Andi Gutmans wrote:
I suggest in order to get 4.0.6 out of the door I will package it today
(the release), post it to php-devphp-qa and we can announce it on Friday.
Sounds good. For the last release, in
On Thu, Jun 21, 2001 at 10:04:45AM +0300, Andi Gutmans wrote:
http://www.php.net/~andi/php-4.0.6.tar.gz
Tomorrow I'll commit it to the phpweb CVS and we'll announce it on Friday.
Please in the meanwhile make sure that no show stoppers have crept in.
Show stoppers == something is completely
RC6 just went out, so I guess if it's the last RC, it could be
approx. time() + 604800. right?
At 21:53 19.6. 2001, Andrei Zmievski wrote the following:
--
When are we releasing 4.0.6? I'm asking more as an end user because it
has a
Hopefully ASAP. We should release RC4 unless people find *serious* problems.
Andi
At 02:53 PM 6/19/2001 -0500, Andrei Zmievski wrote:
When are we releasing 4.0.6? I'm asking more as an end user because it
has a few bug fixes that affect our products.
-Andrei
* Power corrupts. Atomic power
uh, disregard that message. that was pure insanity.
[EMAIL PROTECTED]
-
And the eyes of them both were opened and they saw that their files
were world readable and writable, so they chmoded 600 their files.
- Book of Installation chapt 3 sec 7
--
PHP Development Mailing
Andrei Zmievski wrote:
When are we releasing 4.0.6? I'm asking more as an end user because it
has a few bug fixes that affect our products.
As soon as we stop putting in bug fixes to the RCs!
--
Dan Kalowsky Tonight I think I'll walk alone,
Worldgate Communications
Hey,
I suggest in order to get 4.0.6 out of the door I will package it today
(the release), post it to php-devphp-qa and we can announce it on Friday.
Andi
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
When are we releasing 4.0.6? I'm asking more as an end user because it
has a few bug fixes that affect our products.
-Andrei
* Power corrupts. Atomic power corrupts atomically. *
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
it is not that odd because it may have treated it like whitespace - imagine
a long line script. now it may treat it not as whitespace and hence the
problem
there is no big difference between whitespace and newline(s) in php, is it?
Both today (4.0.6-dev) and earlier \r is treated as whitespace.
- Original Message -
From: Boian Bonev [EMAIL PROTECTED]
To: Dave Jones [EMAIL PROTECTED]
Sent: Tuesday, May 08, 2001 6:29 PM
Subject: Re: [PHP-DEV] 4.0.6
hi,
And also line number don't get incremented if there are no line ends, so
all syntax errors are reported as being on line
There is a problem with line numbers if you use \r as line endings. I
will try and fix it before 4.0.6 (although after my last patch functionally
\r's will work which is the most important thing).
Andi
At 08:50 AM 5/8/2001 -0400, Dave Jones wrote:
it is not that odd because it may have
At 06:32 PM 5/8/2001 +0300, Boian Bonev wrote:
- Original Message -
From: Boian Bonev [EMAIL PROTECTED]
To: Dave Jones [EMAIL PROTECTED]
Sent: Tuesday, May 08, 2001 6:29 PM
Subject: Re: [PHP-DEV] 4.0.6
hi,
And also line number don't get incremented if there are no line ends, so
Can you please check the latest CVS and let me know if the line numbers are
OK now? (when using \r as an end of line).
Thanks,
Andi
At 08:55 PM 5/8/2001 +0300, Andi Gutmans wrote:
There is a problem with line numbers if you use \r as line endings. I
will try and fix it before 4.0.6 (although
Note that there was no such problem with PHP 4.0.4pl1 and earlier.
That's very odd, as PHP never considered \r alone to be a linefeed...
it is not that odd because it may have treated it like whitespace - imagine
a long line script. now it may treat it not as whitespace and hence the
problem
At 06:59 AM 5/8/2001 +0300, Boian Bonev wrote:
Note that there was no such problem with PHP 4.0.4pl1 and earlier.
That's very odd, as PHP never considered \r alone to be a linefeed...
it is not that odd because it may have treated it like whitespace - imagine
a long line script. now it may
On Wed, May 02, 2001 at 11:14:38PM +0300, Zeev Suraski wrote:
At 23:06 2/5/2001, Troels Arvin wrote:
Note that there was no such problem with PHP 4.0.4pl1 and earlier.
That's very odd, as PHP never considered \r alone to be a linefeed...
IIRC, Mac's use \r as an end-of-line. They don't
I've already commited a fix to the CVS which allows \r \n and \r\n.
Andi
At 07:42 AM 5/3/2001 -0700, Ron Chmara wrote:
Andi Gutmans wrote:
The problem occurs when a web-developer using a Mac editor edits PHP
code: If he writes PHP code and his editor uses \r as linefeeds in the
PHP code,
Andi Gutmans wrote:
I've already commited a fix to the CVS which allows \r \n and \r\n.
It gets weirder on OS X (yes, I have one OS X box running...). It uses \r\n
*and* \n.
Sorry 'bout that, I'm reading email remotely (I'm in D.C., right across from
the chinese embassy), and I'm running a
Hi,
I think we should make a list of known 4.0.5 bugs which need to be fixed
for 4.0.6 and once we fix them branch 4.0.6. I think there have been enough
changes to warrant a 4.0.6 release soon.
My list of bugs (please add to this):
- COM support is completely broken (bug #10594)
- libtool
On Wed, 02 May 2001 13:52:58 +0200, Andi Gutmans [EMAIL PROTECTED] wrote:
I think we should make a list of known 4.0.5 bugs which need to be
fixed for 4.0.6
I think that bug #10578 is a very serious problem which should be looked
at before thinking about releasing 4.0.6.
By the way:
The
At 09:02 PM 5/2/2001 +0200, Troels Arvin wrote:
On Wed, 02 May 2001 13:52:58 +0200, Andi Gutmans [EMAIL PROTECTED] wrote:
I think we should make a list of known 4.0.5 bugs which need to be
fixed for 4.0.6
I think that bug #10578 is a very serious problem which should be looked
at before
At 10:06 PM 5/2/2001 +0200, Troels Arvin wrote:
On Wed, 02 May 2001 21:58:03 +0200, Andi Gutmans [EMAIL PROTECTED] wrote:
I think that bug #10578 is a very serious problem which should be
looked at before thinking about releasing 4.0.6.
Do you have any idea what it could be? I don't have
At 23:06 2/5/2001, Troels Arvin wrote:
Note that there was no such problem with PHP 4.0.4pl1 and earlier.
That's very odd, as PHP never considered \r alone to be a linefeed...
Zeev
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
The editor only puts \r without \r\n? Wow, I've never seen a system
that does that :) Were all Mac's like that?
I did. Several times. Unfortunately.
Are you sure you weren't using a different editor?
Isn't there a way for you to save as \n or \r\n?
And, though you probably can save with
At 01:45 PM 5/2/2001 -0700, PHP development @echospace wrote:
The editor only puts \r without \r\n? Wow, I've never seen a system
that does that :) Were all Mac's like that?
I did. Several times. Unfortunately.
Are you sure you weren't using a different editor?
Isn't there a way for
-DEV] 4.0.6
At 01:45 PM 5/2/2001 -0700, PHP development @echospace wrote:
The editor only puts \r without \r\n? Wow, I've never seen a system
that does that :) Were all Mac's like that?
I did. Several times. Unfortunately.
Are you sure you weren't using a different editor?
Isn't
On Wed, May 02, 2001 at 10:06:10PM +0200, Troels Arvin wrote:
The problem occurs when a web-developer using a Mac editor edits PHP
code: If he writes PHP code and his editor uses \r as linefeeds in the
PHP code, then the strange phenomenon may arise.
Don't know wether you have already done
Andi,
We have plan to add ext/jstring which is a japanese string extension module
to php-4.0.6.
Is there any problem to add this module on CVS tree now ?
On Sun, 29 Apr 2001 22:35:43 +0200
Andi Gutmans [EMAIL PROTECTED] wrote:
Guys,
I think that despite the release of 4.0.5 tomorrow we
On Mon, 30 Apr 2001 15:37:14 +0300
Andi Gutmans [EMAIL PROTECTED] wrote:
At 09:35 PM 4/30/2001 +0900, Rui Hirokawa wrote:
Andi,
We have plan to add ext/jstring which is a japanese string extension module
to php-4.0.6.
Is there any problem to add this module on CVS tree now ?
No I
RH For example, this module supports encoding conversion
RH functionality between Unicode and some other encodings like
RH ISO-8859-X. Currently, it includes encoding conversion filter
Doesn't this duplicate the GNU recode functionality?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL
At 10:47 PM 4/30/2001 +0900, Rui Hirokawa wrote:
No I don't see a problem with this but please do it quickly. 4.0.6 has
already gone a long way since we started RC'ing 4.0.5 and I would like to
start RC'ing it pretty soon. You should probably also copy
dotnet/EXPERIMENTAL to your
recode is GPL'd IIRC and thus (your mileage may vary) not very
usable, doesn't build on win32 systems, and the author has
no interest in changing that.
At 15:51 30.4. 2001, Stanislav Malyshev wrote the following:
--
RH For example,
On Mon, 30 Apr 2001 16:51:15 +0300 (IDT)
Stanislav Malyshev [EMAIL PROTECTED] wrote:
RH For example, this module supports encoding conversion
RH functionality between Unicode and some other encodings like
RH ISO-8859-X. Currently, it includes encoding conversion filter
Doesn't this
On Mon, 30 Apr 2001, Rui Hirokawa wrote:
On Mon, 30 Apr 2001 16:51:15 +0300 (IDT)
Stanislav Malyshev [EMAIL PROTECTED] wrote:
RH For example, this module supports encoding conversion
RH functionality between Unicode and some other encodings like
RH ISO-8859-X. Currently, it includes
C recode is GPL'd IIRC and thus (your mileage may vary) not very
C usable, doesn't build on win32 systems, and the author has no
recode libs are LGPL, IIRC. As for win32, I don't know (not being user of
such systems) but I guess since its functionality do not include anything
that is
At 10:01 PM 4/29/2001 -0400, Sterling Hughes wrote:
ext/wchar (wide character support?)
ext/mstring (multibyte string functions)
ext/jpstring (japanese string functions)
I'd make mstring - mbstring.
The question is if it's worth splitting this up into more than one
extension. Probably not.
So
[Cynic [EMAIL PROTECTED]]
recode is GPL'd IIRC and thus (your mileage may vary) not very
usable, doesn't build on win32 systems, and the author has
no interest in changing that.
libiconv is pretty good too. I don't know if it builds on Win32
though.
- Stig
--
Stig Sæther Bakken
On 30 Apr 2001, Stig Sæther Bakken wrote:
[Cynic [EMAIL PROTECTED]]
recode is GPL'd IIRC and thus (your mileage may vary) not very
usable, doesn't build on win32 systems, and the author has
no interest in changing that.
libiconv is pretty good too. I don't know if it builds on Win32
I'd make mstring - mbstring.
The question is if it's worth splitting this up into more than one
extension. Probably not.
So we should probably be picking out of wchar, mbstring, jpstring.
Rui, what do you think?
I'm not Rui, but my vote would be for mbstring (or mb_string). If this
handles
On Mon, 30 Apr 2001 17:26:58 +0300
Andi Gutmans [EMAIL PROTECTED] wrote:
At 10:01 PM 4/29/2001 -0400, Sterling Hughes wrote:
ext/wchar (wide character support?)
ext/mstring (multibyte string functions)
ext/jpstring (japanese string functions)
I'd make mstring - mbstring.
The question is
At 12:23 AM 5/1/2001 +0900, Rui Hirokawa wrote:
On Mon, 30 Apr 2001 17:26:58 +0300
Andi Gutmans [EMAIL PROTECTED] wrote:
At 10:01 PM 4/29/2001 -0400, Sterling Hughes wrote:
ext/wchar (wide character support?)
ext/mstring (multibyte string functions)
ext/jpstring (japanese string
Cynic wrote:
recode is GPL'd IIRC and thus (your mileage may vary) not very
usable, doesn't build on win32 systems, and the author has
no interest in changing that.
the recode command is under GPL while the library part is under LGPL
so it's ok as it is license-wise
(even RMS did not take
Andi Gutmans wrote:
Can we make a list of things which still need to make it into 4.0.6
before we branch?
i have started to create ext/saprfc that will interface with the ABAP/4
Remote Function Call mechanism in SAP R/3,
but right now it only has a working configure script and no
On Mon, Apr 30, 2001 at 10:47:21PM +0900, Rui Hirokawa wrote:
On Mon, 30 Apr 2001 15:37:14 +0300
Andi Gutmans [EMAIL PROTECTED] wrote:
At 09:35 PM 4/30/2001 +0900, Rui Hirokawa wrote:
Andi,
We have plan to add ext/jstring which is a japanese string extension module
to
On Mon, 30 Apr 2001 18:27:26 +0300
Andi Gutmans wrote:
At 12:23 AM 5/1/2001 +0900, Rui Hirokawa wrote:
On Mon, 30 Apr 2001 17:26:58 +0300
Andi Gutmans [EMAIL PROTECTED] wrote:
At 10:01 PM 4/29/2001 -0400, Sterling Hughes wrote:
ext/wchar (wide character support?)
ext/mstring
At 05:56 AM 5/1/2001 +0900, [EMAIL PROTECTED] wrote:
On Mon, 30 Apr 2001 18:27:26 +0300
Andi Gutmans wrote:
At 12:23 AM 5/1/2001 +0900, Rui Hirokawa wrote:
On Mon, 30 Apr 2001 17:26:58 +0300
Andi Gutmans [EMAIL PROTECTED] wrote:
At 10:01 PM 4/29/2001 -0400, Sterling Hughes wrote:
I am also one of the authors of ext/iconv module.
iconv module is only for encoding translation but
jstring (renaming to mbstring) is for general multibyte string
handling fucntions.
The encoding translation is one of functionalities of mbstring.
I think rather iconv module should be merged
Guys,
I think that despite the release of 4.0.5 tomorrow we are pretty close to
having an RC1 for 4.0.6. Lots of things have been fixed/added since 4.0.5
(check the NEWS file).
Can we make a list of things which still need to make it into 4.0.6 before
we branch?
Andi
--
PHP Development
On Sun, 29 Apr 2001, Andi Gutmans wrote:
Guys,
I think that despite the release of 4.0.5 tomorrow we are pretty close to
having an RC1 for 4.0.6. Lots of things have been fixed/added since 4.0.5
(check the NEWS file).
Can we make a list of things which still need to make it into 4.0.6
At 10:09 PM 4/29/2001 +0200, [EMAIL PROTECTED] wrote:
On Sun, 29 Apr 2001, Andi Gutmans wrote:
Guys,
I think that despite the release of 4.0.5 tomorrow we are pretty close to
having an RC1 for 4.0.6. Lots of things have been fixed/added since 4.0.5
(check the NEWS file).
Can we make
On Sun, 29 Apr 2001, Andi Gutmans wrote:
Guys,
I think that despite the release of 4.0.5 tomorrow we are pretty close to
having an RC1 for 4.0.6. Lots of things have been fixed/added since 4.0.5
(check the NEWS file).
Can we make a list of things which still need to make it into 4.0.6
At 04:06 AM 4/29/2001 -0400, Sterling Hughes wrote:
On Sun, 29 Apr 2001, Andi Gutmans wrote:
Guys,
I think that despite the release of 4.0.5 tomorrow we are pretty close to
having an RC1 for 4.0.6. Lots of things have been fixed/added since 4.0.5
(check the NEWS file).
Can we make a
Guys,
I think that despite the release of 4.0.5 tomorrow we are pretty close to
having an RC1 for 4.0.6. Lots of things have been fixed/added since 4.0.5
(check the NEWS file).
Can we make a list of things which still need to make it into
4.0.6 before
we branch?
Andi
K I have a list
On Sun, 29 Apr 2001, James Moore wrote:
=== List of bugs ===
List of iteresting bugs so far:
===
Zend Related
6491 (Incorrect setting of PHP_SELF under certain circumstances)
8130 (Shallow Copy
At 11:36 PM 4/29/2001 +0100, James Moore wrote:
snip
K I have a list of bugs that need to be at least reviewed by the appropraite
developers, this list needs to be added to/altered etc can you please send
feedback on which issues should be fixed before 4.0.6, there are some there
that will not be
On 2001-04-18 06:43:33, "Kurth Bemis" [EMAIL PROTECTED] wrote:
configure: warning: If configure fails try --with-xpm-dir=DIR
checking for freetype(2) (needed by gd 2.0+)... no
...
heres my config line
./configure --with-mysql=/usr/local/mysql
--with-apache=/usr/src/apache_1.3.19
69 matches
Mail list logo
