Configure, Make, and Make Install
 

I'm trying to get DB2 version 8.1 to work with PHP on RH 7.2

I've received instruction to -
- run a configure for PHP (4.0.6)
- make
- make install (under su)

My question

Shouldn't the php.ini file get updated / changed with the proper settings from the above 3 steps?

If it should but it doesn't, can someone explain why?

TIA

-jP

Chances are that the location of
php.ini that Redhat chose for their
installation of php differ from where
the tarball's default install will place
them (same applies for all other files ;}).

Cheers,
Tink

That's what I thought, but when I locate php.ini after the configure, make and make install, there is only one php.ini and the timestamp on it (as well as the contents) are unchanged from prior to make install.

well from my knowledge and installation experience, if there is a existing php.ini. it won't be written over so that you keep your existing settings and configurations; and dont have to change them again. that goes for most configuration files.

So that means that the php.ini may be renamed to php.bak (or something like that) which didn't occur and that a new php.ini created in its place?

Qs - If I try to "update" PHP using a new version, where does it and its configuration go? How do I find out where it goes and how do I tell Linux where it is?

-jP

if you want a new php.ini, just copy and paste and rename 'php.ini-recommended' from the tar file. php.ini should be located in your /etc directory. this is where most configs are located.

Isn't it the responsibility of the configure, make, and make install process to collect the information and produce the php.ini based upon the configure parameters?

Did you run updatedb after the install?
Otherwise a second version WON'T show up.

Cheers,
Tink

Reminder - I'm a newbie.

updatedb - Isn't that for updating the RPM database?

Nothing in any of the references that I have at my disposal indicate needing to run updatedb (and I've looked at only a few). I am not installing from RPMs.

Let's go back to my previous question -

Isn't it the responsibility of the configure, make, and make install process to collect the information and produce the php.ini based upon the configure parameters?

-jP

No - updatedb keeps the database of
files that locate utilizes up to date.

It wouldn't ... but then, it doesn't know
that you rely on locate to find things,
either.

Again: no. It doesn't examine pre-installed versions
usually, and if you don't specify anything different
to ./configure it will use the defaults (which, as I
stated above most likely differ from what RH had
installed).

You're the maintainer of the system, and you're
in charge of keeping the box in tune, and files in
place.

Cheers,
Tink

OK, weekend is over back to this......

So what you are saying is that the flexibility of Linux would make it extremely difficult for a newbie (me) to properly configure the installation of new versions of Apache, PHP and IBM's DB2 UDB and get them to work without some documentation and proper configuration settings from each of the aforementioned software tools on how their software would be configured to work with the other two?

I don't think I'll ever get a prototype the three software tools to work together!!