> On Mon, 15 Dec 1997, linux kernel account wrote:
>
> > Has anyone come up with a patch for dosemu (0.67.16) so that it can be
> > compiled with the new (2.1.7x) signal code? ^^^^^^
> ^^^^^^^^
> It did not _compile_? This for sure has nothing to do with 2.1.72.
> As I understand the new signal stuff it is transparent to user space,
> so it normally should not break DOSEMU. ... and it doesn't
> I just compiled both, 0.66.7 and 0.67.16, without any problems.
> ( and yes, I _had_ the right link into the 2.1.72 header files ;-)
Hers what I see 0.67.16
----
/usr/include/sys/vm86.h:12: warning: type defaults to `int' in declaration
of `vm86'
emu.c:390: warning: return type of `main' is not `int'
emu.c: In function `leavedos':
emu.c:565: incompatible types in assignment
emu.c:565: warning: left-hand operand of comma expression has no effect
emu.c:565: warning: statement with no effect
emu.c:566: incompatible types in assignment
emu.c:566: warning: left-hand operand of comma expression has no effect
emu.c:566: warning: statement with no effect
emu.c:567: incompatible types in assignment
emu.c:567: warning: left-hand operand of comma expression has no effect
-----
and
------
SETSIG(SIG_TIME, ign_sigs);
SETSIG(SIGSEGV, ign_sigs);
SETSIG(SIGILL, ign_sigs);
SETSIG(SIGFPE, ign_sigs);
SETSIG(SIGTRAP, ign_sigs);
---------------
>
> BTW: Both DOSEMU version run fine on 2.1.72, as far as I can tell, though
> I didn't try too much (sorry Bill, not yet trusting the VFAT stuff;-)
> Anyway, till now it neither did crash, nor did it corrupt my VFAT FS.
>
> However, if you are using glibc, then it maybe that DOSEMU fails to
> compile, because we came not yet behind the recent chances. But this
> should happen on 2.0.x too.
>
> Hans
> <lermen@fgan.de>
I'm just using libc5.4.33.. I've got a working 0.66 already compiled..
0.67 did compile for me before the new signal stuff.