too many enumerated types?

[Guy Harris]

>What is going on here?  Am I out of room in the symbol table for
>all my enumerated values?

Probably not.  A quick check of the "ld" source reveals that the error
message in question is printed if an "fwrite" of one symbol table entry
fails to return 1.  The most likely causes of this are:

	1) an error from a "write" call in the standard I/O library
	   failing - i.e.:

		you ran out of disk space

	   or

		you overflowed the stupid 1MB default file size limit
		that many S5 implementations use (I guess they're scared
		to up the default to infinitely, or at least some large
		value - hey, guys, it's not in the SVID, AT&T won't yank
		your S5 license if you default it to a huge value, and
		many many many of your customers will probably love you
		for it)

	   or

		you got a real live I/O error

	   or...

	2) a bug in standard I/O in your system.

It definitely has nothing to do with "too many enumerated types"; you're
making a fairly broad assumption by concluding that it's the problem.

My guess would be that it's 1).  If so, there are a variety of
techniques for upping the ulimit; I think in S5R3.2 you can simply
reconfigure your system to set the default higher.  I'd advise that you
set it as high as you can.

>What other nasty little quirks await me?

Hard to say.  There are a variety of other differences; I don't have a
list of all of them handy.

>Is it tougher to port from BSD to System V, or vice-versa?

Hard to say.  It depends on what you're doing.  It's tougher to port
from a system that supports the facilities you use to a system that
doesn't; in some cases vanilla BSD has the facilities and vanilla S5
doesn't, and in other cases vanilla S5 has the facilities and vanilla
BSD does't.

Note that in your case you're not dealing with vanilla BSD, though; both
Ultrix and SunOS have a number of S5 facilities in addition to BSD
facilities.