Lush2: some compile warnings
Raymond Martin <[email protected]> Mon, 8 Sep 2008 14:23:04 -0400
| Newsgroups | gmane.lisp.lush.devel |
|---|---|
| Organization | Rhythmous Systems |
| Message-ID | <[email protected]> |
Hi, Upon compiling Lush2 I get some warnings, please fix : gcc -std=c99 -DHAVE_CONFIG_H -DNO_DEBUG -Wall -O3 -march=i686 -mmmx -msse -I../include -pthread -I/usr/include/freetype2 -c eval.c eval.c: In function ‘mapcar’: eval.c:314: warning: array subscript is above array bounds eval.c: In function ‘mapc’: eval.c:300: warning: array subscript is above array bounds eval.c: In function ‘mapcan’: eval.c:330: warning: array subscript is above array bounds ... gcc -std=c99 -DHAVE_CONFIG_H -DNO_DEBUG -Wall -O3 -march=i686 -mmmx -msse -I../include -pthread -I/usr/include/freetype2 -c idx1.c idx1.c:75: warning: ‘Xidx_macopy’ defined but not used ... gcc -std=c99 -DHAVE_CONFIG_H -DNO_DEBUG -Wall -O3 -march=i686 -mmmx -msse -I../include -pthread -I/usr/include/freetype2 -c lisp_c.c lisp_c.c: In function ‘dh_listeval’: lisp_c.c:1761: warning: array subscript is below array bounds lisp_c.c:1763: warning: array subscript is below array bounds ... gcc -std=c99 -DHAVE_CONFIG_H -DNO_DEBUG -Wall -O3 -march=i686 -mmmx -msse -I../include -pthread -I/usr/include/freetype2 -c nan.c nan.c: In function ‘getnanF’: nan.c:80: warning: dereferencing type-punned pointer will break strict-aliasing rules nan.c: In function ‘infinityF’: nan.c:87: warning: dereferencing type-punned pointer will break strict-aliasing rules nan.c: In function ‘getnanD’: nan.c:124: warning: dereferencing type-punned pointer will break strict-aliasing rules nan.c: In function ‘infinityD’: nan.c:131: warning: dereferencing type-punned pointer will break strict-aliasing rules nan.c: In function ‘init_nan’: nan.c:519: warning: dereferencing type-punned pointer will break strict-aliasing rules nan.c:520: warning: dereferencing type-punned pointer will break strict-aliasing rules nan.c:521: warning: dereferencing type-punned pointer will break strict-aliasing rules I got more warnings than that but did not manage to catch them in time because creating the manual spit out a long text that scrolled it out of view. Can you please redirect the output of the latex creation/transform to stderr, a log file, /dev/null, or something else. Raymond ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Lush-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lush-devel