mysql5 @5.1.72_2: make[2]: *** [do_abi_check] Error 1

[BjarneDMat]

--->  Dependencies to be installed: mysql5
--->  Fetching distfiles for mysql5
--->  Attempting to fetch mysql-5.1.72.tar.gz from http://nue.de.distfiles.macports.org/mysql51
--->  Verifying checksums for mysql5                                                 
--->  Extracting mysql5
--->  Applying patches to mysql5
--->  Configuring mysql5
Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
...
Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
--->  Building mysql5
Error: Failed to build mysql5: command execution failed
Error: See .../mysql5/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

[raimue (Rainer Müller)]

Please attach the referenced main.log.

[BjarneDMat]

mysql5_main.log

[ryandesign (Ryan Carsten Schmidt)]

It's not clear to me from the log why it failed, but mysql 5.1 is very old, and you probably shouldn't be installing this port anymore. Consider using the mysql55, mysql56, mysql57, mariadb-10.0, mariadb-10.1, or mariadb-10.2 ports instead.

[BjarneDMat]

I wouldn't normally install MySQL 5.1 but I got it is as a default dependency from :

Variants:             mariadb, [+]mysql5, mysql51, mysql55, mysql56, percona, universal
Library Dependencies: python36, mysql5

which is missing a mysql57 variant.

But

1. mysql51 ought not to fail building anyway
2. how about having mysql56 or mysql57 be the default in mysql5
3. kill off all support for mysql51 as it's been EOLed from Oracle

[ryandesign (Ryan Carsten Schmidt)]

Replying to BjarneDMat:

I wouldn't normally install MySQL 5.1 but I got it is as a default dependency from :

Variants:             mariadb, [+]mysql5, mysql51, mysql55, mysql56, percona, universal
Library Dependencies: python36, mysql5

which is missing a mysql57 variant.

That specific example appears to be the py36-oursql port, but there are undoubtedly many other ports in a similar situation.

But

1. mysql51 ought not to fail building anyway
2. how about having mysql56 or mysql57 be the default in mysql5
3. kill off all support for mysql51 as it's been EOLed from Oracle

Yes. The transition off of mysql5 and onto newer versions should have happened long ago, but hasn't: #43431.

I have not considered myself to be responsible for the mysql ports for several years, and invite others to fix these issues.

[BjarneDMat]

I did a "diff" on mysql5 and mysql51. The only difference is in the filename on line 1 !

So isn't upgrading mysql5 as simple as copying the portfile from mysql56 or mysql57 to mysql5 ???

As to whether we should upgrade to 5.6 or 5.7, I'll presently suggest that we use 5.6 as 5.7 has issues under macOS 10.13 : #56228 .

Doing this should also fix a lot of #43431

[ryandesign (Ryan Carsten Schmidt)]

If you're suggesting that we should update the mysql5 port to version 5.6.x, that is not the plan. The plan is that the mysql5 port is considered obsolete, and that users should move to the mysql51, mysql55, mysql56, mysql57, mariadb, mariadb-10.0, mariadb-10.1, mariadb-10.2, or percona ports as desired, and that ports that currently depend on the mysql5 port should be modified to have variants for each of those MySQL versions and derivatives. This is covered by other tickets, especially #43431.