Re: [Hamlib-developer] Re: mac os x libtool problem

[Stephane F. <f4...@fr...>]

Hi Jim!

I hope your trip went well, away from all the troubles and bad luck
you guys have over there.

Anyway, I did some work on the Max OS X port. Thanks to the sourceforge
compile farm, I've been able to get hold of a G4 to play with.
After some hacking, I am able to build everything but the test applications
(problem in the symbol extracting, not investigated yet).
Even though I haven't tried it, straight linking should be possible
without using libtool (the culprit).
libtool porting on Mac OS X is explained at 
  http://fink.sourceforge.net/doc/porting/libtool.php
and the following link talks about a hack with does not work completely.
  http://mail.gnu.org/pipermail/libtool/2001-October/005616.html

<<
libtool 1.4: Long in the works and recently released as the new stable
version, this branch has better autoconf integration. Unfortunately that
makes migrating packages from 1.3 non-trivial. It supports Darwin 1.3 / Mac
OS X 10.0 out of the box and needs a small patch to work on Mac OS X 10.1.
It can be recognized by the absence of ltconfig. Versions that identify
themselves as 1.3b or 1.3d are actually development snapshots of 1.4 and
must be treated with caution
Side note: The libltdl library included with all libtool versions will only
work on Darwin when dlcompat is installed
>>

But there's hope. Lately, one fellow on the libtool mailing list offered 
to work on fixing libtool on Mac OS X. Darwin rule rules :)

In the mean time, I also bought a Kenwood TH-F7E (the european version 
of the TH-F6A). It has a PC connection, and I've made it to work
under Hamlib! So the kenwood backend is on a good way!

Let me know how it goes on your side.

73,
Stephane - F8CFE