jnall%FSU.BITNET@cunyvm.cuny.edu (John Nall 904-644-5241) (04/17/89)
With reference to my previous message regarding problems with trying to build a Minix 1.4a system under Turbo C, using Deborah Mullen's set of codes which were put on the net: I think that I've gunned out the undefined symbol "_interupt" in module MPX88.ASM, by going in and changing that to be identical to the named used to replace the keyword "interrupt" in the .c routines. But the undefined "init_rs232, rs_out_char, set_uart" is more mysterious than ever. All of these routines are defined as PRIVATE in rs232.c. Yet, they are referenced in tty.c. It compiles and links OK in Minix. I know damned well that I'm not seeing something which is obvious!!! John Nall
mullen@sdsu.UUCP (Deborah Mullen) (04/23/89)
This is in response to Jon Nall's problems with compiling
Minix C code with Turbo C 2.0 compiler.
1) Interrupt is a keyword in Turbo C, so some other name
must be used.
2) In reference to the undefined symbols _init_rs232,
_rs_out_char and _set_uart. These routines are called
from other source files. They should NOT be declared
PRIVATE. The minix C compiler does not distinquish between
PUBLIC and PRIVATE. All routines are considered global.
The PUBLIC and PRIVATE in the minix C code is for documentation
only. I mentioned this quite a while ago and most of the
places which had PRIVATE types made it in the updates ( but
I guess not all of them, or they came back in the 1.4a update).
--Deborah Mullenjca@pnet01.cts.com (John C. Archambeau) (04/24/89)
A word about using interrupt as a function name. If you compile with ANSI
keywords only, it becomes a legal function name. I know 1.5 supports this,
and Borland would be stupid to take it out in 2.0.
JCA
UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!jca
ARPA: crash!pnet01!jca@nosc.mil
INET: jca@pnet01.cts.com