Changeset 94640


Ignore:
Timestamp:
Jun 25, 2012, 8:01:54 PM (7 years ago)
Author:
cal@…
Message:

libinfinity: Update to 0.5.2, use llvm-gcc-4.2

libinfinity source uses g_return_if_fail in functions that should return
a value. clang correctly errors on this.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/dports/comms/libinfinity/Portfile

    r86765 r94640  
    55
    66name            libinfinity
    7 version         0.5.1
     7version         0.5.2
    88description     libinfinity is an implementation of the Infinote protocol written in GObject-based C.
    99long_description ${description}
     
    1515master_sites    http://releases.0x539.de/libinfinity/
    1616
    17 checksums       rmd160  12d57cbb12f961bea842a47bae9b7a83ea2f085b \
    18                 sha256  783071349fc6e08e2af6564bc46b3d4a44122991c9330b26553e01bcc42cb573
     17checksums       rmd160  ba5440f0864711944770d67b25ca1a8307072efa \
     18                sha256  940c9a4c5ab5925020bac48bd54295cdd1ae3bef7035191da95495ecc9daee9a
    1919
    2020depends_build   port:pkgconfig
     
    2525                port:gnutls \
    2626                port:libgsasl
     27
     28if {${configure.compiler} == "clang"} {
     29    # libinfinity doesn't build with clang because some functions use g_return_if_fail() where they should use g_return_val_if_fail()
     30    configure.compiler llvm-gcc-4.2
     31}
    2732
    2833# /usr/bin/ranlib: library member: libinftestutil.a(libinfinity-0.5.la) is not an object file (not allowed in a library with multiple architectures)
Note: See TracChangeset for help on using the changeset viewer.