messages crossed - thanks. I was thinking of copying the sqlite, or at
least doing a diff when I saw the same error in both 5.3.14 and 5.4.4

On Thu, Jun 14, 2012 at 6:33 PM, Michael Felt <[email protected]> wrote:

> Well, I am wondering if I posted this wrong - where are all the [PHP-DEV]
> brackets coming from.
>
> But, i believe I found the "syntax" error - by default AIX compiler does
> not support // comments, the CFLAG
> -qlangval=extc99 (or extc89) needs to be added.
>
> Testing further with 5.3.14 and 5.4.4
>
> Michael
>
>
> On Thu, Jun 14, 2012 at 12:58 AM, Michael Felt <[email protected]> wrote:
>
>> Hi.
>>
>> I am trying to compile php against httpd 2.4.2 - but before it gets
>> interesting I think I am having a different problem.
>>
>> The sqlite3 embedded in ./ext/sqlite3 returns a syntax error against
>> vac.C v11 compiler.
>>
>> data/prj/php-5.3.13/ext/sqlite3/sqlite3.c -o ext/sqlite3/sqlite3.lo
>> "/data/prj/php-5.3.13/ext/sqlite3/sqlite3.c", line 893.9: 1506-046 (S)
>> Syntax error.
>> "/data/prj/php-5.3.13/ext/sqlite3/sqlite3.c", line 894.41: 1506-045 (S)
>> Undeclared identifier i.
>> "/data/prj/php-5.3.13/ext/sqlite3/sqlite3.c", line 894.51: 1506-277 (S)
>> Syntax error: possible missing ';' or ','?
>> "/data/prj/php-5.3.13/ext/sqlite3/sqlite3.c", line 894.65: 1506-045 (S)
>> Undeclared identifier or.
>> make: 1254-004 The error code from the last command is 1.
>>
>> Rather than try and solve that I compiled a separate sqlite3 version
>> root@x104:[/]sqlite3 -version
>> 3.6.22
>>
>> However, even after make distclean and a new run of configure with the
>> following arguments - make still continues to try to compile the embedded
>> sqlite3.
>>
>> root@x104:[/data/prj/php-5.3.13]cat php_configure.ksh
>> #!/usr/bin/ksh
>>
>> set -x
>>
>> ./configure \
>>         --prefix=/opt \
>>         --sysconfdir=/etc \
>>         --mandir=/usr/share/man \
>>         --with-libdir=/opt/lib \
>>         --with-sqlite3=/opt \
>>                 > build/aix/configure.out
>>
>>
>>
>> What am I doing wrong? Many thanks!
>>
>> Michael
>>
>>
>

Reply via email to