Wireshark · Ethereal-dev: Re: [Ethereal-dev] Compiling ethereal with GTK2 on Cygwin

["Olivier Biot" <ethereal@xxxxxxxxxx>]

Hi Guy,

Thanks to the changes you checked in earlier today/tonight, I was able
again to compile Ethereal on my cygwin platform. There was only one
issue/problem which was related to some library files missing on my PC
or incorrectly being resolved by libtool (libgtk-X11-2.0.a and
libX11.a are not available; however the .dll.a variants are; I got a
linked Ethereal by replacing the -l option with the full .dll.a
path-and-filename).

Now I can go for the native cygwin/Win32 build again :)

Regards,

Olivier

----- Original Message ----- 
From: Olivier Biot

| From: Guy Harris
|
| | On Sun, Mar 21, 2004 at 08:09:42PM +0100, Biot Olivier wrote:
| | > The problem you mention has been introduced while making
| libethereal a
| | > shared library. The Win32 gcc builds of Ethereal apparently have
| more strict
| | > requirements on what can or cannot be in a shared library. For
| example, the
| | > diameter dissector uses error functions which are not part of
the
| | > libethereal API hence linking fails.
| |
| | Yes, but the errors he's getting are for functions that *are* part
| of
| | the libethereal API; is the problem you mention causing other
| errors?
|
| On my cygwin environment, a build would eventually fail. If I use
| the -no-undefined flag for libtool, then I don't get *those*
warnings,
| but eventually compilation of ethereal fails anyhow, again at
linkage
| stage, and because of symbols.