GDB a VFS module

[Jelmer Vernooij]

Hi,

This really is the way to do these things. See for examples, the
Makefile rules in Samba, for example for pdb_mysql. -lmysql is only
linked against pdb_mysql.so.

Cheers,

Jelmer

On Wed, Apr 21, 2004 at 07:12:37PM -0700, Jagan wrote about 'Re: GDB a VFS module':
> Jelmer

> * Did the gcc -shared stuff. Didnt help. 
> * If individual modules are responsible for linking
> their own libraries then why does a compile of abc.so
> not complain at all. Also ldd of abc.so  does not
> reveal any unlinked dependencies.
> In other words the question is how can individual
> modules make sure they have no unlinked dependecies on
> a compile from the souce tree.

> Jagan.

> --- Jelmer Vernooij <jelmer at vernstok.nl> wrote:
> > Hi,

> > On Wed, Apr 21, 2004 at 06:32:07PM -0700, Jagan
> > wrote about 'GDB a VFS module':
> > > I was able to gdb  my vfs module in vfstest.
> > However a
> > > peculiar thing happened. I am compiling
> > > The module abc.so with some libraries of my own.
> > On a
> > > make modules from samba/source the make
> > > Went through smoothly but the libraries never got
> > > linked. On a run from vfstest ? function foo in
> > abc.so
> > > makes a 
> > > Call to function ?bar? which was never linked in.
> > I am
> > > wondering how the .so?s for vfs modules don?t
> > track 
> > > Library dependencies. Does it just assume that
> > > everything will be dynamically linked in. 
> > You need to link abc.so against your libraries.

> > e.g. 
> > gcc -shared -o abc.so foo.c bar.c -lmylib

> > > Question 2: How does vfstest have its
> > LD_LIBRARY_PATH
> > > linked in??
> > It's the responsibility of the specific modules to
> > link against the
> > libraries they need.

-- 
Jelmer Vernooij <jelmer at vernstok.nl> - http://jelmer.vernstok.nl/
Todo: 0