| www.delorie.com/archives/browse.cgi | search |
| From: | Stefan Ring <e9725446 AT student DOT tuwien DOT ac DOT at> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Allegro problem |
| Date: | Thu, 19 Mar 1998 11:42:28 +0100 |
| Organization: | Vienna University of Technology, Austria |
| Lines: | 12 |
| Message-ID: | <Pine.HPP.3.91.980319114101.9519B-100000@stud3.tuwien.ac.at> |
| References: | <350CC698 DOT 54E1 AT bellatlantic DOT net> <3510740C DOT 6B8A6FDA AT netrover DOT com> |
| Reply-To: | Stefan Ring <sring AT gmx DOT net> |
| NNTP-Posting-Host: | stud3.tuwien.ac.at |
| Mime-Version: | 1.0 |
| NNTP-Posting-User: | e9725446 |
| In-Reply-To: | <3510740C.6B8A6FDA@netrover.com> |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
On Wed, 18 Mar 1998, Nicolas Blais wrote: > No you are not doing anything wrong, open the "makefile" in the allegro > directory, and look for the cc1.exe statement on line 31 and replace > cc1.exe by gcc.exe. Try make again, and go do something while the it > compiles (Takes 20 minutes on a PII333) > When I compile it on my Cyrix P166+ (133MHz), it takes no longer than 8 minutes. Must be a *pretty badly* configured P2 !! Use a ramdisk! (at least for the temp files)
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |