Opened 11 years ago
Closed 10 years ago
#40957 closed defect (fixed)
synergy @1.3.8_1 fails to compile on mavericks when trying to include tr1/tuple
| Reported by: | aaron.pelton+macports@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | mavericks | Cc: | quantum7@…, SickTeddyBear, drkp (Dan Ports), mopihopi |
| Port: | synergy |
Description
build log attached
Attachments (2)
Change History (9)
Changed 11 years ago by aaron.pelton+macports@…
Changed 11 years ago by aaron.pelton+macports@…
| Attachment: | main.2.log added |
|---|
new log under ports 2.2.1 though same result
comment:1 follow-up: 2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | mavericks added |
|---|---|
| Port: | synergy added |
According to the synergy homepage, Mavericks is not yet supported. You can enter your email address on that page if you'd like to be notified when they release a Mavericks-compatible version; we can update the port then.
comment:2 Changed 11 years ago by neil_mayhew@…
The Synergy home page is out of date. I downloaded a later version of the source from svn and I was able to build Synergy (and run synergyc) without any problems. The version of the source that MacPorts is using (1.3.8) is very old (2011-10-22). The latest released version is 1.4.15, and the Synergy Blog has an entry on Oct 29 explaining that it does work on Mavericks now.
So please update the port to use a later version. I ended up using 1.4.12 because 1.4.15 uses a later version of the protocol and I wasn't able to get 1.4.15 to interoperate with the packaged 1.4.12 running on my Linux box (Debian Jessie).
By the way, I didn't need to use the workaround described in the blog. However, I'm using synergyc and not synergys so maybe that makes a difference.
comment:7 Changed 10 years ago by drkp (Dan Ports)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Updated to 1.6.3 in r136192
build log