so why not patching the configure.in ?

// give the possibility to add other embedded targets and be able to
manage next versions
--with-embedded-target=droid-xxxx
--with-embedded-ldflags= // toolchain ldflags
--with-embedded-cflags= // toolchain cflags
--with-embedded-cppflags= // toolchain cppflags
--with-embedded-tuningflags= // toolchain tuningflags

ecetera

why ?
redefining CC and LDFLAGS CFLAGS (11 years of experience in toolchains
creation, cross compiling... ecetera ) won't work with all
cc/ld/libtool versions and it's often a mess when cross compiling
wrong symbol catched, from a Mac no problem Apple patched gcc/ld and
their libtool to handle that AND IT TOOK A WHILE (4 years) before
beeing stable and non buggy, I am not sure about all platform (read
quite sure)

Best

On Sun, Jan 10, 2010 at 7:50 AM, Moshe Doron <m...@php.net> wrote:
> Antony Dovgal wrote:
>>
>> On 01/10/2010 12:45 AM, Moshe Doron wrote:
>>>
>>> Quit easy porting, here the instructions:
>>>
>>> http://www.icomsw.com/~moshe/php-android.php
>>
>> -CC = gcc
>> +CC = /home/git/arm-2009q3/bin/arm-none-linux-gnueabi-gcc
>> -CPP = gcc -E
>> +CPP = /home/git/arm-2009q3/bin/arm-none-linux-gnueabi-gcc -E
>>
>> Such kind of changes is not necessary, you can do it with `CC=<path to
>> gcc> LD=<path to ld> ./configure ...`
>>
>> If you remove that, there are only two parts that seem to be really
>> ARM-specific:
>> 1) -export-dynamic -> -all-static
>> 2) a patch for zend_float.h
>> Both of them are not clear to me, would you care to explain why are they
>> needed?
>>
>
> Hello,
>
> The static compile is due to the fact that in android there is replacment to
> the standard libc called "bionic". Since and i haven't yet managed to tell
> the CodeSourcery to link against bionic i linked all staticlly.
> bionic is something i need to face for allowing the php to interact with the
> local apache and for allowing the php to be embeded into the android ndk
> framework. I guess there some extra patching will need for it.
>
> Moshe
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to