[Hamlib-developer] libltdl / FT747GX timeout problem - solved?

[Kamal M. <ka...@wh...>]

Stephane Fillod wrote:
> Looks like there's a problem with the embedded libltdl.
> [...] can you install libltdl-dev ?

Chris Bryant skribis:
> Ok Stephane, that fixed it, thanks. I'm using debian unstable here, to be sure 

Stephane Fillod wrote:
> Thanks for confirming the libltdl-dev issue. On a side note, that means we have
> to fix that problem before thinking of releasing hamlib 1.2.11.

Chris Bryant wrote: 
> Btw I didn't have that probelm building 1.2.10 from source (d/l from the 
> sourceforge d/l page)


Sorry I'm arriving late to the party here folks...

I suspect that this libltdl problem is related to the change I made on
2010-03-01 (r2841) which affected the way hamlib selects which libltdl
to use:
http://sourceforge.net/mailarchive/message.php?msg_name=1267470158.7216.21.camel%40fourier

At that time, the group discussed (but decided against) the idea of
removing the bundled libltdl from hamlib altogether, which would force
users to want to build hamlib from source to use their distro's native
libltdl (or build that too if their distro doesn't provide it).  FWIW,
it sounds like Chris' problem may have been avoided if we had taken that
step.

The group may want to consider the idea of dropping the bundled libltdl
again.  I'm not sure how many hamlib users even "need" it anymore (I
think libltdl is probably supplied by most distros), but we do have
evidence that its presence causes some problems: CVE-2009-3736, and now
Chris' problem.  Is the benefit of bundling libltdl worth the burden
that it imposes on hamlib?

73 de KA6MAL

 -Kamal