"idle-timeout" => 20
)
)
)
You can take a quick peek at http://daleenterprise.com:86/info.php ,
I'll leave it up for a couple of days.
BuildSmart wrote:
This
This is taken care of by "auto" tools.
If you are experiencing build issues of public releases then you're
doing something wrong.
I build PHP for a living in OS X and I've encountered no build issues
what-so-ever related to building with dylib linking but the resulting
binary will (should
x of C and SH syntax isn't good.
Dmitry.
BuildSmart wrote:
Now that what-if's are occurring in the theoretical world of
intelligent INI, what about file testing capabilities so that the
following can be used to preload extensions by existance?
#if -f ${EXTENSIONS_DIR}/gd.so
extensio
Now that what-if's are occurring in the theoretical world of
intelligent INI, what about file testing capabilities so that the
following can be used to preload extensions by existance?
#if -f ${EXTENSIONS_DIR}/gd.so
extension=gd.so
#endif
or some other syntax that allows testing to include a
On Jan 15, 2008, at 02:12:50, Ronald Chmara wrote:
On Jan 13, 2008, at 5:58 PM, Stanislav Malyshev wrote:
Voting to achieve what?
Fair decisions in a simpler, effective and right manner (and not
discutable, ideally).
I do not consider "fairness", whatever that could mean, having
anything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 11, 2007, at 09:58:16, Gregory Beaver wrote:
BuildSmart wrote:
On Sep 11, 2007, at 05:42:50, Marcus Boerger wrote:
Hello Andi,
to end this 'many tools' reasoning. For those issues we already
adopted
zip and if peopl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 16:15:35, Adam Maccabee Trachtenberg wrote:
On Mon, 10 Sep 2007, BuildSmart wrote:
Perhaps the best approach would be to mimic the ext/mysql functions
and feed them to ext/mysqli function rather than aliasing them
directly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 11, 2007, at 05:42:50, Marcus Boerger wrote:
Hello Andi,
to end this 'many tools' reasoning. For those issues we already
adopted
zip and if people insist I wouldn't mind if anybody would provide a
working
tar implementation that allow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 16:15:35, Adam Maccabee Trachtenberg wrote:
On Mon, 10 Sep 2007, BuildSmart wrote:
Perhaps the best approach would be to mimic the ext/mysql functions
and feed them to ext/mysqli function rather than aliasing them
directly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 14:08:43, Hartmut Holzgraefe wrote:
BuildSmart wrote:
Thanks for the response, OK I think I can manage that with ease,
what I'm contemplating to do is create a mysql_alias extension
that aliases the mysql exte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 08:53:29, Marcus Boerger wrote:
Hello BuildSmart,
If you have the correct includes in place, sure.
marcus
Thanks for the response, OK I think I can manage that with ease, what
I'm contemplating to do is cre
On Sep 10, 2007, at 01:31:54, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 01:01:19, Christian Stocker wrote:
On 10.9.2007 6:53 Uhr, BuildSmart wrote:
On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
On 10.9.2007 3:53 Uhr, BuildSmart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 01:01:19, Christian Stocker wrote:
On 10.9.2007 6:53 Uhr, BuildSmart wrote:
On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
On 10.9.2007 3:53 Uhr, BuildSmart wrote:
I was asked to look into the pdoru patch and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
On 10.9.2007 3:53 Uhr, BuildSmart wrote:
I was asked to look into the pdoru patch and extension by a
client, this
is where I noticed that a similar patch is already applied to the
rfc1867
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was asked to look into the pdoru patch and extension by a client,
this is where I noticed that a similar patch is already applied to
the rfc1867.c file (http://cvs.php.net/viewvc.cgi/php-src/main/
rfc1867.c?r1=1.173.2.1&r2=1.173.2.1.2.1&pathrev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've seen several examples of PHP_FALIAS within a single module, I'm
wondering if it's possible to have one module with aliases
referencing functions in another module?
- -- Dale
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (Darwin)
iD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 6, 2007, at 04:24:32, Hartmut Holzgraefe wrote:
BuildSmart wrote:
The only differences I could find was that openssl was enabled in
the working builds but not enabled in the failing build.
[...]
I went a step further and manually added
s usually
embedded or loaded at runtime then perhaps amending the documentation
to include information if mysql is built with SSL support and you
wish to use SSL with mysql then it is recommended that openssl also
be enabled?
What do you think?
-Rasmus
BuildSmart wrote:
I believe i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I believe it's safe to question source code provided with the PHP
source distributions in an attempt to ascertain a possible direction
to take if any might be required.
I've been trying to determine if the mysql module provided with the
PHP so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 5, 2007, at 10:06:45, David Coallier wrote:
On 9/5/07, BuildSmart <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 5, 2007, at 06:00:41, Hartmut Holzgraefe wrote:
Hello Mr B*S*
hmm, not my name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 5, 2007, at 08:06:20, Jani Taskinen wrote:
Sorry for the top posting Derick. :)
Stas, this patch solves the problems with @ and doing
"php_admin_value error_reporting ":
http://pecl.php.net/~jani/patches/zend_alter_ini_entry.patch
Very n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 5, 2007, at 06:00:41, Hartmut Holzgraefe wrote:
Hello Mr B*S*
hmm, not my name or my pseudonym but the remainder of this post
appears to have been written by me, dyslexic are you?
The complaints over the 4 or 5 I have mentioned on t
sion
to avoid retaliations due to bruised egos.
Let it die here.
-Stut
BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2007, at 09:02:23, Hartmut Holzgraefe wrote:
Dear Mr BuildSmart
BuildSmart wrote:
SInce I didn't consider it a bug but rather a minor error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2007, at 09:02:23, Hartmut Holzgraefe wrote:
Dear Mr BuildSmart
BuildSmart wrote:
SInce I didn't consider it a bug but rather a minor error of
importance,
just out of curiosity: how do you define "bug" if not as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to work on resolving as many of the bugs as possible in the
shortest amount of time because there are not enough PHP developers
to go around validating and fixing every reported bug, this means
that the person assigned many of the bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For those interested in the fix.
ext/standard/config.m4:
dnl
dnl round fuzz
dnl
+AC_DEFUN([PHP_CHECK_ROUNDING_WORKS],[
AC_MSG_CHECKING([whether rounding works as expected])
AC_TRY_RUN([
#include
/* keep this out-of-line to prevent use of gc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 3, 2007, at 15:21:26, Hartmut Holzgraefe wrote:
Dear Mr. BuildSmart
I didn't change my autoconf to correct the problem, that is an
assumption on your part,
talking about assumptions: i didn't claim that changing the
autoco
, don't tell me it's because you claim
all other versions are buggy, I find that hard to accept since the
only problem I've ever experienced to date has been with PHP6 and
swapping two lines corrected this.
--Jani
On Mon, 2007-09-03 at 01:55 -0400, BuildSmart wrote:
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There appears to be an issue with the configure script generation
that warrants further examination which might just be related to
Darwin / Mac OSX but unconfirmed at this time.
I have tested this on 3 different machines with the same results an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This reported bug is bogus, the error is caused by faulty binaries
provided by mysql.org/mysql.com.
A lot of people are experiencing this issue and they believe it is a
problem with the PHP source, I have confirmed that the PHP source is
not t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there going to be a pear installation that works with PHP6 in the
near future?
- - -- Dale
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (Darwin)
iD8DBQFG2kso0hzWbkf0eKgRArwhAJ9sQjxbpxzPXbyF3+6vqicsuVJRxQCfRNw8
Wprb8keup4hc94kuLjXrxPc=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 31, 2007, at 17:11:04, Antony Dovgal wrote:
On 31.08.2007 18:26, BuildSmart wrote:
+#if PHP_MAJOR_VERSION > 4
+ if (!php_stream_get_line(stream, ZSTR(buffer), sizeof(buffer) - 1,
&fetch_len)) {
+#else
Are you sure PHP >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 31, 2007, at 14:02:57, Andrey Hristov wrote:
Hi Dale,
BuildSmart wrote:
On Aug 31, 2007, at 09:43:14, Andrey Hristov wrote:
Hi,
BuildSmart wrote:
On Aug 30, 2007, at 03:18:34, Jani Taskinen wrote:
Perhaps you could send the diff to
wrote:
This is not the list your looking for..try the pecl list instead:
http://pecl.php.net/support.php#lists
--Jani
On Fri, 2007-08-31 at 10:26 -0400, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A quick fix to get pop3 working in PHP6, there might be a better way
but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 31, 2007, at 09:43:14, Andrey Hristov wrote:
Hi,
BuildSmart wrote:
On Aug 30, 2007, at 03:18:34, Jani Taskinen wrote:
Perhaps you could send the diff to the list, or better yet, an url
pointing to the place you uploaded the diff. And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A quick fix to get pop3 working in PHP6, there might be a better way
but this solution seemed to work with the least amount of changes,
tested in 4.3.10, 4.4.0, 5.1.6, 5.2.3 and 6.0.0-dev all of which worked.
link:
http://daleenterprise.com/pop3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 30, 2007, at 03:18:34, Jani Taskinen wrote:
Perhaps you could send the diff to the list, or better yet, an url
pointing to the place you uploaded the diff. And note: it should be
unified diff. (diff -u)
--Jani
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yeah, I had just built something else using gcc 2.95 and forgot to
switch back to 4.0, it sailed through giving it a warning and not an
error.
On Aug 30, 2007, at 06:23:23, Antony Dovgal wrote:
On 30.08.2007 14:08, BuildSmart wrote
quot;, I do have /default_charset = "iso-8859-1"/ set but it
doesn't seem to make any difference.
-- BuildSmart
PGP.sig
Description: This is a digitally signed message part
incorporate into
your java server (unless your java server is all script based then it
might take a little more work).
Cheers,
Rob.
- -- BuildSmart
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (Darwin)
iD8DBQFGzxsv0hzWbkf0eKgRAvb6AKCqlvNucj+YQtnEyENYbwkAKMCnTQCbBDSF
CGhKu8kbc2
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
- -- BuildSmart
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (Darwin)
iD8DBQFGzor10hzWbkf0eKgRAmbHAKCIsMaBV/8GglMHlAWEr38y5/riGwCeOz9T
RN7yuf4nNN9sHFbvbBk1k+o=
=g31
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 24, 2007, at 01:08:50, Rasmus Lerdorf wrote:
BuildSmart wrote:
On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote:
BuildSmart wrote:
True but by enabling it (or I thought) I could generate a single
set of
modules that could be used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:53:17, Ilia Alshanetsky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-07, at 9:49 PM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote:
BuildSmart wrote:
True but by enabling it (or I thought) I could generate a single
set of
modules that could be used with apache 1 and apache 2 but it doesn't
seem to matter to the apa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:53:17, Ilia Alshanetsky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-07, at 9:49 PM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote
7;t figured out which is
the case yet and no one seems to be of any help so far).
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
- -- BuildSmart
-BEGIN PGP SIGNATURE--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 17:05:06, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 16:50:02, Johannes Schlüter wrote:
Hi,
On Thu, 2007-08-23 at 16:23 -0400
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 16:50:02, Johannes Schlüter wrote:
Hi,
On Thu, 2007-08-23 at 16:23 -0400, BuildSmart wrote:
[...]
Symbol not found: _compiler_globals
Referenced from: /usr/local/php/lib/php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It appears that several modules/extensions don't work when built as
loadable extensions.
All software was built on Apple servers using the Apple Developer
Environment, I have tried the builds on owned machines running
current OSes with the sam
s='$CC $allow_undefined_flag -o $lib -dynamic -
bundle $libobjs $deplibs$compiler_flags'
All this does is prevent the static modules from being built (no
name.a files, only name.so files).
On 8/16/07, BuildSmart <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wrote an extension/module (quite some time ago) for PHP4, for the
last year or so (on and off) I've been rewriting it for PHP5.
Under PHP4 it works properly as an embedded extension or a loadable
module.
Under PHP5 it only appears to work pr
l/icu/lib -L/
usr/local/icu/lib conftest.c
-lm -lm -licui18n -licuuc -licudata -lm -licuio -lxml2 -lz
- -liconv -lm >&5
configure:28135: $? = 0
configure:28137: ./conftest
dyld: Library not loaded: libicui18n.dylib
Referenced from: /SourceCache/BuildSmart/PHP504/srcroot/
52 matches
Mail list logo
