On Mon, Feb 12, 2001 at 05:02:15PM +0100, David Guerizec wrote:
> Alexander Bokovoy wrote:
>
> > On Mon, Feb 12, 2001 at 02:36:04PM +0000, John P . Looney wrote:
> >
> >> On Mon, Feb 12, 2001 at 01:37:26PM +0100, Emiliano mentioned:
> >>
> >>>> Is it that I'm pulling up two PHP modules ? They certainly aren't there
> >>>> in the httpd.conf - BTW, this is on the machine that's running 1.4.1b1 and
> >>>> PHP4.
> >>>
> >>> You mean 1.4.1/PHP3 or 1.4.1/PHP4?
> >>
> >> 1.4.1/PHP4 - it turns out that it was because there was a mysql.so module
> >> defined in the PHP.ini file - and mysql support was build into either php4
> >> or the midgard.so module.
> >
> > I've already experienced same problem. In my case php4 was without
> > builtin mysql but mysql.so was built as extension and using system's
> > mysqlclient library (as suggested in PHP4's notes to mysql module).
> > Strange enough and workaround for the moment is to disable PHP4's mysql module.
>
> I'm using PHP4 with midgard.so and mysql.so without any problem...
Are you using PHP4 compiled from sources? Actual problem is with distribution-based
RPMs because
in Mandrake, for example, all extensions are compiled with manual options.
--
Sincerely yours, Alexander Bokovoy
The Midgard Project | www.midgard-project.org | Aurora R&D team
Minsk Linux Users Group | www.minsk-lug.net | www.aurora-linux.com
IPLabs Linux Team | linux.iplabs.ru | Architecte Open Source
-- A man's best friend is his dogma.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
