[EMAIL PROTECTED] wrote:


> 
> Hi Daniel,
> 
> On Mon, 23 Jul 2001, danielk wrote:
> > I searched the archives on this which suggested to link midgard.so
> > manualy to different libs. So i did:
> >
> > [root@core midgard-php4-1.4.1-7]# ldd
> > /usr/local/lib/php/extensions/no-debug-non-zts-20001222/midgard.so
> >         libmidgard.so.3 => /usr/local/lib/libmidgard.so.3 (0x40057000)
> >         libexpat.so.0 => /usr/lib/libexpat.so.0 (0x40069000)
> >         libmysqlclient.so.10 =>
> > /usr/local/mysql/lib/mysql/libmysqlclient.so.10 (0x40087000)
> >         libm.so.6 => /lib/i686/libm.so.6 (0x400a2000)
> >         libz.so.1 => /usr/lib/libz.so.1 (0x400c6000)
> >         libcrypt.so.1 => /lib/libcrypt.so.1 (0x400d4000)
> >         libnsl.so.1 => /lib/libnsl.so.1 (0x40102000)
> >         libc.so.6 => /lib/i686/libc.so.6 (0x4011a000)
> >         libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0
> > (0x4024a000)[root@core midgard-php4-1.4.1-7]#
> >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
> 
> This command does not do any linking, it reports what kind of linking is
> allready there.
You're right there, but the first time i ldd-ed this binariy, only libc
and libglib where linked into it.

Cheers

> 
> > I still get the PHP-warning:
> <snip>
> > Maybe I'll try the cvs-version?
> It is very advisable to use cvs or at least a more recent cvs
> snapshot. Current CVS has many fixes to get around the PHP limbo. If you
> don't feel like using cvs, you can get a recent snapshot from
> snaps.midgard-project.org
> 
> --
> 'The joy of my life is in Zion - Lauryn Hill'
> Armand A. Verstappen * <[EMAIL PROTECTED]> *
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to