Thommie Rother wrote:
>
> Am Montag, 30. April 2001 16:52 schrieben Sie:
>
> > > > conclusion:
> > > > > recompile apache, php4, mod_midgard and midgard-php4 (no matter
> > > > > the
>
> OK, now I spent some hours with checking the options to get midgard 1.4
> on suse 7.1 running. Unfortunately, I must say that "simple
> recompilation" is NOT the way and NO solution for suse users in the
> long run. Here are my points:
>
> The precompiled rpms for apache include a number of "Suse patches". For
> example, there is one module to enable the included SuseHelp. I would
> first need a complete documentaion for the way they produce their rpms
> in detail. Only then I could recreate the "compiling environment" they
> use, for doing it on my own. I doubt that I can get that.
>
> A compilation of the main apache core elements with DSO enabled and
> then re-entering the precompiled stuff during run-time into the newly
> compiled apache was also NOT successful. During the tries I mangled my
> apache setup completely so I needed to build it up again;-(( Well, I'm
> not a guru in compiling, I do that very very rarely ...
Why you need to recompile Apache itself? Seems I've lost thread
describing your problems, could you repeat that again, if possible?
> Moreover, I doubt that a larger number of Suse users (and even admins!)
> are willing to recompile the whole apache setup due to an "unknown
> incompatibility" between Midgard 1.4 and apache. Moerover, even Suse
> themselves would not include Midgard 1.4 (suse 7.1 has 1.2 included) if
> they can't get it running with their apache ...
They hadn't included 1.4 for another reason: SuSE 7.1 based on the
December's freeze when 1.4 was in beta and 1.2.5 was stable version.
It's policy of distribution to be based on stable versions (and very
respective policy in Suse).
> In the long run, RPMs, DEBs and so on are needed for all
> dists."Recompile apache from the scratch" is only temporarily and
> apparently a solution. Sorry to say, but I think that developers still
> need to find the "real" reason behind the segfault ....
We are looking for this problem. In mean time, we have working RPMS for
Mandrake Russian Edition released at 4th of April. It works with PHP
4.0.5 RC1 and Apache 1.3.19+mod_ssl without problems.
> Meanwhile, I will contact suse directly to grab some info on their rpm
> strategy. I am still open for doing more tests - but please - not those
> that need recompiation of a running system ("never touch ..") ;-)
It would be interesting to get their answer, though Suse's approach to
produce RPMS and rules to name them in distro seems to be greatly
outdated these days.
--
AB
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
