Opened 9 years ago

Closed 9 years ago

#30892 closed update (fixed)

Updated swi-prolog portfile for version 5.10.5

Reported by: pmoura (Paulo Moura) Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.0.1
Keywords: haspatch maintainer Cc:
Port: swi-prolog

Description

Updated swi-prolog portfile for version 5.10.5.

Attachments (1)

Portfile-swi-prolog.diff (859 bytes) - added by pmoura (Paulo Moura) 9 years ago.

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by pmoura (Paulo Moura)

Attachment: Portfile-swi-prolog.diff added

comment:1 Changed 9 years ago by ryandesign (Ryan Schmidt)

Why did you add the block:

platform darwin 11 { 
        configure.compiler gcc-4.2 
} 

In MacPorts 2, compilers are chosen based on Xcode version, not OS version. For example, Xcode 3.1/3.2 uses gcc-4.2, Xcode 4.0/4.1 uses llvm-gcc-4.2, and Xcode 4.2 uses clang.

Item 3 of the MacPorts on Lion (common issues, fixes, and workarounds) post shows how you should coerce the use of gcc-4.2 instead of these other compilers -- if indeed that is the only way this port will work. If this port can be made to work with clang instead of llvm-gcc-4.2, that is preferable.

comment:2 Changed 9 years ago by pmoura (Paulo Moura)

SWI-Prolog will not work with llvm-gcc-4.2 and Xcode 4.2 is not yet publicly available. SWI-Prolog developer have given up (for the moment) in trying to find a fix for llvm-gcc-4.2 (he is not a MacOS X user and is access to Lion machines is limited). I will try to look into using clang instead when Xcode 4.2 gets released.

comment:3 Changed 9 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… removed
Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

comment:4 Changed 9 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: assignedclosed

Updated to 5.10.5 in r82802, using the verbiage from MacPorts on Lion (common issues, fixes, and workarounds) to force the use of gcc-4.2. If you test clang in the future and find it works, please switch to using that instead.

Note: See TracTickets for help on using tickets.