Re: [PHP-DOC] PHP Doc ./configure
> As expected. > > In my Cygwin installation I tried ... > > cd /cygdrive/c > cd Program\ Files/Zend > > And this worked ... > > /cygdrive/c/Program Files/Zend > > If all the paths in the .in (or the environment variables which contain > paths/files/etc) are passed through sed, then this should be OK? > > The further issue is what happens to filenames with spaces in. I don't > think these are used. I don't think we use filenames with spaces (intentionally :). But there would not be any difference in escaping it, so if you have an escaping routine as a simple sed command or whatever, we can apply it where needed. Goba
RE: [PHP-DOC] PHP Doc ./configure
CLI based code has space separator. Always has done. Probably always will. On windows long file names with spaces are enclosed in double quotes. In fact if you want to pass a string with spaces as a parameter to any program, putting it inside "double quotes" will work. In cygwin, I have to escape the space to use it. Both mechanisms are valid, but obviously incompatible. E.g. On Windows C: CD "\Program Files\Zend" Will take me to ... C:\Program Files\Zend As expected. In my Cygwin installation I tried ... cd /cygdrive/c cd Program\ Files/Zend And this worked ... /cygdrive/c/Program Files/Zend If all the paths in the .in (or the environment variables which contain paths/files/etc) are passed through sed, then this should be OK? The further issue is what happens to filenames with spaces in. I don't think these are used. -Original Message- From: gerzson [mailto:[EMAIL PROTECTED] Sent: 18 November 2005 08:50 To: Gabor Hojtsy Cc: [EMAIL PROTECTED]; PHP Docs List Subject: Re: [PHP-DOC] PHP Doc ./configure > 1. It is really a bad idea to put command line programs into a folder > with space in the name (or any special character for that matter) BTW, IMHO it's a "really bad idea" in 2005 not to let the user choose where to install his own programs. I repeat "In 2005..." -- Papp, Gyozo
Re: [PHP-DOC] PHP Doc ./configure
> At first sight, this may be nothing(?) to with Cygwin nor PHP scripts > but with autoconf which does not enclose filename arguments for 'test' > into quotes: Stupid me! As Nuno wrote the configure.in should be modified. I'll try to see what. (Currently I'm behind a proxy and could not connect to the CVS) -- Papp, Gyozo
Re: [PHP-DOC] PHP Doc ./configure
On 11/18/05, Gabor Hojtsy <[EMAIL PROTECTED]> wrote: > Well, this is an open invitation for telling you that it is open source, > so you can fix. well, already known. :-) > I don't know whether Cygwin has problems still with > spaces in path names, but in that case, first Cygwin needs to be fixed. At first sight, this may be nothing(?) to with Cygwin nor PHP scripts but with autoconf which does not enclose filename arguments for 'test' into quotes: ./configure: line 1403: test: too many argyments ./configure: line 1410: /cygdrive/c/Program: No such file or directory ./configure: line 1412: /cygdrive/c/Program: No such file or directory ./configure: line 1412: test: yes: unary operator expected This may happen merely because those auto* magic stuffs are heavily Unix-based where pathname components rarely contains non-word characters other then . , _-. -- Papp, Gyozo
Re: [PHP-DOC] PHP Doc ./configure
Well, this is an open invitation for telling you that it is open source, so you can fix. I don't know whether Cygwin has problems still with spaces in path names, but in that case, first Cygwin needs to be fixed. If Cygwin has no problems, then only the phpdoc scripts are to blame, and it is an easier fix. Goba gerzson wrote: >>1. It is really a bad idea to put command line programs into a folder >>with space in the name (or any special character for that matter) > > > BTW, IMHO it's a "really bad idea" in 2005 not to let the user choose > where to install his own programs. I repeat "In 2005..." > > -- > Papp, Gyozo >
Re: [PHP-DOC] PHP Doc ./configure
> 1. It is really a bad idea to put command line programs into a folder > with space in the name (or any special character for that matter) BTW, IMHO it's a "really bad idea" in 2005 not to let the user choose where to install his own programs. I repeat "In 2005..." -- Papp, Gyozo
Re: [PHP-DOC] PHP Doc ./configure
> I've come across my first problem with Windows/PHP doc setup and that > is with the ./configure script after checking out a fresh copy from > CVS. My PHP dir is C:\Program Files\PHP which seems to be giving the > configure script problems because of the space. It is getting the path > directly from the system PATH variable. 1. It is really a bad idea to put command line programs into a folder with space in the name (or any special character for that matter) 2. What I used to do is to have C:/WebDev or something where I installed Apache, some SQL server, PHP, etc. Or I added php.bat to the Windows folder (or anywhere on the path), so that it can be found, and run from anywhere with "php ...". This also helps with the space in the path problem, since the batch file handles the issue. Goba
Re: [PHP-DOC] PHP Doc ./configure
On 17/11/05, Nuno Lopes <[EMAIL PROTECTED]> wrote: > Stupid question: did you run 'autoconf' after this change? whats the value > of `echo $PHP` after the sed command? Ahh no, I didn't. However, I just did that (changed path to prog files again, launched cygwin, cd phpdoc, autoconf, ./configure) and even with that line, I get a similar error: file versions Makefile.in,v 1.170 configure.in,v 1.233 configure options: source directory: . working directory: /home/Administrator/phpdoc checking for php... /cygdrive/c/Program Files/PHP/php Could not open input file: =. ./configure: line 1404: test: too many arguments checking php version... ./configure: line 1411: /cygdrive/c/Program: No such file or directory ./configure: line 1413: /cygdrive/c/Program: No such file or directory ./configure: line 1413: test: yes: unary operator expected configure: error: PHP version 4.0.0 or newer needed -- David Mytton http://www.olate.co.uk
Re: [PHP-DOC] PHP Doc ./configure
> Looking forward to this. I know I got a fair way before, but getting the > updates sent back to the CVS was handled by Nuno for me. Could you not use CVS, or do you not have a CVS account? No, Richard doesn't have an account. He usually sends the mails to me directly. > Can you give some thought the steps of upgrading Cygwin. This is what > broke my last attempt (before the server went pop!). Not bothered since. Hmm. Isn't this a case of just running setup.exe again and checking to see if there are any updated packages? Some time ago, a cygwin update also broke my cvs client, because it wasn't handling the unix new-lines properly. But a re-install did the trick. Usually upgrading is a matter of running setup.exe (more recent setups also check if the setup.exe file is up-to-date). > Do you still need the openjade tools separate from Cygwin? Or do the > jade tools that cygwin supply now work OK? The cygwin tools are already supported. A few months ago we patched our scritps, so that cygwin tools could be used. This is carefully explained (I hope) in the dochowto: http://doc.php.net/php/dochowto/ Nuno
Re: [PHP-DOC] PHP Doc ./configure
I added PHP = `echo $PHP | sed 's/ /\\ /'` to line 68: fi PHP = `echo $PHP | sed 's/ /\\ /'` if test $PHP = "no"; then but it didn't seem to have any effect. Stupid question: did you run 'autoconf' after this change? whats the value of `echo $PHP` after the sed command? Nuno
Re: [PHP-DOC] PHP Doc ./configure
On 17/11/05, Richard A. Quadling <[EMAIL PROTECTED]> wrote: > Just took a look at all the progs install in C:\ Heh, my C:\ is virtually empty :p > Looking forward to this. I know I got a fair way before, but getting the > updates sent back to the CVS was handled by Nuno for me. Could you not use CVS, or do you not have a CVS account? > Can you give some thought the steps of upgrading Cygwin. This is what > broke my last attempt (before the server went pop!). Not bothered since. Hmm. Isn't this a case of just running setup.exe again and checking to see if there are any updated packages? > Do you still need the openjade tools separate from Cygwin? Or do the > jade tools that cygwin supply now work OK? I seem to remember having major problems with this last time - Jade wasn't working properly and I had to do a lot of manual stuff I can't remember! But I've just gone through the setup process on my brand new x64 PC and the jade that comes with Cygwin worked perfectly first time. In fact, everything has worked perfectly first time with the exception of the Program Files path issue. > Or shall I just wait and see what the notes say! I'll send the first copy now in my original message. :) -- David Mytton http://www.olate.co.uk
Re: [PHP-DOC] PHP Doc ./configure
On 17/11/05, Richard A. Quadling <[EMAIL PROTECTED]> wrote: > Which is why PHP is in the root. Probably. > Also, the issues with having PHP not in C:\PHP for newbies and IIS is > going to cause a LOT of issues. Editing the INI file is hard enough for > some. Yes, I agree. Most people will just install it to the root. But I'm not most people :) > Are you ready to give me a trial run? Not yet. I've got the Cygwin setup, checkout and config instructions done. Now I'm doing the basics of editing, checking the syntax and building the manual. -- David Mytton http://www.olate.co.uk
Re: [PHP-DOC] PHP Doc ./configure
I added PHP = `echo $PHP | sed 's/ /\\ /'` to line 68: fi ] ) PHP = `echo $PHP | sed 's/ /\\ /'` if test $PHP = "no"; then but it didn't seem to have any effect. I like to have my filesystem organised so I put PHP into Prog Files. The guide I'm writing, however, is not specific on that so it does't matter where you put PHP. But I think I'll create a separate copy in C:\PHP so as to avoid this problem. -- David Mytton http://www.olate.co.uk
RE: [PHP-DOC] PHP Doc ./configure
For the purposes of the documenting the installation process for PHP documentation, I would suggest sticking with the standard paths used by PHP. I've never considered placing PHP in anything other than C:\PHP \ C:\PHP5. The only thing I do differently is move PEAR out of PHP. Richard. -Original Message- From: David Mytton [mailto:[EMAIL PROTECTED] Sent: 16 November 2005 23:12 To: PHP Docs List Subject: [PHP-DOC] PHP Doc ./configure I've come across my first problem with Windows/PHP doc setup and that is with the ./configure script after checking out a fresh copy from CVS. My PHP dir is C:\Program Files\PHP which seems to be giving the configure script problems because of the space. It is getting the path directly from the system PATH variable. This is the output I get: file versions Makefile.in,v 1.170 configure.in,v 1.233 configure options: source directory: . working directory: /home/Administrator/phpdoc checking for php... /cygdrive/c/Program Files/PHP/php checking php version... ./configure: line 1403: test: too many argyments ./configure: line 1410: /cygdrive/c/Program: No such file or directory ./configure: line 1412: /cygdrive/c/Program: No such file or directory ./configure: line 1412: test: yes: unary operator expected configure: error: PHP version 4.0.0 or newer needed -- Regards, David Mytton http://www.olate.co.uk
Re: [PHP-DOC] PHP Doc ./configure
Nobody installs PHP to C:\program files :) But try to quote the PHP path, like (add to line 68 of configure.in): PHP = `echo $PHP | sed 's/ /\\ /'` I'm not an expert in configure/bash scripts, but that should do the trick. Nuno - Original Message - From: "David Mytton" <[EMAIL PROTECTED]> To: "PHP Docs List" Sent: Wednesday, November 16, 2005 11:11 PM Subject: [PHP-DOC] PHP Doc ./configure I've come across my first problem with Windows/PHP doc setup and that is with the ./configure script after checking out a fresh copy from CVS. My PHP dir is C:\Program Files\PHP which seems to be giving the configure script problems because of the space. It is getting the path directly from the system PATH variable. This is the output I get: file versions Makefile.in,v 1.170 configure.in,v 1.233 configure options: source directory: . working directory: /home/Administrator/phpdoc checking for php... /cygdrive/c/Program Files/PHP/php checking php version... ./configure: line 1403: test: too many argyments ./configure: line 1410: /cygdrive/c/Program: No such file or directory ./configure: line 1412: /cygdrive/c/Program: No such file or directory ./configure: line 1412: test: yes: unary operator expected configure: error: PHP version 4.0.0 or newer needed -- Regards, David Mytton http://www.olate.co.uk
[PHP-DOC] PHP Doc ./configure
I've come across my first problem with Windows/PHP doc setup and that is with the ./configure script after checking out a fresh copy from CVS. My PHP dir is C:\Program Files\PHP which seems to be giving the configure script problems because of the space. It is getting the path directly from the system PATH variable. This is the output I get: file versions Makefile.in,v 1.170 configure.in,v 1.233 configure options: source directory: . working directory: /home/Administrator/phpdoc checking for php... /cygdrive/c/Program Files/PHP/php checking php version... ./configure: line 1403: test: too many argyments ./configure: line 1410: /cygdrive/c/Program: No such file or directory ./configure: line 1412: /cygdrive/c/Program: No such file or directory ./configure: line 1412: test: yes: unary operator expected configure: error: PHP version 4.0.0 or newer needed -- Regards, David Mytton http://www.olate.co.uk
