🚀 go-pugleaf

gcc-2.1 configured for next

NeXT 2.1 "ld" returns the following error, e.g. when making gperf:

ld: options.o symbol 61 (___DTOR_LIST__) has unknown n_type field (0x16)

since "collect2" feeds the system's loader "ld", g++ stuff cannot be
loaded.

Additionally, "nm" displays a "?" as type field for __CTOR_LIST__ and
__DTOR_LIST__ when applied as "nm options.o".

The problem results from the default code in varasm.c defining constructors
and destructors.  To fix insert

	#define ASM_OUTPUT_CONSTRUCTOR(FILE,NAME)
	#define ASM_OUTPUT_DESTRUCTOR(FILE,NAME)
	#define ASM_OUTPUT_GC_ENTRY(FILE,NAME)

into config/next.h as an "#else" to the "#if 0" which surrounds alternative
definitions and promises for them to work under NeXT system 3.0.

PS: varasm.c contains the same definition for these operations as does,
e.g., config/aoutos.h. Wouldn't it make more sense for varasm.c not to do
anything and let the various machine files take appropriate action?