I doubt that there is a compiler problem on your system. It's not impossible, I've run into a number of them myself. The chances that one of them would cause a popular package like PHP to not build is kind of slight, though.
One thing that both Red Hat and SUSE do, is customize a lot of their package builds. Things like backported patches, distribution-specific changes, etc., etc. I don't know if PHP is one of them for SUSE or not, but it could be. The safest thing to do is install the binary RPM whenever you can. If you can't do that for some reason, then try to get your hands on the source RPM, and rebuild the binary from that. The source RPM will have all the platform-specific things built into it that I mentioned above. At a minimum, the .spec file for the package will tell you exactly how the distribution provider created the package in the first place. I myself have had to build some older packages with down-level compilers (gcc 2.95.x versus the current 3.x), so you may have run into something similar. Again, I doubt it in this particular case, but you never know. The .spec file will make that clear, though. If the individual instance system administrators are allowed by your shop to add and remove packages, then bug your system programmers _now_ to make the rest of the installation media available. If that lack is preventing you from doing your job, it is their responsibility to correct the situation. If your shop does _not_ allow you to do that, then I wouldn't try to get around that policy without getting permission for what you're doing, first. Either way, you're going to have to communicate with the other people/groups to make things work they way they ought to work. I would guess that the VM folks at your shop are very interested in helping making sure Linux/390 is a success. I don't think they're going to view things like this as being a "bother." Mark Post -----Original Message----- From: Benjamin White [mailto:[EMAIL PROTECTED] Sent: Saturday, December 27, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Source PHP4 Suse Linux Sorry, I forgot to answer your second question I tried to compile form source, because a was just an administrator of one Linux image and not the whole VM/Linux system. I did not have the install RPMs and wanted to try this first without bothering the sysprogs for this. It was over the holidays also. It sounds like I may have to do this anyway. I have installed other things from source before. My concern is that there may be special compiler issues? >From: Mark Post <[EMAIL PROTECTED]> >Reply-To: Linux on 390 Port <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: PHP4 Suse Linux >Date: Sat, 27 Dec 2003 00:50:26 -0500 > >Just how did you try to install PHP? Via the binary RPM provided by SUSE? >Or were you trying to compile PHP from source? (It sounds like the latter. >If so, why were you trying to compile from source?) > > >Mark Post > >-----Original Message----- >From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of >Benjamin White >Sent: Friday, December 26, 2003 5:43 PM >To: [EMAIL PROTECTED] >Subject: PHP4 Suse Linux > > >My attempt to install PHP4 in Suse S390 linux had problems. The >configuration log complained about the -R option of he C compiler and many >other errors. Apache ver 1 was installed and working. > >If anyone has had sucsess, what else needs to be done in addition to the >standard PHP4/Linux install procedure? > >_________________________________________________________________ >Working moms: Find helpful tips here on managing kids, home, work and >yourself. http://special.msn.com/msnbc/workingmom.armx _________________________________________________________________ Take advantage of our limited-time introductory offer for dial-up Internet access. http://join.msn.com/?page=dept/dialup
