× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: FreeBSD port ?
  • From: "Scott Klement" <infosys@xxxxxxxxxxxx>
  • Date: 01 Oct 1999 19:17:02 -0500

"Jason M. Felice" <jasonf@Baldwingroup.COM> wrote:
>
> > Hello,
> >
> > Last time I checked there really wasn't anything Linux
> > specific in the code.  I've gotten it working on SVR4
> > based machines.  Also, I have not seen any of the people
> > on the list foaming at the mouth about Linux vs Anything.
> > Except maybe some toy from Redmond.  And, even that is
> > being supported somewhat here.
> >
> > So, I wouldn't expect that it would take much work to port
> > it to BSD.  Have fun.
>
> Let me add two notes to that - BSD uses BSD curses, and Linux uses G
> ncurses.  The configure script tries to find GNU curses, but will fa
> fall back on BSD curses, if it does you might get a bunch of errors
> (mostly because there isn't any color support in BSD curses last I
> checked).

Hmmm... well, I can't speak for BSD, but FreeBSD (which isn't exactly
the same thing) comes with both curses AND ncurses.  But it apparently
comes with an older version of ncurses than Linux does.  (Probably
because of the whole termcap vs. terminfo thing)

>
> Installing GNU curses is recommended, unless you're colorblind ;)

Not necessary... the colors work fine under FreeBSD, once you get it
to compile :)

>
> If you want it to run under BSD curses, try to compile and mail me t
>  errors, and I'll try to help ...
>
> -Jay

Okay, here's the patches that I used to make version 0.13.12 compile,
maybe you can find a way to incorporate this into the base distrib...


Patch for cursesterm.c:

--- cursesterm.c.dist   Fri Oct  1 18:49:05 1999
+++ cursesterm.c        Fri Oct  1 18:51:42 1999
@@ -25,7 +25,9 @@
 #include <sys/time.h>
 #include <sys/types.h>
 #include <unistd.h>
-#include <curses.h>
+/* #include <curses.h> */
+typedef int attr_t;
+#include <ncurses.h>
 #include <signal.h>
 #include <string.h>
 #include <ctype.h>


patch for tn5250.c:

--- tn5250.c.dist       Fri Oct  1 18:49:14 1999
+++ tn5250.c    Fri Oct  1 19:02:47 1999
@@ -20,6 +20,7 @@
 #include <stdlib.h>
 #include <stdio.h>
 #include <string.h>
+#include <unistd.h>
 #ifdef HAVE_GETOPT_H
 #include <getopt.h>
 #endif


Patch for portsnoop.c:

--- portsnoop.c.dist    Fri Oct  1 19:00:59 1999
+++ portsnoop.c Fri Oct  1 19:01:12 1999
@@ -12,6 +12,7 @@
 #include <sys/ioctl.h>
 #include <fcntl.h>
 #include <netdb.h>
+#include <netinet/in.h>
 #include <arpa/inet.h>
 #include <unistd.h>


Then, of course, theres the keyboard mapping issue.  I'm working on
getting a full map... but if someone wants to try for themselves,
they need to:

1) Set up a termcap that handles all the necessary keys...

2) Depending on what keys they want to handle which things, they
     may need to change the syscons settings that map a scancode
     to a key...  these are in /usr/share/syscons/keymaps


I will try to work on getting the keyboard maps for FreeBSD finished
as well as see what patches are needed for 0.13.13 when I return
from my trip...  (I still need to set my machine up to grab from
cvs as well)

So, I'll be gone for 10 days :)  good luck!

Scott Klement
FreeBSD-guru-wannabe.
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.