search

Roverok / libnfc

Automatically exported from code.google.com/p/libnfc
GNU Lesser General Public License v3.0
0 stars 0 forks source link

fix compiler warnings #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Using GCC with some warning flags reveals some potential issues, among a
possible buffer overflow issue (array out of bounds).

Search for "warning" @
http://koji.fedoraproject.org/koji/getfile?taskID=1915037&name=build.log

Original issue reported on code.google.com by fkooman%tuxed.net@gtempaccount.com on 11 Jan 2010 at 8:43

GoogleCodeExporter commented 9 years ago 
Hi François,

Thanks for report.
This should be fixed in r260

Original comment by romu...@libnfc.org on 12 Jan 2010 at 12:38

GoogleCodeExporter commented 9 years ago 
Much better indeed. Some are still left (or new?) Also a Doxygen warning now as 
I
included Doxygen API generation in CMake files now. Maybe Fedora development 
has a
too new doxygen ;)

http://koji.fedoraproject.org/koji/getfile?taskID=1917370&name=build.log

Original comment by fkooman%tuxed.net@gtempaccount.com on 12 Jan 2010 at 7:24

GoogleCodeExporter commented 9 years ago 
Remaining warnings in C code should be avoid defining _XOPEN_SOURCE=600 in linux
boxes. Autotools suite generate a "config.h" that contains _XOPEN_SOURCE define
depending platform. So, if you want to compile without warnings, you must 
reproduce
_XOPEN_SOURCE=600 in "config.h" and define HAVE_CONFIG_H using compiler command 
line.
(This change appears in r262).

Regarding Doxygen warning, it should be fixed (r264), thanks !

Original comment by romu...@libnfc.org on 13 Jan 2010 at 2:19

GoogleCodeExporter commented 9 years ago 
Fixed in r292

Original comment by romu...@libnfc.org on 1 Feb 2010 at 4:39