#32599: blt on OSX 10.7 Lion: generates 2 errors during compilation ---------------------------------+------------------------------------------ Reporter: fsalgado@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: lion clang | Port: blt ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * keywords: blt;Lion;10.7.2 => lion clang * owner: macports-tickets@… => markd@… * milestone: MacPorts 2.0.4 => Comment: I see you're using clang. Does it help if you use [wiki:ProblemHotlist#compiler a different compiler]? -- Ticket URL: <https://trac.macports.org/ticket/32599#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32599: blt on OSX 10.7 Lion: generates 2 errors during compilation ---------------------------------+------------------------------------------ Reporter: fsalgado@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: lion clang | Port: blt ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Replying to [comment:2 fsalgado@…]:

it’s the automatic installation from ports.

Right. And in this case, MacPorts' choice may not have been the best one for this port. Once you figure out if one of the other compilers works, we can fix the port to automatically choose that instead.

is there a way to “choose” another complier on this automated set-up?

Instructions are in [wiki:ProblemHotlist#compiler the problem hotlist]. -- Ticket URL: <https://trac.macports.org/ticket/32599#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32599: blt on OSX 10.7 Lion: generates 2 errors during compilation ----------------------------------+----------------------------------------- Reporter: fsalgado@… | Owner: markd@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: fixed | Keywords: lion clang Port: blt | ----------------------------------+----------------------------------------- Changes (by ryandesign@…): * cc: neumann@… (added) * status: new => closed * resolution: => fixed Comment: Has duplicate #33146 which says apple-gcc-4.2 works, but we want to use llvm-gcc-4.2 instead if that works. [http://lists.macosforge.org/pipermail /macports-dev/2012-February/017686.html This mailing list post] says that llvm-gcc-4.2 does work, so I've changed the port in r89711 to use that. -- Ticket URL: <https://trac.macports.org/ticket/32599#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32599: blt is missing includes and fails to compile with clang ----------------------------------+----------------------------------------- Reporter: fsalgado@… | Owner: markd@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: clang Port: blt | ----------------------------------+----------------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/32599#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32599: blt is missing includes and fails to compile with clang ----------------------------------+----------------------------------------- Reporter: fsalgado@… | Owner: markd@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: clang Port: blt | ----------------------------------+----------------------------------------- Comment(by neumann@…): I stepped over the blt port, while i was testing the effects of a threaded tcl on depending ports. I have no blt apps around. As it looks to me the current blt port is not usable, the demos are not working, at least the blt::tile support seems missing. While browsing around, it seems that the way to go is to use blt 2.5 http://pdqi.com/w/pw/pdqi/Wize/Blt. I made a quick attempt to provide a portfile for 2.5 (see attachment), but currently it seems to fail to find the tcl and tk library during the destroot step - most likely for an macports expert a trivial task. Maybe the provided incomplete port helps to reduce some typing. -- Ticket URL: <https://trac.macports.org/ticket/32599#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS