RE: New packge: lighttpd-1.3.0
Hi Gerrit, > But why wait for me? Try it yourself? No problem that > cannot be discussed at this list (as long as it is about problems with > building some open sourced code for cygwin). Well, I'll give it a go... I just downloaded the latest cygwin + gnu toolset. The lighttpd package is also installed. I also downloaded and built the fastcgi dev. Kit (http://www.fastcgi.com/dist/fcgi.tar.gz) I then grabbed the latest 4.3.8 php source tarball, un-tarred it and built it as follows: # ./configure --enable-fastcgi --enable-force-cgi-redirect --with-layout=GNU --with-pgsql # make # make install # php -v PHP 4.3.8 (cgi-fcgi) (built: Sep 22 2004 00:46:39) Copyright (c) 1997-2004 The PHP Group Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies Well, that seems to work. I then downloaded and installed spawn-fcgi from the lighttpd project download page and built and installed it. (http://jan.kneschke.de/projects/lighttpd/download/spawn-fcgi-1.2.0.tar.gz) I ran the PHP fastcgi interface like this: # spawn-fcgi.exe -f /usr/local/bin/php -p 1026 -C 5 spawn-fcgi.c.150: child spawned successfully: PID: 5824 I also grabbed the spawn-php.sh example script (http://jan.kneschke.de/projects/lighttpd/download/spawn-php.sh) but this didn't seem to work. I then configured lighttpd to use the fastcgi for php and created sample file info.php in the home directory of the web site containing: When I opened by web browser to localhost I saw the php configuration page. It works! Not sure where to go with this now - I'll try setting up a php application that uses a database or something. Any suggestions? R. -- http://robinbowes.com -- 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/
RE: New packge: lighttpd-1.3.0
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Reini Urban > Sent: 22 September 2004 01:12 > Cc: [EMAIL PROTECTED] > Subject: Re: New packge: lighttpd-1.3.0 > > >>But why wait for me? Try it yourself? No problem that > >>cannot be discussed at this list (as long as it is about > problems with > >>building some open sourced code for cygwin). > > robin schrieb: > > Not sure where to go with this now - I'll try setting up a > php application that > > uses a database or something. > > > > Any suggestions? > > Either make Jan adding php and fastcgi support by himself, > or ITP a lighttpd-php package at apps. I think what is required is a separate php package - making it work with a web server (apache or lighttpd) is just a configuration issue. I imagine most of the problems arise when trying to decide on a standard set of modules to be included with the "standard" php package. Or is it possible to package php modules separately, e.g. the postgres, ssl, imap, etc.? R. -- http://robinbowes.com -- 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/
RE: Request for change to /etc/profile
Hi,
I've got a sort-of-related issue with the location of the home directory.
On my work laptop, my home directory is on a network share (mapped as a H:
drive) and "My Documents" is on their too. This is made available offline using
the ... "Make Available Offline" feature of WinXP.
When I'm connected to the network all is well and cygwin correctly finds my home
directory, However, if I'm not connected to the network, cygwin just starts in
root (/). My home directory is there on the machine, but cygwin doesn't find it.
Is there any chance that this could be fixed?
Thanks,
R.
--
http://robinbowes.com
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: 22 September 2004 08:31
> To: [EMAIL PROTECTED]
> Subject: Re: Request for change to /etc/profile
>
> On 21 Sep, CyberZombie wrote:
> > Or 'mkdir -p "$HOME"'...
>
> No, that would do entirely the wrong thing!
>
> If the place where /home is supposed to be mounted hasn't
> been mounted,
> the last thing you want to do is create an alternate /home.
>
> I can imagine the weird problems and reports ("all my files
> disappeared!"), that doing mkdir -p would cause!
>
> My change means that if you can't make the user directory, you just
> don't try to create the skeleton files in it for them.
>
> > >$ diff /etc/profile /etc/profile.orig
> > >38,39c38
> > >< if [ ! -d "$HOME" ] && mkdir "$HOME"
> > >< then
> > >---
> > >
> > >
> > >>if [ ! -d "$HOME" ]; then
>
> luke
>
>
> --
> 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/
RE: New packge: lighttpd-1.3.0
p> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Gerrit P. Haase > Sent: 22 September 2004 10:31 > To: [EMAIL PROTECTED] > Cc: 'Reini Urban'; [EMAIL PROTECTED] > Subject: Re: New packge: lighttpd-1.3.0 > > Hallo R., > > > I think what is required is a separate php package - making it work > > with a web server (apache or lighttpd) is just a configuration > > issue. > > Yes, but you cannot build PHP with fastcgi and Apache support at the > same time, so there should be several packages, runtime for every > webserver available (currently only lighttpd) plus one common > package (devel stuff). Can you expand a little on that? Do you mean something like: php-common php-cgi php-apache php-devel Etc. ? Can cgi php use the same modules as mod_php? Should we build statically? > > I imagine most of the problems arise when trying to decide on a > > standard set of modules to be included with the "standard" php > > package. Or is it possible to package php modules separately, e.g. > > the postgres, ssl, imap, etc.? > > Just include everything possible seems to be ok;) There should be all > important modules which are really needed, e.g. database modules for > mysql and pgsql, sqlite and others, all graphic stuff possible (GD, > JPEG, PNG, ...), cryptographic stuff like openssl, mhash, ..., > compression, pear, XML/XSLT, pdflib, PSPELL? Well you see, one cannot > say which extension is important and which isn't, just try to use > every available extension seems to be ok IMO. That would be OK if all the extensions are built as modules, but building everything into one php executable would make it pretty big, wouldn't it? R. -- 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/
