delorie.com/archives/browse.cgi | search |
From: | "Maverick" <vhd AT chello DOT at> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Compiling Allegro |
Lines: | 17 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Newsreader: | Microsoft Outlook Express 5.00.2615.200 |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.00.2615.200 |
Message-ID: | <Y6YN6.124299$2q.4385907@news.chello.at> |
Date: | Sun, 20 May 2001 23:07:36 GMT |
NNTP-Posting-Host: | 212.17.127.89 |
X-Complaints-To: | abuse AT news DOT chello DOT at |
X-Trace: | news.chello.at 990400056 212.17.127.89 (Mon, 21 May 2001 01:07:36 MET DST) |
NNTP-Posting-Date: | Mon, 21 May 2001 01:07:36 MET DST |
Organization: | Customers chello Austria |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
I've used make to compile allegro as suggested by it's own readme. It compiles without any errors, but I do wonder about the warnings it gives out when compling some parts : indirect call without '*' <--- this shows up pretty often indirect ljmp without '*' <--- this also shows up pretty often using '%ex' instead of '%ecx' due to 'w' suffix using '%si' instead of '%esi' due to 'w' suffix using '%al' instead of %eax' due to 'b' suffix Still, it compiles without errors, and I haven't checked if allegro is working anyway. And even if it is, I just wondered... can those warnings have an undesireable effect? Are they occuring because of djgpp or is it my fault? Thx, Maverick
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |