Opened 2 months ago

Last modified 2 weeks ago

#55049 assigned defect

textmate2 @2.0-rc.4: build fails under highsierra (10.13) with error: no viable conversion from

Reported by: hardwhack Owned by: neverpanic (Clemens Lang)
Priority: Normal Milestone:
Component: ports Version: 2.4.1
Keywords: sierra highsierra Cc:
Port: textmate2


Trying to build textmate2 in High Sierra (10.13) using XCode 9.0. Build fails with

:info:build Frameworks/editor/src/ error: no viable conversion from 'vector<pair<char *, char *>>' to 'const vector<pair<const char *, const char *>>'
:info:build                                 std::vector< std::pair<char const*, char const*> > const& v = text::to_lines(, + str.size());
:info:build                                                                                           ^ 

Attaching logfile. Above line # is ~2805. Tried clean followed by install and same problem.

Attachments (1)

main.log (603.4 KB) - added by hardwhack 2 months ago.

Download all attachments as: .zip

Change History (5)

Changed 2 months ago by hardwhack

comment:1 Changed 2 months ago by mf2k (Frank Schima)

  • Cc cal@… removed
  • Owner set to neverpanic
  • Status changed from new to assigned

comment:2 Changed 4 weeks ago by ryandesign (Ryan Schmidt)

  • Keywords sierra added

And on Sierra with Xcode 9.0.1.

comment:3 Changed 2 weeks ago by sierkb


The port file referrs with livecheck.url to the (outdated?) textmate website, which indeed says: 2.0-rc.4, so the port's version of textmate sticks to date to that version. But: the textmate project's upstream info on its GitHub repository on says other: latest upstream release version obviously is not RC4 (release date: 18 Nov 2016) but at least RC7 (release date: 5 Dec 2016). Or further, since there is active code commitment every now and then in the master branch (see, the latest commit is only 11 days ago from today).

Should the MacPort's port of textmate not point to at least that RC7 version code (or maybe better to master, which seems indeed very alive) rather than sticking to the obviously obsolete RC4 (for whatever reason that version has been left on instead of reflecting the actual state as its repository on GitHub)?

comment:4 Changed 2 weeks ago by neverpanic (Clemens Lang)

Yes, it should ship RC7. It's always a hassle to get newer versions to build, though. Patches welcome.

Note: See TracTickets for help on using tickets.