Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 12:56:43 -0400
Message-ID: <2CBCAAE91EB1E4479A35C1750EE44F98570FFD@alfalfa.fortresstech.com>
Thread-Topic: [users@httpd] Cross-compiling Apache 2.2.3 and PHP 5.1.6
Thread-Index: AcbpXcdrOld4Tre2SV6SmKv4XPI7dQACEToA
From: "Lawrence Stefani" <LStefani@fortresstech.com>
To: "Luc I. Suryo" <luc@suryo.com>
Cc: <users@httpd.apache.org>
Subject: RE: [users@httpd] Cross-compiling Apache 2.2.3 and PHP 5.1.6

Hello Luc,

Thanks for the reply.

I visited your site, but it's not clear to me whether you were
cross-compiling for SPARC on your x86 system.  If so, did you use the
standard --host=3D and --target=3D options to point to your =
cross-compiler
when building Apache?  Also, did you configure PHP using both --host=3D
and --with-apxs2=3D options?

The problem I'm seeing is the same ./apache/bin directory that contains
the apxs PERL script also contains the cross-compiled httpd daemon.  In
the above example, the daemon would have been compiled and linked for
SPARC, which (naturally) isn't executable under x86, so PHP configure
fails.

If you were able to build libphp5.so for SPARC on your Solaris x86
system using Apache 2.2.3 apxs, I'd appreciate seeing your ./configure
lines.

Thanks,
Larry

-----Original Message-----
From: Luc I. Suryo [mailto:luc@suryo.com]=20
Sent: Friday, October 06, 2006 11:40 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Cross-compiling Apache 2.2.3 and PHP 5.1.6


i have: Solaris 10 x86...
no issues... and i have the packages available at ftp://ftp.patriots.net

for the Solaris users: I have not tested my SMF (manifest/xml file..)


> Has anyone successfully cross-compiled Apache 2.2.3 and PHP 5.1.6 for=20
> any platform?
> The Apache eXtenSion tool (apxs) as a PERL script is platform=20
> independent, but it relies on executing httpd, which having been=20
> cross-compiled, can't be executed natively.
> The problem first appears when configuring PHP.  When you pass the=20
> --with-apxs2=3D option on the ./configure line, it runs apxs, which=20
> fails to execute httpd.  Since apxs is built dynamically and most=20
> build information is found in the ./build directory, why does it need=20
> to execute httpd?
> How can apxs become truly platform independent, so it can run=20
> successfully in a cross-compiled environment?
> I've also entered this in Bugzilla
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=3D40653) for =
tracking

> purposes.

-ls

---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org