Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#58081 closed defect (fixed)

mysql @ 5.7.25_0: Failed to build mysql57: command execution failed

Reported by: dgelmer Owned by: Schamschula (Marius Schamschula)
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: Cc:
Port: mysql57


  macOS 10.13.6 (17G5019)
  XCode 10.1
  Model Identifier:	iMac11,1
  Processor Name:	Intel Core i7
  Processor Speed:	2.8 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	8 MB
  Memory:	12 GB
  Boot ROM Version:

Attachments (1)

main.log.gz (152.7 KB) - added by dgelmer 3 years ago.

Download all attachments as: .zip

Change History (7)

Changed 3 years ago by dgelmer

Attachment: main.log.gz added


comment:1 Changed 3 years ago by mf2k (Frank Schima)

Keywords: highsierra x86_64 removed

comment:2 Changed 3 years ago by enekochan (enekochan)

I was having the same issue. As seen in #56228 the problem is that MySQL 5.7 can only use boost 1.59.0 and I had 1.66.0 installed (by another port). Removing boost and then installing MySQL 5.7 again solved the problem:

$ sudo port uninstall boost
$ sudo port clean mysql57
$ sudo port install mysql57

comment:3 Changed 3 years ago by Schamschula (Marius Schamschula)

Strange. When I updated the Portfile, I cleanly built mysql57 5.7.25 with boost 1.66.0 installed and active.

It should suffice to deactivate boost, rather than uninstalling it.

comment:4 Changed 3 years ago by Schamschula (Marius Schamschula)

A second thought:

Perhaps, in my case, building in trace mode prevented the boost issue, as mysql builds against its own version of boost, whereas the boost package is hidden.

comment:5 Changed 3 years ago by Schamschula (Marius Schamschula)

Owner: set to Schamschula
Resolution: fixed
Status: newclosed

In c4245ca8b9d3e84e0316007407362cb5a958ec23/macports-ports (master):

mysql57: use conflicts_build for boost build issue

Closes: #58081

comment:6 Changed 3 years ago by TheLastLovemark

How do I use conflicts_build ??

Note: See TracTickets for help on using tickets.