[fpc-devel] DOS Platforms

[Lee, John]

I've never been able to make go32v2 make work properly under w2k/xp, and neither has anyone else afaik - because of the well known bugs...Not worth trying imho - best to use real dos. 

Current make cycle (just compiler & rtl) & go32v2zip (whole release) works fine under win9x - I use ME.  

Both v20x and v21x and v20 release makes work at present for me, using the fpc.zip from ftp & unzipping into clear directories, using the make that's included, dos window under win me. The resulting compiler/rtl sort of works too...As you've heard exceptions cause a crash- they used to work but stopped around Feb 2005, probably when the asm calling conventions were changed for v19.

... I'd try v21x - v20x & v20 will probably then work anyway.  

I'll upload v20x & v21x snapshots onto ftp.freepascal.org ... \snapshot\v21 & v20 soon. 

Regards John

-----Original Message-----
From: fpc-devel-bounces at lists.freepascal.org
[mailto:fpc-devel-bounces at lists.freepascal.org]On Behalf Of Vinzent
Hoefler
Sent: 25 May 2005 13:03
To: FPC developers' list
Subject: Re: [fpc-devel] DOS Platforms


Ok, first status on the matter:

Tonight I've spent some time with the sources and my Win2K machine. For 
me it seems as the Makefile(.fpc)'s are not yet up to date for the 
go32v2 target (object files didn't get deleted on cleanall, some unit 
paths were missing, that sort of stuff) [FYI: I checked out the current 
2.0.1 from CVS], but in the end I managed to make the compiler cycle 
manually. Hmm, well, let's see if I still remember how I did it, when I 
get back to it this evening ;).

Result: I get occasional seg faults (probably related to the ntvdm bug 
mentioned in the current djgpp, so this is definitely something to 
try). I can compile a simple hello world (huhu, what an achievement, 
but, hey, look at that matter when it's 3.30am).
Next test was to check some files from the tests/test stuff and those 
(very) few I checked seemed to compile quite ok. BTW, the tstring1.pp 
failed horribly (on successfull execution of the test, not on 
compilation) just like the current fpc does (don't you happen to 
actually run these tests?).

So it's definitely some more work to do, especially for building release 
version etc.pp., but at the first glance it doesn't look too hard.

> I can help on doing dos makes eg under win9x - I do them every day
> for dos snapshots.

Well, if you could manage to send me a makefile, so that I don't have to 
hack it myself (using Pascal and Ada for years, I somehow got used to 
the fact that makefiles are mostly unnecessary complex and outdated 
C-related stuff), that would be nice.

It also seems, I'll get an old Win95 system up und running in the next 
few days, so I even can do tests for the most important environments.

> ... and setting up a comfortable environment to develop in. The
> compiler sources itself aren't that interresting, more the runtime
> environment end the IDE. But for now just try to run a make cycle.

Well, I just tested in on my linux box, there it runs just fine (well, 
with fpc2.0.0, that is). It *should* not make any difference if I use 
fpc1.0.10, should it? Or am I missing something here?

> The Buildfaq documents it very nicely

Yes. Even I could understand it. ;-)

> and if you've got questions, just ask.

Well, at the moment I'd say, I take look at the makefile, see what I do 
with those "error setting exception" messages and trying to compile 
something larger to test with. I expect hard-to-find effects soon 
enough.

Oh, yes. One question: Should I use the current fpc2.0.1 release from 
the CVS or would it be better to switch to the 2.1.x branch already to 
not get too far behind the current development? Just don't say 
"both". ;-)


Vinzent.

-- 
public key: http://www.t-domaingrabbing.ch/publickey.asc


_______________________________________________
fpc-devel maillist  -  fpc-devel at lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.