[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Lout 3.35 on DOS (DJGPP)
From: |
Robert Riebisch |
Subject: |
Lout 3.35 on DOS (DJGPP) |
Date: |
Tue, 12 Jun 2007 17:54:03 +0200 |
Hi!
I'm trying to build a new version of Lout using the DJGPP 2.03p2 + GCC 4.1.2
environment.
Is any of these warnings really bad?
***
z04.c: In function 'NewToken':
z04.c:45: warning: comparison is always true due to limited range of data type
z06.c: In function 'Parse':
z06.c:1513: warning: comparison is always true due to limited range of data type
z07.c: In function 'CopyObject':
z07.c:319: warning: comparison is always true due to limited range of data type
z07.c:330: warning: comparison is always true due to limited range of data type
z12.c: In function 'MinSize':
z12.c:395: warning: comparison is always true due to limited range of data type
z12.c:436: warning: comparison is always true due to limited range of data type
z29.c: In function 'InsertSym':
z29.c:341: warning: comparison is always true due to limited range of data type
z37.c: In function 'FontRead':
z37.c:673: warning: comparison is always false due to limited range of data type
z37.c: In function 'FontChange':
z37.c:1428: warning: comparison is always false due to limited range of data
type
z44.c: In function 'EncloseInHcat':
z44.c:214: warning: comparison is always true due to limited range of data type
z46.c:411: warning: 'DebugOptimizedAcat' defined but not used
z48.c: In function 'PDFFont_AddFont':
z48.c:1045: warning: pointer type mismatch in conditional expression
z49.c:281: warning: 'ltab_debug' defined but not used
z50.c:536:1: warning: "PI" redefined
In file included from z50.c:30:
c:/djgpp/include/math.h:60:1: warning: this is the location of the previous
definition
z50.c:266: warning: 'PrintComposite' defined but not used
***
Why does Lout redefine PI?
Nevertheless I built Lout `successfully', but it behaves `strange' sometimes.
Adding
debugging switch `-dddio' together with `-r2' or `-r3' results in SIGSEGV exits.
Bfdsymify shows this trace:
***
Call frame traceback EIPs:
0x0000950b .debug_frame+147, file c:/home/lout-3.35/z02.c, line 636
0x00019209 .debug_info+6436, file c:/home/lout-3.35/z05.c, line 814
0x0002140c .debug_info+646, file c:/home/lout-3.35/z06.c, line 821
0x0001980b .debug_info+371, file c:/home/lout-3.35/z05.c, line 848
0x0002140c .debug_info+646, file c:/home/lout-3.35/z06.c, line 821
0x000075bb .debug_line+18, file c:/home/lout-3.35/z01.c, line 898
0x00007792 main+132, file c:/home/lout-3.35/z01.c, line 971
0x00118988 __crt1_startup+176, file crt1.c
***
Line 636 in `z02.c' reads:
setword(WORD, res, file_pos, startpos, p-startpos);
Why does it blow?
Robert Riebisch
PS: Yes, I know Kein-Hong Man's port, but that was before `-r' was introduced.
--
BTTR Software
http://www.bttr-software.de/
- Lout 3.35 on DOS (DJGPP),
Robert Riebisch <=
- Re: Lout 3.35 on DOS (DJGPP), Jeff Kingston, 2007/06/12
- Re: Lout 3.35 on DOS (DJGPP), Kein-Hong Man, 2007/06/13
- Re: Lout 3.35 on DOS (DJGPP), Robert Riebisch, 2007/06/13
- Re: Lout 3.35 on DOS (DJGPP), Kein-Hong Man, 2007/06/13
- Re: Lout 3.35 on DOS (DJGPP), Robert Riebisch, 2007/06/13
- Re: Lout 3.35 on DOS (DJGPP), Kein-Hong Man, 2007/06/13
- Re: Lout 3.35 on DOS (DJGPP), Robert Riebisch, 2007/06/13
Re: Lout 3.35 on DOS (DJGPP), Robert Riebisch, 2007/06/13