delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:483 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!netline-fddi.jpl.nasa.gov!nntp-server.caltech.edu!ashley |
From: | ashley AT alumni DOT caltech DOT edu (Allen M. Ashley) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: I can't even get it installed!(NOT FUNNY damn it!) |
Date: | 21 Jun 1995 11:29:49 GMT |
Organization: | California Institute of Technology, Pasadena |
Lines: | 20 |
References: | <DAFIzn DOT 8C3 AT jade DOT mv DOT net> <3s6d2q$luc AT gap DOT cco DOT caltech DOT edu> <3s8t78INN5o3 AT CS DOT UTK DOT EDU> |
Nntp-Posting-Host: | alumni.caltech.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
I have tried to respond to another post and my mail bounced. I would like to ask here why it should take 45 minutes to install a compiler? Why should it take 3000 files or 500 files? I think a distribution package should include: 1. cc.exe 2. library module 3. stdio.h and a few other header files 4. env.bat to set up the environment 5. some doc files and examples 6. GO32 Let the developer's package include source and make capability. I don't care to twiddle with the compiler. -- ============================================== Allen Ashley ashley AT alumni DOT caltech DOT edu =============================================
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |