OK. I've just about had it with PHP and MySQL.
I was very pleased to find PHP 3 practically all installed after the basic
setup for LinuxPPC. A little bit of tweaking of the Apache conf files, and
basic PHP scripts were running.
MySQL doesn't come with the distro, though, so I downloaded the rpm and
installed it*. And... hmmm, no rpm for PHP with MySQL support
(postgres, though -- gotta check that out), but hey, I'm not afraid of
making it from the source. So I grab the source and proceed to:
./configure --with-mysql --with-pgsql
and it runs through the litany of stuff it checks and then:
checking for MySQL support... no
configure: error: Invalid MySQL directory
- unable to find libmysqlclient.a or
So I need to find these two files, and give configure a path for them.
After some unsuccesful looking around, I finally result to
find / -name "*mysql*" -print
and nothing comes up. These files are nowhere to be found on the filesystem.
So maybe I need to download the source for mysql? Alright, I go and grap
an RPM of the source (why not a tarball? I don't know. I'm still under the
illusion there might be some sort of advantage to rpms at this point). I
have it on my system now, all 4.2MB. But when I try to install this
package, I get:
D: file: mysql-3.22.32.spec action: unknown
D: file: mysql-3.22.32.tar.gz action: unknown
D: file: mysql.gif action: unknown
In short, it doesn't know what to do with these things.
(I'm downloading the tarballed source tonight, but as you can see,
I'm in need of sage advice).
(And please tell me that I don't have to make apache too).
cheer and warm fuzzies,
* (this, by the way, was my first introduction to the fact
that rpm installs everything in /usr/bin. Why is this? I'd really like
to see things like MySQL go in the traditional /usr/local/bin, or
better yet, just be able to tell rpm where to put it).