Andy --
Careful about mixing service models. > I just ran ./configure with the options I wanted... This is what I would recommend 99 times out of 100 [jab], but ... > In most cases I have found that works in a sane way, > but perhaps not! What I ended up doing was taking the stock > PHP installation and tweaking it a bit to get what I needed > without recompiling. Obviously you stumbled onto some hidden requirement which only reveals itself at run time. Bummer. (This is worse with C++ based packages.) [jab] > Where is this .spec file that you speak of.... SuSE Linux and RedHat Linux are RPM based systems. Not only is RPM used for package delivery, but also (for better or worse) for actually *building* the packages. The .spec file is contained within the RPM-ified packaging of PHP. You'll need to get the source RPM from the distributor. The .spec file is in there. Now, the .spec file itself will only give you some hints about the hooks into and out of PHP (as packaged by SuSE). If you really want to get it right, you'll need to rebuild with RPM. (Which I forget how to do and have to look up ever time.) IF YOU REALLY want to follow the standard open source recipe, you'll need to be sure that whatever other components interact (especially shared libraries) with this package are prepared to do so. With PHP, for example, I presume you'll want Apache to be able to call it, so you may find that you have to rebuild Apache too. (Or find some other way around whatever the distributor has done.) In the z/VM world, the customers fought really hard (some might say they complained really loudly) so that CP and CMS could be serviced separately. The vendor complied. But in Linux land, the separation between the various RPM-based packages is much less clear than the clean barrier between CP and CMS. So even a willing and listening Linux distributor may have a real challenge meeting our demands. Of course, you ARE doing it "the right way". [jab] There, I think I've offended plenty of parties. :-) -- R; <>< ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
