Xref:	news-dnh.mv.net comp.os.msdos.djgpp:1483
Path:	news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!news.ingr.com!news.msfc.nasa.gov!pendragon.jsc.nasa.gov!ames!waikato!comp.vuw.ac.nz!mu.sans.vuw.ac.nz!empty
From:	empty AT sans DOT vuw DOT ac DOT nz (Malcolm Taylor)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: v2 problems compiling old code
Date:	11 Aug 1995 11:29:54 GMT
Organization:	SANS, Student Access Network System
Lines:	20
References:	<DD4xB4 DOT KJs AT jade DOT mv DOT net>
Nntp-Posting-Host:	mu.sans.vuw.ac.nz
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

Marc Anton Sperisen (msperise AT iiic DOT ethz DOT ch) wrote:
: Hi,
: I have written a program in v1 and lately changed it to grx2.0 beta grafix.
: Now I installed DJGPP V2 and tryed to compile the program with the same
: compiler options. Unfortunately the combilation had some "(in text 0x256) 
: reference" errors.
: Do I have to recompile the grx20 stuff for v2? Is there an othere problems 
: with the recombilation of old code? How can I deal with error msgs that have
: hex error locations, how can I locat the problem in the source?
: Do signals work like the linux version? What is the best way to catch exeptions and illegal opcodes, who can i access the registers of the trapping cpu state?

A probable cause is that some of your object files are still there from 
the v1... Delete all the .o files and then re make your project. Object 
files compiled with v1... will not link properly (generally) with v2.0 
code. This may not be the problem, but it seems the most likely.

Malcolm

: Thanx
: Marc

- Raw text -