From: Paul Garceau <pgarceau@te...> - 2001-01-03 03:19:47
On 1 Jan 2001, at 19:32, the Illustrious Sigbj=F8rn Lund Olsen wrote:
> I've just recently upgraded to Win98SE, and now I find that
> Allegro (www.talula.demon.co.uk) will no longer compile on MinGW
> even though I'm following the instructions to the letter.
Are you using the latest release of Allegro source for Win32?
If not, you could get variable conflicts between the old Allegro
source and the latest Allegro source. Allegro was initially
written for djgpp.
> getting errors like this:
> gcc -DALLEGRO_SRC -Wall -Wno-unused -m486 -O3 -ffast-math
> -fomit-frame-pointer - fno-strength-reduce -I. -I./include -o
> obj/mingw32/alleg/wddwin.o -c src/win/wdd win.c
> src/win/wddwin.c:50: warning: initialization from incompatible
> pointer type src/win/wddwin.c: In function `init_directx_win':
> src/win/wddwin.c:606: warning: assignment from incompatible
> pointer type
> My questions are as follows: What is an incompatible pointer
> type? Is there any form of documentation on the net that tries to
> explain the meaning of GCC warnings and errors?
The warnings you are talking about are just that, warnings. If
you get parse errors, that is a different story. For the most
part, the warnings don't usually cause crashes, though it will
influence how the compiler thinks of your code.
If you're using a make, try doing "make -k" to force compiler
to keep going when it gets the warnings you're talking about
Nothing real can be threatened.
Nothing unreal exists.