Re: [AD] Allegro 4.2 doesn't compile under OpenWatcom 1.0

[Evert Glebbeek <eglebbk@xxxxxxxxxx>]

> The build docs claim that OpenWatcom 1.0 is supported. First problem
> is that it doesn't include either inttypes.h or stdint.h, but the
> Allegro include defines the former.

I saw your message on A.CC about gcc 2.95 and an issue with the same file.
Was that resolved already? In any case, the build should not choke on a
missing inttypes.h or stdint.h - if it does, it's a bug we should fix.
I haven't looked at how the availability is determined but if I were to
guess I'd say that it's checked using the configure script in *nix, meaning
the detection is broken in Windows. That's a shot in the dark on my part
though.

> Commenting it out fails to work, because it does not recognize the
> #warning command. :P

Hehe. I used to get that too with gcc in a strict mode. It seems the
portable name should be #warn.

> src\midi.c(1537): Error! E1011: Symbol 'midi_timer_frequency' has not
> been declared
> make: *** [obj/watcom/alleg/midi.obj] Error 8

Elias applied a fix to CVS yesterday that should fix that problem:

--- midi.c        22 Mar 2005 20:23:57 -0000        1.21
+++ midi.c        1 Apr 2005 23:06:29 -0000        1.22
@@ -1534,7 +1534,6 @@
    LOCK_VARIABLE(midi_loop);
    LOCK_VARIABLE(midi_loop_start);
    LOCK_VARIABLE(midi_loop_end);
-   LOCK_VARIABLE(midi_timer_frequency);
    LOCK_VARIABLE(midi_timer_speed);
    LOCK_VARIABLE(midi_pos_speed);
    LOCK_VARIABLE(midi_speed);

> Version 1.3 is the most recent, but I don't have it. Is Allegro known
> to compile on that?

To my knowledge, no one has tested it.

Thanks for reporting these problems!

Evert