W9MDB
From: Alan VK2ZIW [mailto:bea...@unixservice.com.au]
Sent: Thursday, December 11, 2014 5:56 PM
To: WSJT software development
Subject: Re: [wsjt-devel] JTSDK hamlib3 build
Hi Mike,
the PATH to "ar" never should be. It's been the unix "archiver tool" since
1977.
It'
Hi Alan,
The only time you would need to state the archiver, linker and other
support binaries is when those binaries are in the system path already,
cross compiling on Linux for example. Stating CC and CXX paths should
pull what's needed.
With JTSDK v2, none of the compiler tool-chains are on $P
Hi Mike,
the PATH to "ar" never should be. It's been the unix "archiver tool" since 1977.
It's always in the "default" PATH for all users. eg. "/bin" or "/usr/bin".
"ar" pre-dates "tar" and "cpio"
Alan VK2ZIW, see my footer.
On Tue, 9 Dec 2014 23:00:31 -0600, Michael Black wrote
> Trying to bui
Trying to build hamlib3 under JTSDK without using the script which
takes WAY too long and does a bunch of stuff I don't want it to do.
But building doesn't work since the PATH to ar isn't included in the shell.
Mike
W9MDB
Black@Black-PC~/g4wjs-hamlib/build/yaesu$ make
CC new
