Wireshark · Ethereal-users: [Ethereal-users] FW: Zillions of undefined references when linking ethereal.exe on cygwin

[Biot Olivier <Olivier.Biot@xxxxxxxxxxx>]

-----Original Message-----
From: Stephen Blackheath [mailto:stephen@xxxxxxxxxxxxxxxxx] 
Sent: donderdag 29 april 2004 11:14
To: Biot Olivier
Subject: Re: Zillions of undefined references when linking ethereal.exe on
cygwin


Olivier,

Thanks.

The "build a native Win32 app with cygwin tools" scenario works beautifully 
for me now.  I have done it with 0.10.2 and now the 0.10.3 version of 
ethereal.

Please find a collection of scripts and patches that do it all for 0.10.3 
attached to this email.  You will need to create a directory called 'zip'
and 
put the files listed in zip.contents into it.  (I don't want to send you a 
huge file.)

To build, just go

  make -f Makefile.cygwin

To run it, go

  . ./env-win32.sh
  ./ethereal

Ignore the "Hunk #1 succeeded at" errors - these are the result of me
removing 
some patches that aren't of interest (i.e. that I am doing for work).

I haven't tried this all the way though after having removed my stuff, but
it 
should work.  If it doesn't, it won't be hard to fix.  If you really can't 
get it working, I'd be glad to more properly test what I have sent you.

I am using:  Windows 2000 with SP3 (I think) and Cygwin - latest Internet 
version as of yesterday.

The "ethereal-0.10.3-a-instead-of-la.patch" file can be replaced with your 
better solution to the .la problem.


Steve

On Thu, 29 Apr 2004 20:12, Biot Olivier wrote:
> Hi Stephen,
>
> The day after I posted the initial mail for this thread I started looking
> at some libtool and cygwin documentation, and I noted that Win32 platforms
> don't like unresolved objects in DLLs. Adding -mno-undefined to the linker
> flags seems to work and as a bonus I was able to build a cygwin ethereal
> *with plugins* (it required linkage to libethereal); I can now run
> "./configure --enable-gtk2" from the command-line, and I get a fully
> functional ethereal. Agreed, it takes about an hour to fully compile on my
> 650 MHz laptop, but it works at last again.
>
> However I am really puzzled on the "build a native Win32 app with cygwin
> tools" scenario which I eventually want to succeed again with the shared
> library architecture.
>
> Could you tell me with which version of the Ethereal sources you're
> working, as there has been a point in time when the *NIX/cygwin builds
> moved from static libraries to shared libraries.
>
> Best regards,
>
> Olivier
>
> |-----Original Message-----
> |From: Stephen Blackheath
> |
> |
> |Olivier,
> |
> |I've solved the problem.  For whatever reason .la libraries
> |don't work on
> |Cygwin.  The attached patch fixes the problem by changing it to use .a
> |instead of .la libraries.
> |
> |Can I give you the job of posting the outcome of this to the
> |ethereal-dev
> |list?  I'm not subscribed.
> |
> |
> |Steve
> |
> |On Thu, 29 Apr 2004 13:17, Stephen Blackheath wrote:
> |> Olivier,
> |>
> |> I'm working on this one.  It seems libethereal.la is empty,
> |
> |apart from the
> |
> |> things added to it in the libethereal_la_LIBADD line.  See
> |> epan/Makefile.am.
> |>
> |> It'll be some kind of Cygwin or autotools bug.
> |>
> |>
> |> Steve

Attachment: ethereal-build.tar.gz
Description: application/tgz