Ethereal-dev: Re: [Ethereal-dev] Compilation problems on rh8.0 gcc 3.2

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

From: Guy Harris <guy@xxxxxxxxxx>
Date: Fri, 8 Nov 2002 15:29:20 -0800
On Fri, Nov 08, 2002 at 03:08:36PM -0800, Jaime Fournier wrote:
> After installing a fresh redhat 8 box with gcc 3.2, I
> found a suprise.
> Instead of the tethereal file being a binary, it was a
> wrapper script generated by libtool.
> To say the least, this is not what I expected.
> So my question is this.
> What do I have to do to get the good old binary I fell
> in love with?

One of:

	1) find the magic libtool flag that says "nope, no shared
	   libraries here, just a bunch of run-time-loadable objects"
	   (assuming such a flag even exists; I don't know whether it
	   does), and the right way to tweak Makefile.am to pass that
	   flag.

	2) find the binary that the wrapper script runs.

	3) do "make install".

The rationale for the wrapper script is, I assume, in the comment at the
beginning

   # The tethereal program cannot be directly executed until all the libtool
   # libraries that it depends on are installed.

which I infer means that libtool assumes that there might be shared
libraries (as opposed to run-time-loaded objects) from the same tree
with which the binary is linked, and that if you run the binary, the
run-time linker will, by default, only look for those libraries in the
ultimate destination directory, not in the tree from which you're
running the binary.

At times I think libtool's motto should be "libtool - given what a pain
it is, just imagine how bad the alternatives must be."