public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Paul McFerrin <pmcferrin@columbus.rr.com>
To: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>,
	  cygwin@cygwin.com
Subject: Re: building PHP5
Date: Sun, 18 Jan 2009 13:12:00 -0000	[thread overview]
Message-ID: <4972C373.4010509@columbus.rr.com> (raw)
In-Reply-To: <49728016.70509@users.sourceforge.net>

I'm confused what to download.  When I click the link:
  SCM Repositories - cygwin-ports 
<http://sourceforge.net/projects/cygwin-ports>

and following the instructions to build/install:
   ./configure ; make ; make install

All three steps above complete in under 10 seconds.  There is no code 
present to compile.  I seem to be jumping thru many hoops to get a 
*php5*.dll module to install AND what the complete syntax I should use for:
         LoadModule   xxxxxxxx   libexec/xxxxxxx.dll
Everytime I build the PHP5 library always has unresolved symbols and 
thus install a .a library instead of one with DSO support.

I'm at the end of my rope and the rope is not too long!

- Paul

Yaakov (Cygwin/X) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Paul McFerrin wrote:
>   
>> I'm needing an expert on building PHP5 to work on Apache 1.3.22.  What
>> am I doing wrong?
>>
>> I'm having a dickens of a time building PHP5.  Here is my confugure
>> command line:
>>  ./configure --with-apxs=/usr/local/apache/bin/apxs ./configure
>> --with-apxs=/usr/local/apache/bin/apxs --enable-module=so 2>&1 | tee
>> configure.out 2>&1 | tee configure.out
>>
>> I also tried without the "--enable-module=so" and in every case I get
>> the following error message:
>>   libtool: link: warning: undefined symbols not allowed in
>> i686-pc-cygwin shared libraries
>>
>> and I endup without .dll libraries since my Apache(1.3.x) uses DSO support.
>>
>> Can anyone shed some light on this?
>>     
>
> PHP doesn't build OOTB, but there are packages in Cygwin Ports:
>
> http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/lang/php/
> ftp://ftp.cygwinports.org/pub/cygwinports/release/PHP/php/
>
> Be aware that many of the PHP modules require external deps only
> available from Cygwin Ports.
>
>
> Yaakov
> Cygwin Ports
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEAREIAAYFAklygBYACgkQpiWmPGlmQSOOXgCfS2Z9UcVdKst/vNx7WwfgkXds
> /mYAoO3ffKk9CA/CAdg5mIdQo2/n3i9q
> =aQwF
> -----END PGP SIGNATURE-----
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>
>   

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2009-01-18  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 12:36 Paul McFerrin
2009-01-18  2:23 ` Yaakov (Cygwin/X)
2009-01-18 13:12   ` Paul McFerrin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4972C373.4010509@columbus.rr.com \
    --to=pmcferrin@columbus.rr.com \
    --cc=cygwin@cygwin.com \
    --cc=yselkowitz@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).