Message-ID:	<3BFC9CEA.BAC53572@eluviis.ohsu.edu>
From:	Programming <prog AT eluviis DOT ohsu DOT edu>
X-Mailer:	Mozilla 4.78 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: djgpp 3.0.2 problem?
References:	<3bfc2f62 AT leia DOT ktsnet DOT com> <9ti43o$vvd$1 AT nntp9 DOT atl DOT mindspring DOT net>
Lines:	62
Date:	Thu, 22 Nov 2001 06:36:15 GMT
NNTP-Posting-Host:	66.68.63.103
X-Complaints-To:	abuse AT rr DOT com
X-Trace:	typhoon.austin.rr.com 1006410975 66.68.63.103 (Thu, 22 Nov 2001 00:36:15 CST)
NNTP-Posting-Date:	Thu, 22 Nov 2001 00:36:15 CST
Organization:	Road Runner - Texas
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

gcc 3.0.2 at last time I checked was the latest stable version of gcc version
3.
gcc 3 is a re-write of gcc that is not backward compatible with older versions.

Thus the reason things do not compile. I have had this problem with gcc 3 for
going on almost 3 years now when 3.0.0 first came out, which was total trash,
and 3.0.1 was even worse. 3.0.2 is the best so far but still not backward
compatible.

There are other problems writing code and using libraries that compile under
gcc 2 that do not compile/link under gcc 3. Optimization is one of them, some
header files have mismatched information (might be fixed in 3.0.2). To get
programs to compile and run with gcc 3 you must write the code for that or
write code that will compile under both (most often done by configuration
(configure under unix os's) or bat files under msdos (which I do not use
often).

With DJGPP I have not tried compiling without optimizations so I do not know if
that will fix the problem. However, the other 2 will work with out a problem.

Marp wrote:

> This is a known problem when compiling allegro with optimization with gcc
> 3.0.2. The allegro people are aware of this. You have 3 choices:
>
> 1. do a non-optimized build
> 2. build it with an older version of gcc
> 3. wait until it is fixed
>
> BTW, what version of allegro were you trying to build?
>
> - Marp
>
> "Cody" <cody1 AT ktsnet DOT com> wrote in message news:3bfc2f62 AT leia DOT ktsnet DOT com...
> > I just downloaded the newest version of djgpp, and when trying to compile
> > the allegro gaming library, the following error occurred:
> >
> > C:\WINDOWS\Desktop\t\djgpp\allegro\make
> > <snip successful compilations>
> > Exiting due to signal SIGSEGV
> > Page fault at eip=0002229e, error=0004
> > eax=1f2b4a0f ebx=00000000 ecx=00000001 edx=00000000 esi=2f0f4238
> > edi=00000000
> > ebp=007c6054 esp=fe1dee28
> > program=C:\WINDOWS\DESKTOP\T\DJGPP\ALLEGRO\TOOLS\DAT2S
> > .EXE
> > cs: sel=00ef  base=863eb000  limit=fe1dffff
> > ds: sel=00ff  base=863eb000  limit=fe1dffff
> > es: sel=00ff  base=863eb000  limit=fe1dffff
> > fs: sel=00cf  base=00013a30  limit=0000ffff
> > gs: sel=010f  base=00000000  limit=0010ffff
> > ss: sel=00ff  base=863eb000  limit=fe1dffff
> > App stack: [fe1e0000..fe160000]  Exceptn stack: [000db460..000d9520]
> >
> > Call frame traceback EIPs:
> >   0x0002229e
> > make.exe: *** [obj/djgpp/setupdat.s] Error -1
> > This could be a problem with allegro, but I don't think so.  Anyone have
> > some advice?
> >
> >

- Raw text -