Ethereal-dev: Re: [Ethereal-dev] libethereal linking problem

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

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Sat, 28 May 2005 10:08:19 +0200
On Sat, May 28, 2005 at 10:25:30AM +1000, Michael Cohen wrote:
>    Would it be worth fixing the build problems first, and then tackling
>    problems as they arise. For example you mention that libethereal does
>    not support having multiple instances of everything. Do you mean that
>    libethereal is not multi-threaded? or that all dissection trees share
>    common static memory?

Yes, Ethereal (and especially libethereal) is not threadsave and it will
be lots of work to make it that. We want to get there eventually, but
it may take a long time until we actually do. You are free to speed up
that process of course ;-)

>    I think I have a way to work around the build deficiencies, but it is
>    an ugly hack (tm). I can do an ldd on the ethereal/tethereal binary
>    and just link all those libraries into my binary as well.

The linking process deficiencies derive from restrictions on some platforms
- we changed it to be the way it is today because of these problems
(I don't remember which, maybe windows?). The restriction is: a library
cannot link to other libraries directly.

>    Would it be worth having a look at the libethereal build process to
>    see if I can easily fix this for inclusion into cvs?

If you talk about the linking dependencies problem: Probably not -
unless I am wrong, which might also be the case :-)

Btw - what sort of program are you writing? Maybe it can be put
into the Ethereal source tree directly, thus giving you the necessary
dependencies for free.

  Ciao
   Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.