redefined data types in different packages - request for help

[Eric Gallager]

Hoping this gets fixed sometime soon, because for some reason it's been
screwing with my `camlimages` build...



On Tue, Nov 12, 2013 at 7:20 AM, Titus von Boxberg <titus at v9g.de> wrote:

> Am 11.11.2013 20:08, schrieb Mojca Miklavec:
>
>> On Sun, Nov 10, 2013 at 12:04 PM, Titus von Boxberg wrote:
>>
>>> Without having a system here to test my suggestions, you might be able to
>>> - configure tiff to not define this type name (or define it correctly in
>>> the
>>> sense of portability and compatibility, at least).
>>>
>> I cannot configure it to not define the type name "uint64". This type
>> name is used all over the place. The solution might be to define it to
>> uint64_t instead of "unsigned long".
>>
> Yes, that seems reasonable as long as uint64_t is guaranteed to be defined
> before the typedef of uint64 happens.
> Maybe you could patch tiffconfig.h.in or something else in tiff's
> configuration phase.
>
> Regards
> Titus
>
>
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20131113/09b48d45/attachment.html>