From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <9609212220.AA13797@clio.rice.edu> Subject: Re: [KendallB AT scitechsoft DOT com: (Fwd) PoV-Ray compiling with DJGPP2.01] To: dj AT delorie DOT com (DJ Delorie) Date: Sat, 21 Sep 1996 17:20:26 -0600 (CDT) Cc: robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de, djgpp-workers AT delorie DOT com, kendallb AT scitechsoft DOT com In-Reply-To: <199609211809.OAA24763@delorie.com> from "DJ Delorie" at Sep 21, 96 02:09:07 pm Content-Type: text Content-Length: 717 > > Is there a strong reason NOT to include a.out support? > > It makes it more obvious to people that V1 libraries can't be used > with V2, since the linker will refuse to use them (if they're a.out) > rather than produce a program that crashes. Not clear at all, based on the messages you get currently. Unless someone modifies them to say "a.out not supported, recompile your libraries". V1.x compiled code except for the libc (which had changes in globals) and some calls to libc routines (IOB, etc) work just fine under V2.x. Is there some compelling reason to break the .OBJ to .O tool which has been provided (just because it's a.out?) Are we now trying to discourage commercial development with DJGPP?