php-install Digest 16 Oct 2002 20:38:10 -0000 Issue 1072
Topics (messages 8819 through 8822):
Re: Multibyte ([PHP-INST] Re: "If-Modified-Since"..)
8819 by: Ryo Takagi
error installing PHP 4.2.3
8820 by: Jason
PHP and ODBC
8821 by: fresler.adex-intl.com
Re: Problems with PHP 4.2.3 & IIS 5.1 & WinXP
8822 by: Stuart
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
--- Begin Message ---
> >ply correctly to requests with If-Modified-Since: header other than to
> > modify PHP source code.
>
> Try CVS version.
Thank you. The CVS version seemed to work correctly on this matter.
> Hmm... Let us know the problem so that we can fix problems before
> release.
What I found is as follows. Both 4.3.0-pre1 and today's CVS snapshot
reproduced the same result.
The script:
BEGIN --- test.phtml ---
<?php
header ( "Last-Modified: " . gmdate ( 'D, d M Y H:i:s \G\M\T' ) ) ;
header("content-type: text/html; charset=ISO-2022-JP");
?>
<html><head><title>Test Multibyte</title></head><body>
<?php
function jstringout( $jstr )
{
print ( mb_convert_encoding( $jstr, "ISO-2022-JP" ) ) ;
}
jstringout ( "<h1> ##### </h1>\n" ) ;
?>
</body></html>
END --- test.phtml
If I put Japanese characters in place of "#####", save this script
using EUC-JP encoding, and access this script using Microsoft Internet
Explorer 6, then the characters does not seem to be correctly encoded.
The selection of encoding in the browser did not help.
In 4.2.3, this script posed no problem.
If "#####" is replaced by the single-byte characters (alphabets) there
is no problem.
If the line:
print ( mb_convert_encoding( $jstr, "ISO-2022-JP" ) ) ;
in this script is modified to:
print ( mb_convert_encoding( $jstr, "ISO-2022-JP", "EUC-JP" ) ) ;
then it works again.
Regards
Ryo
--
R Takagi <[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---
I have run the ./configure --with-mysql --with-apxs command and it always
fails at line 2746 with a Lex output fail.
Here is a copy of the log from config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:1565: checking for Cygwin environment
configure:1581: cc -c conftest.c 1>&5
configure: In function `main':
configure:1577: `__CYGWIN32__' undeclared (first use in this function)
configure:1577: (Each undeclared identifier is reported only once
configure:1577: for each function it appears in.)
configure: failed program was:
#line 1570 "configure"
#include "confdefs.h"
int main() {
#ifndef __CYGWIN__
#define __CYGWIN__ __CYGWIN32__
#endif
return __CYGWIN__;
; return 0; }
configure:1598: checking for mingw32 environment
configure:1610: cc -c conftest.c 1>&5
configure: In function `main':
configure:1606: `__MINGW32__' undeclared (first use in this function)
configure:1606: (Each undeclared identifier is reported only once
configure:1606: for each function it appears in.)
configure: failed program was:
#line 1603 "configure"
#include "confdefs.h"
int main() {
return __MINGW32__;
; return 0; }
configure:1680: checking host system type
configure:1712: checking for a BSD compatible install
configure:1765: checking whether build environment is sane
configure:1822: checking whether make sets ${MAKE}
configure:1861: checking for working aclocal
configure:1874: checking for working autoconf
configure:1887: checking for working automake
configure:1900: checking for working autoheader
configure:1913: checking for working makeinfo
configure:1930: checking whether to enable maintainer-specific portions of
Makefiles
configure:2005: checking for gcc
configure:2118: checking whether the C compiler (gcc ) works
configure:2134: gcc -o conftest conftest.c 1>&5
configure:2160: checking whether the C compiler (gcc ) is a cross-compiler
configure:2165: checking whether we are using GNU C
configure:2174: gcc -E conftest.c
configure:2193: checking whether gcc accepts -g
configure:2226: checking whether gcc and cc understand -c and -o together
configure:2241: gcc -c conftest.c -o conftest.o 1>&5
configure:2242: gcc -c conftest.c -o conftest.o 1>&5
configure:2247: cc -c conftest.c 1>&5
configure:2249: cc -c conftest.c -o conftest.o 1>&5
configure:2250: cc -c conftest.c -o conftest.o 1>&5
configure:2277: checking how to run the C preprocessor
configure:2298: gcc -E conftest.c >/dev/null 2>conftest.out
configure:2357: checking for AIX
configure:2384: checking for gcc option to accept ANSI C
configure:2437: gcc -c -g -O2 conftest.c 1>&5
configure:2461: checking whether compiler supports -R
configure:2476: gcc -o conftest -g -O2 conftest.c -R /usr/lib 1>&5
gcc: unrecognized option `-R'
/usr/lib: file not recognized: Is a directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 2469 "configure"
#include "confdefs.h"
int main() {
; return 0; }
configure:2494: checking whether compiler supports -Wl,-rpath,
configure:2509: gcc -o conftest -g -O2 conftest.c -Wl,-rpath,/usr/lib
1>&5
configure:2532: checking for ranlib
configure:2560: checking whether ln -s works
configure:2585: checking for mawk
configure:2619: checking for bison
configure:2653: checking bison version
configure:2663: checking for flex
configure:2697: checking for yywrap in -ll
configure:2716: gcc -o conftest -g -O2 conftest.c -ll 1>&5
/usr/bin/ld: cannot find -ll
collect2: ld returned 1 exit status
configure: failed program was:
#line 2705 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char yywrap();
int main() {
yywrap()
; return 0; }
configure:2740: checking lex output file root
HERE is a copy of the lines around and including 2746 in the config file.
# The minimal lex program is just a single line: %%. But some broken
lexes
# (Solaris, I think it was) want two %% lines, so accommodate them.
echo '%%
%%' | $LEX
if test -f lex.yy.c; then
ac_cv_prog_lex_root=lex.yy
elif test -f lexyy.c; then
ac_cv_prog_lex_root=lexyy
else
{ echo "configure: error: cannot find output from $LEX; giving up" 1>&2;
exit 1; }
fi
fi
THanks
--- End Message ---
--- Begin Message ---
I am having troubles with ODBC. I can get it to compile and function
correctly, except I believe it is not using the drivers I want it to use.
I have install OpenLink's ODBC drivers on my Linux box. Therefore, my
configuration looks like this:
./configure --with-mysql --with-unixODBC=/usr/openlink/lib --with-apxs
Everything works fine and I can make ODBC calls. However, when I try to
connect, I get the following error:
Warning: SQL error: [unixODBC][Driver Manager]Data source name not found,
and no default driver specified, SQL state IM002 in SQLConnect
I have checked my OpenLink ODBC settings, and everything seems to be set up
fine. Is the above error telling me that it is using the wrong driver?
Thanks for any help.
Floyd
--- End Message ---
--- Begin Message ---
On Tuesday, Oct 15, 2002, at 01:08 Europe/London, David Barrett wrote:
> Hehe... I love quick solutions... not...
>
> The problem has got to be with PHP 4.2.3. I have the same using it
> under
> Apache 2.whatever the latest stable release is. And my php.ini is the
> same
> as it is on all my other installations.
>
> Mind you, in my case the problem could be Apache, too... the above
> versions
> appear not to like each other.
>
> Any more ideas? Oh, and can I have a page reference for any "look it
> up in
> manual" comments, please? ;-)
Are you absolutely sure your php.ini file is exactly the same on each
installation? You are aware that the default value for register_globals
changed at version 4.2? If not, read the warning on this page:
http://www.php.net/manual/en/language.variables.predefined.php
If that's not it, have you tried echoing the variable. Have you tried
doing a print_r (www.php.net/print_r) on $_GET and/or $_POST?
--
Stuart
--- End Message ---
