Bugs item #1822907, was opened at 2007-10-30 18:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=118378&aid=1822907&group_id=18378
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jukka Salmi (jukka)
Assigned to: Nobody/Anonymous (nobody)
Summary: libticables: conflicting types (at least on NetBSD)
Initial Comment:
On a NetBSD system libticables fails to build:
$ make
[...]
gcc -DHAVE_CONFIG_H -I. -I.. -I../intl -DLOCALEDIR=\"/usr/local/share/locale\" -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include -DTICABLES_EXPORTS -Wall -g -O2 -D__BSD__ -D__I386__ -fvisibility=hidden -MT libticables2_la-hex2dusb.lo -MD -MP -MF .deps/libticables2_la-hex2dusb.Tpo -c hex2dusb.c -fPIC -DPIC -o .libs/libticables2_la-hex2dusb.o
hex2dusb.c:37: error: conflicting types for '__uint32_t'
/usr/include/machine/int_types.h:50: error: previous declaration of '__uint32_t' was here
*** Error code 1
Stop.
make: stopped in /usr/local/src/tilp2/libticables/src
*** Error code 1
On NetBSD, uint32_t is an unsigned int while ticables/src/hex2dusb.c tries to redefine it as an unsigned long. Glancing at /usr/include/inttypes.h on a Linux system reveals that they also define uint32_t as an unsigned int; thus I think this should be changed in libticables.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=118378&aid=1822907&group_id=18378
|
