From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_MSGID, SUBJ_ALL_CAPS autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9e20292f693f1408 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: ADA CORE TECHNOLOGIES ANNOUNCES GNAT-TO-JAVA SYSTEM Date: 1997/09/22 Message-ID: #1/1 X-Deja-AN: 274548177 References: <34196E8E.1790@gsfc.nasa.gov> <341B2309.4A41@ibm.net> <34204085.5377@ibm.net> <5vt73c$3nk$1@goanna.cs.rmit.edu.au> <602opd$f2h@mulga.cs.mu.OZ.AU> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-09-22T00:00:00+00:00 List-Id: <> I would be interested in why you think this? Is this based on experience with slim binaries? I would guess not. In fact I doubt slim binaries have been used on the kind of large projects where building from sources can be an issue. In fact building from sources works remarkably well. I am always impressed when we pull off soe new GPL tool, type the configure command, and everything works. The problems I see in building from sources (e.g. which exact version of what do you use for the build) would not be solved by slim binaries, since they still have to be compiled, and indeed all the hard part of compilation remains. So if anything the situation is worse. Now, we cannot simply use whatever standard C compiler we have around to build a tool from scratch, but we have to make sure we get the right binary version of the compiler to handle the slim binary. Indeed this is what makes GNAT harder to build than GNU C. You need a GNAT compiler to start with, and you have to make sure you get all the right versions and pieces.