Mail Archives: djgpp/2001/07/09/08:00:08
From: | Gero Timann <gtimann AT nexgo DOT de>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | gcc 3.0 problem ?
|
Date: | Fri, 06 Jul 2001 11:43:42 GMT
|
Organization: | [neXgo] the next generation online
|
Lines: | 13
|
Message-ID: | <1103_994419822@default>
|
NNTP-Posting-Host: | b8cb0.pppool.de
|
Mime-Version: | 1.0
|
X-Trace: | newsread2.nexgo.de 28111 NG Z3RpbWFubg==
|
X-Complaints-To: | abuse AT germany DOT net
|
NNTP-Posting-Date: | 9 Jul 2001 11:46:23 GMT
|
User-Agent: | Mozilla/4.76 (Windows 95; U) Opera 5.12 [en]
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
Hallo !
Some problems occur, if i recompile the allegro-lib with gcc 3.0.
Compile run's fine, but the resulting library doesn't work, if it's compiled
with optimation-flag -O2 or -O3. Ok, allegro is very a complicate near
hardware programmed library, but, strange, -O1 and -O2/-O3 with
generating debugging code (=-g) works (strange !?). Never seen
this with gcc 2.95.3, therefore it's maybe a gcc3.0-problem.
Gero
- Raw text -