Re: cvs: php4 / acinclude.m4 configure.in /main streams.c
| From: | Alex Waugh | Date: | Thu, 02 Jan 2003 22:15:49 +0000 |
| Subject: | Re: cvs: php4 / acinclude.m4 configure.in /main streams.c | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-17536@lists.php.net to get a copy of this message | ||
In message <Pine.LNX.4.50.0301022234580.3459-100000@eco.foo>
Sascha Schumann <sascha@schumann.cx> wrote:
> On Thu, 2 Jan 2003, Alex Waugh wrote:
>
> > In message <Pine.LNX.4.50.0301022056250.3459-100000@eco.foo>
> > Sascha Schumann <sascha@schumann.cx> wrote:
> >
> > > > You can; I cross compile it regularly.
> > >
> > > What is your target/host platform then?
> >
> > Building on Linux, targetting RISC OS.
>
> Are our defaults directly applicable to RISC OS? Or how do
> you manage that configure produces an appropiate
> php_config.h for that target?
The vast majority of tests don't require running a test program,
therefore they work equally well whether cross compiling or not. On the
few that do, the default is usually fine. For those that it gets wrong
the easiest way to change them is to put the correct values in
config.cache before running configure. eg. currently I'm doing the
following:
cat > config.cache << EOF
ac_cv_path_PROG_SENDMAIL=\${ac_cv_path_PROG_SENDMAIL=\<PHP\\\$Mail\>}
lt_cv_prog_cc_can_build_shared=\${lt_cv_prog_cc_can_build_shared=no}
lt_cv_prog_cc_pic_works=\${lt_cv_prog_cc_pic_works=no}
EOF
./configure --host=arm-riscos-aof --with-config-file-path=/Choices:
Alex
--
Alex Waugh alex@alexwaugh.com
RISC OS software from http://www.alexwaugh.com/