#58801 closed defect (fixed)
mysql57@5.7.27 does not build under OS X 10.11.6
| Reported by: | josephsacco | Owned by: | chrstphrchvz (Christopher Chavez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | cjones051073 (Chris Jones), chrstphrchvz (Christopher Chavez) | |
| Port: | mysql57 |
Description
mysql57@5.7.27 does not build under OS X 10.11.6. There is a problem with an undeclared macro, CLOCK_MONOTONIC
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_mysql57/mysql57/work/mysql-5.7.27/storage/innobase/os/os0event.cc:374:24: error: use of undeclared identifier 'CLOCK_MONOTONIC'
if (clock_gettime(CLOCK_MONOTONIC, &tp) == -1) {
^
1 error generated.
-Joseph
Change History (5)
comment:1 follow-up: 2 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | cjones051073 added |
|---|---|
| Keywords: | mysql57 removed |
comment:2 follow-up: 5 Changed 5 years ago by chrstphrchvz (Christopher Chavez)
Replying to ryandesign:
Maybe using the legacy support portgroup would help.
I have opened a pull request to use it: https://github.com/macports/macports-ports/pull/4987
MySQL regularly drops support for running any version of MySQL on older macOS versions (see https://www.mysql.com/support/eol-notice.html); currently, 10.12 and lower unsupported. Should the mysql ports indicate this?
comment:3 Changed 5 years ago by chrstphrchvz (Christopher Chavez)
| Cc: | chrstphrchvz added |
|---|
comment:4 Changed 5 years ago by chrstphrchvz (Christopher Chavez)
| Owner: | set to chrstphrchvz |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:5 Changed 5 years ago by cjones051073 (Chris Jones)
MySQL regularly drops support for running any version of MySQL on older macOS versions (see https://www.mysql.com/support/eol-notice.html); currently, 10.12 and lower unsupported. Should the mysql ports indicate this?
Not sure. MacPorts is regularly able to build ports on platforms upstream does not directly support, through the use of the various mechanisms we have such as our own (newer) compilers and the legacysupport PG. I am not sure we need to mention in each and every port when we are doing this.
That said, maybe in cases like this, where there is a direct comment from upstream on what is supported (often there isn't) we could conditionally add the obsolete PG for the Darwin versions that have been dropped.
b.t.w. legacysupport PG has indeed worked here, e.g. for 10.9
Maybe using the legacy support portgroup would help.