How to Contribute a C-Kermit Binary

`How to Contribute a C-Kermit Binary`

[ Unix ] [ VMS ] [ Other ]

Unix

Check the binaries table to make sure the binary you are about to make is not already there, or is not at the current C-Kermit release level (i.e. 8.0.211). Alternatively, use FTP:
```
  $ ftp kermit.columbia.edu
  User: anonymous
  Password: [email protected]
  ftp> cd kermit/bin
  ftp> dir ck[cu]211*
  ftp> bye
  $
```
Make a fresh directory and 'cd' to it. Example:
```
  $ mkdir kermit
  $ cd kermit
```

Download the appropriate source code archive. Click on the download link or do it by hand the old-fashioned way. Example:

  $ ftp kermit.columbia.edu
  User: anonymous
  Password: [email protected]
  ftp> cd kermit/archives
  ftp> binary
  ftp> get cku211.tar.gz
  ftp> bye
  $

If you downloaded a compressed tar file, uncompress it. Examples:
```
  $ gunzip cku211.tar.gz
  $ uncompress cku211.tar.Z
```
If you downloaded a tar archive, "un-tar" it. Example:
```
  $ tar xvf cku211.tar
```
If you downloaded a Zip archive, unzip it. Example:
```
  $ unzip -a cku211.zip
```

Now you can delete the tar archive (or zip archive) if you wish:

  $ rm cku211.tar                 (or rm cku211.zip)

Read the comments at the top of the makefile to find out which target is appropriate for your computer and operating system, and then give the appropriate "make" command. Examples:

  $ make linux                    (Linux, almost any version)
  $ make freebsd51                (FreeBSD 5.1)
  $ make solaris9                 (Solaris 8 with cc)
  $ make solaris9g                (Solaris 8 with gcc)
  $ make irix62                   (IRIX 6.2)

Rename (or copy, or link) the resulting "wermit" binary to match the naming conventions in the C-Kermit binaries table. In most cases, this would be:

  cku211.makefiletarget-architecture-osversion

Examples:

  cku211.linux-alpha-db2.2        (Debian Linux 2.2 on the Alpha)
  cku211.linux-i386-db2.2         (Debian Linux 2.2 on a PC)
  cku211.solaris25-i386-2.5.1     (Solaris 2.5.1 on a PC)
  cku211.solaris25-sparc-2.5.1    (Solaris 2.5.1 on a Sun)
  cku211.solaris25g-sparc-2.5.1   (Ditto but built with gcc)

For some platforms, additional information must be included in the name. For Silicon Graphics IRIX, for example, we need the Instruction Set Architecture (MIPS level) and the Application Binary Interface:

  cku211.irix53-mips2-o32-5.3
  cku211.irix65-mips3-n32-6.5.14m

If you want to make another binary, use the "clean" target to remove the object files:
```
  $ make clean
```
and then go back to step 7.

Upload the binary (or binaries) you have built to ftp://kermit.columbia.edu/kermit/incoming/. You can use FTP or Kermit. Example:

  $ cp wermit cku211.irix62-mips3-n32.6.2
  $ ftp kermit.columbia.edu
  User: anonymous
  Password: [email protected]
  ftp> cd kermit/incoming
  ftp> binary
  ftp> put cku211.irix62-mips3-n32.6.2
  ftp> bye
  $

If you compress the binary, be sure to include the appropriate compression suffix (.Z or .gz) in the filename. Example:

  $ cp wermit cku211.irix62-mips3-n32.6.2
  $ gzip cku211.irix62-mips3-n32.6.2
  $ ftp kermit.columbia.edu
  User: anonymous
  Password: [email protected]
  ftp> cd kermit/incoming
  ftp> binary
  ftp> put cku211.irix62-mips3-n32.6.2,gz
  ftp> bye
  $

Send e-mail to [email protected] and let us know that you uploaded a binary and give any relevant information: machine/OS model and particulars, any error messages or warnings, any changes you had to make to the build procedure or source code.
To install the version of Kermit you have just built, read the installation instructions.

Thanks!

VMS

Check the binaries table to make sure the binary you are about to make is not already there, or is not at the current C-Kermit release level (i.e. 8.0.211).

Make a fresh directory and SET DEFAULT to it. Example:

  $ create/directory kermit
  $ set default [.kermit]

Download the VMS source code Zip archive. Click on the download link or do it by hand the old-fashioned way. Example:

  $ ftp kermit.columbia.edu
  User: anonymous
  Password: [email protected]
  ftp> cd kermit/archives
  ftp> binary
  ftp> get ckv211.zip
  ftp> bye
  $

Or use the Internet Kermit service as described above.

Unpack the Zip archive. Example:
```
  $ unzip -a ckv211.zip
```
Run the build procedure to make a "no-net" version (i.e. a version that does not have TCP/IP networking built in:
```
  $ @ckvker n
```
If you have a pre-5.0 VMS release, use the "old" build procedure:
```
  $ @ckvold n
```
If you experience any trouble, read the comments at the top of the build procedure.
Rename the resulting WERMIT.EXE binary to match the naming conventions in the C-Kermit binaries table:
```
  ckv211-architecture-vmsNN-nonet.exe
```
where architecture is "vax" or "axp" (or maybe by the time you read this, "ia64"); NN is the VMS version number, such as "72" for 7.2, and "nonet" means no networking. Examples:
```
  ckv211-vax-vms47-nonet.exe
  ckv211-axp-vms62-nonet.exe
```
If you have a TCP/IP product installed, create a second binary with TCP/IP networking built in:
```
  $ @ckvker
```
(or @ckvold for VMS 4.x or ealier).
Rename the second WERMIT.EXE binary like the first one, except this time include the TCP/IP product and version:
```
  ckv211-architecture-vmsNN-netVV.exe
```
where netVV is a three-letter code for the network product and its two-digit version number (with no decimal point):
  ucx  DEC TCP/IP
  tgv  TGV MultiNet
  pst  Process Software TCPware
  twg  The Wollongong Group WIN/TCP or PathWay
  cmu  Carnegie-Mellon University CMU/IP
Examples:
```
  ckv211-vax-vms55-ucx20.exe
  ckv211-axp-vms62-tgv41.exe
  ckv211-axp-vms73-ucx51.exe
```
If you want to make more binaries, use the build procedure's "c" option to remove the object files:
```
  $ @ckvker c
```
and then go back to step 5.

Upload the binary (or binaries) you have built to ftp://kermit.columbia.edu/kermit/incoming/. You can use FTP or Kermit. Example:

  $ ftp kermit.columbia.edu
  User: anonymous
  Password: [email protected]
  FTP> cd kermit/incoming
  FTP> binary
  FTP> mput ckv211*.exe
  FTP> bye
  $

Send e-mail to [email protected] and let us know that you uploaded a binary and give any relevant information: machine/OS model and particulars, any error messages or warnings, any changes you had to make to the build procedure or source code.
To install the version of Kermit you have just built, read the installation instructions.

Thanks!

Other

[ Top ] [ C-Kermit Home ] [ Kermit Home ]

C-Kermit 8.0 / Columbia University / [email protected] / 17 March 2003