Date: Sun, 09 Aug 2015 18:12:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 202204] graphics/argyllcms can't compile on FreeBSD-9 Message-ID: <bug-202204-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202204 Bug ID: 202204 Summary: graphics/argyllcms can't compile on FreeBSD-9 Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: kwm@FreeBSD.org Reporter: gja822@narod.ru Flags: maintainer-feedback?(kwm@FreeBSD.org) Assignee: kwm@FreeBSD.org Last version of graphics/argyllcms 1.7.0_1 do not compile for me. uname: FreeBSD 9.3-RELEASE-p22 #8 r286420M Errors about conflicting declarations of int64_t: In file included from ccast/axTLS/os_port.h:147:0, from ccast/axTLS/aes.c:38: ccast/axTLS/os_int.h:60:28: error: conflicting types for 'int64_t' typedef long long int64_t; ^ In file included from /usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd9.3/4.8.5/include-fixed/sys/types.h:72:0, from /usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd9.3/4.8.5/include-fixed/unistd.h:46, from ccast/axTLS/os_port.h:127, from ccast/axTLS/aes.c:38: /usr/include/sys/_stdint.h:49:20: note: previous declaration of 'int64_t' was here typedef __int64_t int64_t; ^ If I comment out lines 57 till 66 in os_int.h: /* typedef signed char int8_t; typedef signed short int16_t; typedef signed int int32_t; typedef long long int64_t; typedef unsigned char uint8_t; typedef unsigned short uint16_t; typedef unsigned int uint32_t; typedef unsigned long long uint64_t; */ And insert line with system include in top of these files: cast_channel.pb-c.c and protobuf-c.c: #include <sys/types.h> Then compilation goes till the end. (Not sure about working correctness.) -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202204-13>