BJ> Congradulations.....

 BJ> You took a different approach that I was 
 BJ> considering for my initial work.  I didn't want to 
 BJ> try compiling on Linux until I had stuff compiling 
 BJ> under OS/2.....  
 
Thanks!  Not knowing anything about OS/2, and having one goal (get it
running under Solaris) made my decision pretty easy. Linux was chosen as an
intermediary port because I knew my Alpha CPU would be easier to get
running with Maximus than a Sparc. The Alpha is little-endian, and under
Linux it is tolerant of mis-aligned access (although that tolerance is VERY
expensive, because it is via a hardware trap intercepted by the kernel and
"adjusted" there).
 
 BJ> After finding I had the user libraries for ncurses installed, but not 
 BJ> the development support, I installed the additional 
 BJ> related ncurses packages....  After messing around 
 
I've added ncurses detection in configure to the TODO list. Actually,
curses works too, but I don't think that's available under Linux.
 
 BJ> that far along, I need to setup my user and group 
 BJ> for the bbs development, copy over a number of 
 BJ> files from the running (os/2 based) system and see 
 BJ> where things go.  
 
That will be a particularly interesting exercise, as I'm not sure all
struct sizes have been correctly preserved. That said, since you're running
Intel arch, you at least have a good chance of having the files work.
 
Also, you mind compiling a mex file under OS/2 and Linux, and seeing if the
binary output is the same? (diff will tell you)
 
 BJ> With some slight configure file changes, we should be able to get 
 BJ> this to compile for OS/2 under the EMX setup (a 
 BJ> ported version of GCC with a runtime DLL that hooks 
 BJ> unix type system calls back to the OS/2 equivalent 
 BJ> code) and see if I can get this running there 
 BJ> also......  Could be interesting to have three 
 BJ> versions running in parallel (OS/2 max 3.01, OS/2 
 BJ> max 3.02b and Linux max 3.02b).....  It will be a 
 BJ> bit before I unleash the 3.02b versions (or later) 
 BJ> for live user testing here.  I notice there are 
 BJ> still some configuration issues to work out.....
 
Being able to run under all OSes properly will certainly be interesting,
especially if they can share files like the squish bases, user records,
etc. 
 
If you can come up with a replacement for the Dos* semaphore routines under
OS/2 which interoperate with mine (in the unix directory), that would be
super interesting, then we could synchronize things a little more safely.
 
As for porting via EMX -- If I were doing the OS/2 port (or back port, or
whatever you want to call it), I'd run GNU Make, but native compilers. You
can construct implicit makefile rules to run any compiler you want, I can
help there. You'll also want to pull the makefile.mk files out of the CVS
"attic" and see what objects are required for building under
OS/2. For example, I left out all of the assembler code..
 
Wes

--- Maximus/2 3.01