directive.
---
Hans Zaunere / President / New York PHP Community
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> Jani is right, this is not a PHP bug. You need to configure your system
> correctly to make sure the libs are checked in the right order for
They are - per the bug report, the ordering is correct:
# ldconfig -p | grep -i xml2
libxml2.so.2 (libc6,x86-64) => /usr/local/lib/libxml2.so.2
libxm
d it was {}. I remember being very, very
> surprised to find [] doing double duty, and glad that {} existed as
> an alternative.
Yup - if anything, let's remove [] as string access - then again, if it
ain't broke, why try to fix it?
---
Hans Zaunere / President / New York PHP
www.nyphp.org / www.nyphp.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> > On Fri, Oct 22, 2004 at 02:36:00PM +0200, Derick Rethans wrote:
> > > AFAIK Joe is going to commit his patch, but we need to "fix" it
for the
> > > PECL extensions too if applicable.
> >
> > I was kind of waiting for Sascha to review it... do you want me to
> > commit it now? PECL extensions
p4 to
libphp4.so and then make install works. For PHP 5, this is of course
libphp5. Any insight into this would be appreciated.
Thanks Joe and everyone - this seems to get things working for both 4
and 5. I'm going to continue testing, and then document all of this for
future generations,
_strerror'
/root/INSTALLED/php5/ext/standard/streamsfuncs.c:70: warning: passing
arg 2 of `add_next_index_zval' makes pointer from integer without a cast
/root/INSTALLED/php5/ext/standard/streamsfuncs.c:71: warning: passing
arg 2 of `add_next_index_zval' makes pointer from integer withou
--enable-sockets \
--without-sqlite \
--enable-sysvmsg \
--enable-sysvsem \
--enable-sysvshm \
--enable-wddx \
--with-xmlrpc \
--with-xsl
Which works great, and looks like it wants to compile; except for the
seemingly unrelated bug in HEAD that I noted in my previous post.
Thanks,
---
Hans Zaunere
President, Founder
New York PHP
http://www.nyphp.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
; configure: error: Unable to find libgd.(a|so) anywhere under /usr
>
> OK, I've just fixed that. Thanks for testing this stuff out!
That did it - HEAD from CVS works great, as does the GD extension now.
Thanks much Joe - this is a critical step in getting PHP to work on
these newer p
from end-developers, and at the
same time generates interest and challenges for those developing PHP and
Apache themselves.
With other new developments like 64bit platforms, simply, "times, they
are a-changing." Does it make sense to change things just for the sake
of keeping up wit
> > That presents somewhat of a chicken-and-egg problem. Production
sites
> > won't be compelled to make a move until PHP recommends it in some
way,
> > or if there is a killer feature that pulls people in, regardless of
the
> > perceived stability.
>
> Right, and they shouldn't. If there is no
order to use the 64bit libs, you need to either use PHP 5.1, or =
symlink all your libs from /usr/lib and /lib to /usr/lib64 and /lib64
Search the archives for the "./configure, PHP, SuSE and the AMD64" =
thread.
---
Hans Zaunere
President, Founder
New York PHP
http://www.nyph
ow changed. Any news or ideas? Many thanks,
---
Hans Zaunere
President, Founder
New York PHP
http://www.nyphp.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
nux ELF.
> linux-gnu*)
>case $host_cpu in
> - alpha* | hppa* | i*86 | mips | mipsel | powerpc* | sparc* | ia64*)
> + alpha* | hppa* | i*86 | mips | mipsel | powerpc* | sparc* | ia64* | s390* |
> x86_64*)
> lt_cv_deplibs_check_method=pass_all ;;
>*)
> # gl
0 2002/10/23 01:39:54)
My system build environment (Fedora Core 2, updated) has the following:
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
autoconf (GNU Autoconf) 2.59
automake (GNU automake) 1.8.3
This had worked a few months ago, when we first started on this stuff.
So it s
Hey guys,
Just a quick reminder; needing a couple of blurbs for the upcoming meetings.
H
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
need to fix before that happens. One of them is the requirement for
> autoconf
> 2.5x..
I'd be +1, as long as we can have a stable compile for x86_64 systems (/lib64
and all that). Currently HEAD still won't compile. It looks like the
--with-libdir option that Joe ad
candidates passed a file format test
*** using a file magic. Last file checked: /lib/libdl-2.3.3.so
These errors occur for every library.
This all worked in December's CVS HEAD right after Joe put the patch in.
---
Hans Zaunere
President, Founder
New York PHP
http://www.nyphp.org
AMP Technology
Supporting Apache, MySQL and PHP
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t any compat libs. It linked
against the 64bit libs without a problem and worked great.
Hopefully it's just a little glitch after you made the patch. Thanks Joe for
taking a look.
---
Hans Zaunere
President, Founder
New York PHP
http://www.nyphp.org
AMP Technology
Supporting Apache, MySQL
s of what doing The Right Thing really is. Are these
potentially bugs and mis-documentations, or simply me missing the
obvious?
Any thoughts appreciated, thanks all,
---
Hans Zaunere
President
New York PHP
http://nyphp.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ot found." 1>&2; }
Thanks James. That's unfortunate about the configure script being
broken. I do remember some issues years ago, but would have thought
they were cleared up already.
Getting around the libjpeg problem is doable, either by your method or
by using a symlink, a
> > The patch shown is what SuSE did for their RPM distribution of PHP.
> >
> > One solution may be with the --with-= directive is to assume
that
> > dir may be an absolute path as well.
> >
> > --with-domxml=/usr/lib64
>
> No, this is too different from what PHP always has been doing... thus
a
>
> > > > The patch shown is what SuSE did for their RPM distribution of
PHP.
> > > >
> > > > One solution may be with the --with-= directive is to
assume that
> > > > dir may be an absolute path as well.
> > > >
> > > > --with-domxml=/usr/lib64
> > >
> > > No, this is too different from what PHP al
cross the office from me. If
there's a problem, I yank the cord and publicly embarrass the person
abusing it :)
---
Hans Zaunere
President, Founder
New York PHP
http://www.nyphp.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> > > > As I mentioned in my original post, --with-module and
> > > > --with-module-dir seem to have some inconsistencies themselves
as
> > > > well. What is the behavior?
> > >
> > > Where are the inconsistencies, can you point those out?
> >
> > Here are some notes additions from my previous p
> > For #2, per Robert Silva's post:
> >
> > "For #2, I believe he is referring to searching LD_LIBRARY_PATH
> > directories for libraries rather than hardcoding /lib everywhere
(which
> > is how its done now)."
>
> Unfortunately it's not that easy from what I remember.
>
> > > with as it is com
Hello,
Please forgive me if this question is redundant, but I've searched high and
low to no avail.
As a PHP extension, I'm writing a ZEND_FUNCTION(myfunc) that needs to accept
two variables from PHP land, fill in two values (longs) and then return TRUE
or FALSE. Briefly:
ZEND_FUNCTION(ncurse
Andi Gutmans wrote:
At 02:23 PM 11/19/2003 -0500, Ilia Alshanetsky wrote:
> IMHO it should be php_check_syntax() and not
> script_check_syntax() to make clear what it actualy
> checks (it won't check the syntax of my shell, awk
> or perl scripts, would it? ;)
Good idea, we already have some fun
27 matches
Mail list logo
