Andy Galewsky wrote:
I just ran ./configure with the options I wanted... 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.
Generally speaking, when you build an application following its
supplier's instructions, you should also follow the suppliers
instructions for reporting and resolving problems.
Somewhere inside the PHP group there are people building it all the
time, and the chances of getting help (albeit with raised eyebrows when
you tell them what the hardware is) are quite good.
If you're trying to do something a little different (say, make a
SLES-compatible rpm), then doing a straight build is a good first step.
If _I_ wanted a later (say) PHP for my system, I would first look at
Fedora (for RHEL), opensuse (SLES), testing/sid (Debian) to see whether
I could find a satisfactory package there. I would expect to have to
rebuild it from the source rpm to ensure it's linked with the libraries
_I_ have.
Failing that. I'd look at the original supplier's website (php.net in
this case) to see what I could find. Sometimes it's only a tarball,
sometimes it's a set if binaries packages and source.
I'd guess that the prospects of finding zedBinaries are not good, but a
source package for another architecture of release should build with
only modest difficulty.
A couple of caveats.
1. I'd want to be satisfied that this is really the right path. The Boss
is paying truckloads of dosh to support this, and it would be a pity to
spoil the support.
2. Once you adopt this path, it's your responsibility to track security
updates and ensure that they're applied in a timely manner.
If this is for testing something, I'd counsel a nice cheap intellish
system outside my domain, at least until whatever it is works on that.
On intellish hardware, one can run Fedora and OpenSUSE and so are likely
to have bleeding-edge stuff supplied ready to go, and update service of
sorts. It's probably reasonable to develop on those, targetting the next
release of your Enterprise Linux.
Where is this .spec file that you speak of....
-Andy
On 2/20/09 1:31 PM, "Mark Post" <[email protected]> wrote:
On 2/20/2009 at 2:25 PM, Andy Galewsky <[email protected]>
wrote:
Fellows -
I am running SUSE as a guest and trying to compile a custom version of PHP5.
It seems to compile without any errors - but when I try to run it I always
get a segmentation fault.
The version that comes from the SUSE repository works fine of course - has
anybody seen this?
Lots of times. The question I have is, did you use the SUSE .spec file as a
starting point for what you did? That means, all the patches, all the compile
time options, etc.
What are you trying to get out of compiling your own?
Mark Post
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
--
Cheers
John
-- spambait
[email protected] [email protected]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
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
