Carl Bowden wrote:
> > > 1st: mkall could not file the apache or midgard include
> > ->
> > > checked apxs' include path (as surggested on list) and
> > this
> > > is correct -> ok so i include in the mkall HACK_CFLAGS
> > the
> > > -I paths (yes i expect this is a bad idea) and it
> > compiles
> > > (this looks good for all of 2 seconds)
> >
> > $ apxs -q INCLUDEDIR
> >
> > should return the correct include directory. If not, apxs
> > is broken.
>
> it does: /usr/local/apache/include
OK, then I need the verbatim error message generated when you run
mkall. See 'man script'.
> I have been running it as: "./mkall /usr/local/midgard"
That's good.
> > > and php spits out the midgard.so (no mgd_table_exname)
> >
> > If this is still happening, file a bugreport please. It's
> > probably a
> > missing include.
Found the missing include, now in CVS.
> > Nope, the linkage is wrong.
>
> this is still the case:
>
> has any one installed from CVS in the last few days, should
> i go back to the 1.4.1 source?
I always install from CVS. That's not to say you must, perse, but it
must work, in general. The first problem, where mkall will not run
correctly without changing include paths, could well be the cause of
this problem too.
> apache-1.3.20
Same here
> php4.0.6
4.0.5.6rc3. That's what Debian Sid has now, the upgrade has been
broken for a few days, so in a few more I'll probably have 4.0.6.
Shouldn't make any difference, in any case.
> mysql-3.23.39
Same here.
> openssl etc
No openssl here but that shouldn't make a difference.
> none of these complained about incudes (I know this don't
> mean much but I think the envroment (& apxs) is ok)
Looks like it. The script log will tell me more. Ran without unpatched
sources, please.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
