On Tue, Mar 09, 2004 at 01:48:10AM -0800, Guy Harris wrote:
> Well, it builds - with some dissector changes that I just checked in,
> making some variables used only in the modules in question static to the
> modules. I do get some warnings:
>
> ld: warning multiple definitions of symbol _locale_charset
> /usr/lib/libiconv.dylib(localcharset.o) definition of _locale_charset
> /usr/local/lib/libintl.dylib(localcharset.o) definition of
> _locale_charset
That looks like a problem in the MacOS X library structure (not that this
would help in case Ethereal wasn't working because of this).
> as well as a lot of
>
> gcc: unrecognized option `-pthreads'
That's quite likely a bug in the package installation of glib2 (or whichever
packet tells us to use -pthreads).
> and some
>
> ld: warning suggest use of -bind_at_load, as lazy binding may
> result in errors or different symbols being used
>
> It also appears to be working, at least when I run it from the build
> directory ("ethereal", in the build directory, is a shell script wrapper
> generated by libtool, which sets the appropriate environment variable to
> get it to find the shared libraries in the build tree).
That's the normal situation when using libtool and shared libs.
> It requires GTK+ 2.x, as GLib 1.2.10 and GTK+ 1.2.10 were built with an
> old version of libtool that doesn't know how to build shared GLib and
> GTK+ libraries.
One more reason to make glib2/gtk2 the default :-)
> It would probably be worth trying it on AIX and Digital UNIX as well,
> just to test two more non-ELF systems and two more systems not using the
> GNU linker. Perhaps Albert Chin of The Written Word would be willing to
> do that.
OK, I'll wait a bit and see whether he has something to say.
Ciao
Jï¿œrg
--
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.
