Mail Archives: djgpp/1994/04/08/15:43:40
> (1) During the making of 'stubedit.exe' a new version of
> 'crt0.o' is created. This new 'crt0.o' is then used
> when linking 'stubedit.exe' which I think is not meant
> that way (yet). See below for details.
> I renamed the new 'crt0.o' to 'crt0_200.o' in the makefile,
> and reinstalled 'crt0.o' from dj111m3.zip.
sample.exe should be linked with the V2.0 crt0.o and libc.a. No other
program in V2.0 should use these (at the moment). These two should
always go together - you can't mix and match.
> (2) _go32_dpmi_exception_setup() and npxsetup() seem to be
> missing, but I understand that V2.0 is under development.
Perhaps same as (1) ?
> (3) With supplied dummies for the two routines in (2) the sample
> program 'sample.c' only outputs some newlines, i.e. printf()
> doesn't show the arguments given to the program 'sample.exe'.
> (I have a Dell PC with S3 graphics)
Probably the wrong libc.a.
> My compliments for the 'djasm' program!
> (We don't need to be afraid of the Borland no-nonsense licence anymore!)
Exactly the point. The new graphics drivers and such will all be DLLs
too, so no problems there either.
- Raw text -