Elm 2.3 PL11 compilation trouble

[Sakari Jalovaara]

To make elm on the RS/6000 I'd also suggest you put

	#include <sys/ioctl.h>

at the top of src/curses.c.  This helps elm figure out the number of
lines and columns on your terminal.

>>                                        Yet, I had to comment out all
>>declarations of string functions (e.g. strcpy, strchr, etc.), or else
>>the compiler would generate the error:
>
>If you had used the bsdcc from the bsdport document in /usr/lpp/bos,
>you wouldn't have had to go through this.

Well, bsdcc does help in this regard but it can also hurt you.  It
turns off little things like function prototypes in system include
files:

	% bsdcc -c t.c
	% cc -c t.c
	        6 |     fprintf ("hello\n");
	            ......................a.
	a - 1506-098: (E) Missing argument(s).
	%

I think finding bugs like that justifies the extra work on
net.programs (let alone my own stuff (bsdcc is even worse when
I'm writing something new.))

(Though the real fix to this particular strcpy problem would probably
be to change the compiler to use
	#pragma hey_compiler_this_is_the_string_copy_function (strcpy)
instead of
	#define strcpy(s1,s2) __inlined_strcpy((s1),(s2))
)
									++sja