[users@httpd] Apache for embedded arm - seeking advice

[yan seiner <yan@xxxxxxxxxx>]

I am not an apache guru....  I've managed to set up a few websites, 
which so far run and do what they need to do, but I am not very 
knowledgeable about apache as a developer, which is the role I find 
myself in.....

I am working on an embedded arm project.  I've been trying (so far 
unsuccessfully) to build apache from source, using a cross-tool chain...

I really don't care if I use 1.3 or 2.x; I just need something that 
compiles from source so that we can document the build process.

All I really need is PHP+ming support... Nothing else. No virtual 
hosting, nothing fancy.... I just need to serve up a few pages....  I 
would appreciate any suggestions, both for ./confiugure options - what 
can I safely jettison if I don't care about security, will only serve 
static and php pages, and don't ever want apache to write anything to 
disk....

In the build process, I've gotten as far as PTHREADS in the configure 
for 2.2, where ./configure dies with

checking for PTHREAD_PROCESS_SHARED in pthread.h... yes
checking for pthread_mutexattr_setpshared... yes
checking for working PROCESS_SHARED locks... configure: error: cannot 
run test program while cross compiling
See `config.log' for more details.

Unfortunately config.log doesn't give any details.  I can't hit on a 
magic combination of ac_*=yes to get it to go past that step....

1.3 dies during the build because it tries to build some executables, 
and the build script doesn't allow for HOST_CC and BUILD_CC...

Anyone have a hacked 1.3 build script for cross compiling?

I've googled for answers, and while this seems to be an FAQ, there 
appear to be precious few answers.....

Any information or pointers to docs welcome (and if I missed a doc 
somewhere, apologies....)

--Yan

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx