Ok well I just tried to run the configure command in no particular directory and these are my results. Any ideas?
> .configure --with pfpro=/var/www/html/Verisign/verisign/payflowpro/linuxrh9/perl sh: line 1: .configure: command not found > ./configure --with-pfpro=/var/www/html/Verisign/verisign/payflowpro/linuxrh9/perl sh: line 1: ./configure: No such file or directory The php bin directory is = /usr/bin. What am I missing with the configure command? I tried figuring out commands with cc but I didn't get very far. Thanks again for your help, I think I'm close to getting this resolved. Sarah --- Chris Hewitt <[EMAIL PROTECTED]> wrote: > On Mon, 2004-11-22 at 19:12, Sarah wrote: > > I believe the server is Redhat linux. I'm just > helping > > out with something so I'm new to this particular > > server also. I did which cc and got "/usr/bin/cc". > > This computer has Fedora Core 1 (effectively RedHat > 10). It has cc and > gcc. I've not used cc but I would suggest gcc. As > you probably have both > the configure/make will probably sort out what it > needs. > > > > The server has php4 installed along with mysql and > > several other options. Really the only thing > needed is > > the payflow pro functions. > > Some of the configure options indicate the file > layout so they can be > important. I would recommend noting the configure > line in phpinfo() > anyway, even if you do not use it. The safest way is > to use all the > existing options (changing any paths necessary) and > add the payflow pro > option to it. > > > > Just so I'm clear on what I need to do, does this > > sound right? > > > > 1.) go to usr/bin/cc and type in the configure > command > > from my previous email or is there a way to > reference > > the compiler directory in my configure command? > > Just go to the directory with the PHP source code. > As the "which cc" > gave you an answer it is on your path so it will get > picked up from > whatever directory you are in. > > > > 2.) after that go to the php directory and type in > > make install? BTW I'm not certain what the php > > directory will look like because the best > candidate I > > found was one directory that only a php file with > no > > extension. I also found one where the sessions > were > > kept. Also what's typical php installation > directory? > > PHP definately is working on the server so I know > > that's ok. > > The source code you can put in any convenient > directory. The resulting > binaries are subject to the configure options. There > are three ways of > using PHP and you need to know which you want. Least > likely is the > command line one only (CGI). If using Apache httpd > webserver most likely > is as an Apache module (DSO). The third is to > compile it into Apache > itself, which would mean compiling Apache too. Your > existing PHP > configure line will indicate which. If it has > --with-apxs (or > --with-apxs2) then it is an Apache DSO. The INSTALL > file in the root PHP > source directory gives quite a lot of information. > > The basic stages of most software is: > configure - set up options for compilation. > make - compile, using the configure options. > make install - put the resulting files int the right > place. This stage > you would normally expect to be the root user for. > > > > 3.) Do I need to add anything to the php.ini file > or > > will everything be all set once the configure and > make > > is done? > > Save your existing php.ini file. It is probably in > /etc but again the > configure options may put it elsewhere. I'm not sure > but the make > install may install a new one. You can overwite it > with the old one > afterwards if you want to, or just merge the > contents. I'm not aware of > any change needed for PHP 5 as opposed to 4. You > will need to change > httpd.conf (assuming Apache), the INSTALL file will > say how. > > > > Thanks for your help, > > Sarah > > You are welcome. I should tell you that I have > compiled PHP 5 here but I > do not use it (or payflow pro) but PHP 4.x. Also, > others on this list > including Chuck will have information that I may not > be aware of. YMMV. > > Regards > > Chris > >
