Very Computer

by **caitrin lyn** » Sat, 17 Sep 1994 04:39:44

I am trying to compile Ncftp 183 to work with Term2.04. Unfortunately,
the Makefile for Ncftp expects to find client.a somewhere. Now, I know
that the Term2.00+ uses libtermnet.a and maybe termnet.h instead of client.a
and maybe client.h (not to sure about the *.h's). But how do I tell Ncftp this.

Nick

--

------------------------

by **Christopher Wil** » Sat, 17 Sep 1994 10:14:29

: I am trying to compile Ncftp 183 to work with Term2.04. Unfortunately,
: the Makefile for Ncftp expects to find client.a somewhere. Now, I know
: that the Term2.00+ uses libtermnet.a and maybe termnet.h instead of client.a
: and maybe client.h (not to sure about the *.h's). But how do I tell Ncftp this.

Edit the makefile.

-- Chris

"... but I want to use all eight comm ports SIMULTANEOUSLY!"
PGP 2.6 public key available by finger for the clinically paranoid.

by **David Konerdi** » Sat, 17 Sep 1994 11:57:41

: : I am trying to compile Ncftp 183 to work with Term2.04. Unfortunately,
: : the Makefile for Ncftp expects to find client.a somewhere. Now, I know
: : that the Term2.00+ uses libtermnet.a and maybe termnet.h instead of client.a
: : and maybe client.h (not to sure about the *.h's). But how do I tell Ncftp this.

: Edit the makefile.

As of ncftp182, the makefile had a circular definition in the term part of the
Makefile (TNCFTP) that makes it quiet difficult to compile unless you hack
the makefile somewhat. Has this been fixed?

: -- Chris

: "... but I want to use all eight comm ports SIMULTANEOUSLY!"
: PGP 2.6 public key available by finger for the clinically paranoid.

--
--
O~_ ------------- David Konerding (University of California, Santa Cruz)

by **Jeff Epl** » Sat, 17 Sep 1994 12:50:29

>As of ncftp182, the makefile had a circular definition in the term part of the
>Makefile (TNCFTP) that makes it quiet difficult to compile unless you hack
>the makefile somewhat. Has this been fixed?

Not that I know of.

I run the make, and some time after it has gone recursive I come back,
ctrl-c, and issue the final link command manaully.

I couldn't figure out why the makefile did that -- It's sort of hard
to understand, for me. I always kept my makefiles simple.

Jeff
--
____ "And if I smile please tell me some bad news
\BI/ before I laugh and act like a fool"
\/ -The Who "Behind Blue Eyes"
IRC: Synger Running Linux 1.1 -- Free Unix for 386+ machines

by **Mike Gleas** » Sun, 18 Sep 1994 11:48:47

|>As of ncftp182, the makefile had a circular definition in the term part of the
|>Makefile (TNCFTP) that makes it quiet difficult to compile unless you hack
|>the makefile somewhat. Has this been fixed?

Nope. Someone needs to tell me these things, since I totally ignore the
term stuff. And if someone already told me ;-) it's better to just send
a patch, so I won't put it off. One kind soul did send a patch which did
mess with the term area, in particular the install_termman: portions. This
has been applied and will appear in the next 1.8.x release.

|I run the make, and some time after it has gone recursive I come back,
|ctrl-c, and issue the final link command manaully.

|I couldn't figure out why the makefile did that -- It's sort of hard
|to understand, for me. I always kept my makefiles simple.

Since I don't have access to Linux, I have to rely upon what others tell
me about it. I've known about the libtermnet deal, but haven't replaced
it in the Makefile because I don't know if that is all that needs to be done.
Someone should just redo the term portions of the Makefile, and send it to
me. The ftp.c source file may need to be hacked too, because it tries to
include a term header which may or may not be the correct way to do it
these days.

I've been busily working on the rewrite, which when finished, should be much
easier for me to maintain and a helluva lot more flexible on the user-end
too.

--

by **Christopher Wil** » Thu, 22 Sep 1994 03:16:40

: If you use -DTERM it won't work!!! It would probably be a good
: idea to eliminate all the term dependant code, as all of it is
: completely obsolete and really confuses people when they try
: to use it anyways. If you remind me where to find the latest
: source code for ncftp, I'll happily mail a patch.

That's funny ... I've had no problems getting NcFTP compiled with TERM
2.0.6 support. Of course, you've got to define TERM_FTP instead of TERM.

Don't be so hasty in recommending removal of the old TERM support code.
There's still some of us out here that can't get things compiled under
the new scheme, and rely upon the old rules to get things done.

-- Chris

"... but I want to use all eight comm ports SIMULTANEOUSLY!"
PGP 2.6 public key available by finger for the clinically paranoid.

by **Mike Gleas** » Sat, 24 Sep 1994 10:32:03

|That's funny ... I've had no problems getting NcFTP compiled with TERM
|2.0.6 support. Of course, you've got to define TERM_FTP instead of TERM.

|Don't be so hasty in recommending removal of the old TERM support code.
|There's still some of us out here that can't get things compiled under
|the new scheme, and rely upon the old rules to get things done.

<gulp> Too late now. Keep the 1.8.4 and below sources handy if you
require this, because it was removed as of 1.8.5. Either way, v2.0 will
need to be repatched for term support, since none of the 1.8 term stuff
was incorporated into the brand new code.

Incidentally, v2 is not that far off. I want to start full beta testing
in about a month.

--

Current version of NcFTP is 1.8.5, and is available from cse.unl.edu, in the
/pub/mgleason/ncftp directory. Public permissions are turned on daily at 5pm
CST; To decode the gzip'd tar file, do "gunzip -c ncftp.tgz | tar xvof -".

Very Computer

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00

Making Ncftp Binaries with Term > 2.00