Ethereal-dev: [Ethereal-dev] how to select plugin directories for building

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Patnaik, Anjela" <APatnaik@xxxxxxxxx>
Date: Wed, 11 Sep 2002 12:36:19 -0400
Hello, 
I was wondering if there is a configure
option to disable building the
mgcp, docsis and gryphon plugin directories??

In my case, I'm interested only in the "giop"
plugins so the others are not necessary.

Also, do i need to do anything else after
configure i.e. in make and make install to disable
them.

Let me know if there is a way to do this.

Thanks,
ap

-----Original Message-----
From: Guy Harris [mailto:gharris@xxxxxxxxx]
Sent: Tuesday, September 10, 2002 3:20 PM
To: Patnaik, Anjela
Cc: Richard Sharpe; ethereal-dev@xxxxxxxxxxxx
Subject: Re: [Ethereal-dev] ethereal error


On Tue, Sep 10, 2002 at 03:11:29PM -0400, Patnaik, Anjela wrote:
> I just checked the plugins directory under
> the lib directory and yes, docsis.so, docsis.a
> and docsis.la show up. Now, the question is
> why does ethereal NOT find it if they are
> there with the other plugins??

Ethereal isn't what's not finding it.

The dynamic linker is what's not finding it.

Now, perhaps the part of the dynamic linker that implements run-time
loading is, on whatever OS you're running this, horribly broken, so that
an attempt to load a module using a pathname for a file that doesn't
exist causes the linker to abort rather than just causing "dlopen()" (or
whatever) to return an error, or perhaps some other plugin was somehow
linked at build time with the DOCSIS plugin and the attempt to load
*that* plugin causes the run-time linker to fail in that fashion.

Or perhaps Ethereal itself was linked at build time with the DOCSIS
plugin.

I don't know which, if any, of those is the case.  Try running "ldd"
with the pathname of your Ethereal executable as an argument; *NONE* of
the output of "ldd" should contain the string "docsis.so".