mariadb-10.0, mariadb-10.1: error: cannot use 'try' with exceptions disabled

[hbsimon (Horst Simon)]

Hi,

When building mariadb-10.1 it fails with command error, the same goes for mariadb-10.0.

OS: macOS Sierra Version 10.12.6 with XCode Version 8.3.2 (BE2002)

Log file is attached

Regards, Horst Simon

[ryandesign (Ryan Carsten Schmidt)]

I see this error on my Sierra system too. But binary archives exist on our server for these ports from June. Perhaps something changed in one of mariadb's dependencies since then to cause this?

[ryandesign (Ryan Carsten Schmidt)]

Here are the commits that changed mariadb's dependencies after it was last updated; perhaps one of them is relevant:

• ncurses: Update to 6.0-20170610
• ncurses: update to 6.0-20170708
• cmake: update release to 3.9.0
• cmake: update to 3.9.1

[ryandesign (Ryan Carsten Schmidt)]

A more complete list of changes, including changes to dependencies of dependencies:

• curl: update to 7.54.1
• ncurses: Update to 6.0-20170610
• automake: update to version 1.15.1
• libtool 2.4.6: revision bump for automake 1.15.1
• expat: security update to version 2.2.1
• expat 2.2.1: use upstream patch.
• libuv: update release to 1.13.0 and devel to d3a958d4 (20170705).
• gperf: Update to version 3.1
• libuv: update to 1.13.1
• ncurses: update to 6.0-20170708
• libarchive: update to 3.3.2.
• expat: Update to 2.2.2
• cmake: update release to 3.9.0 and devel to b5a28eb9 (20170718).
• perl5: update to 5.24.2, patch to fix test
• curl-ca-bundle: update to be884de5820a / NSS 3.32
• expat: Update to 2.2.3
• curl: update to 7.55.0
• cmake: update to 3.9.1.
• curl: update to 7.55.1
• libuv: update to 1.14.0
• expat: Update to 2.2.4
• lz4: update to version 1.8.0

I still get the error when building with trace mode, so it shouldn't be a problem of interference from a port that is not listed as a dependency.

[ruipacheco (Rui Pacheco)]

Hi,

I get this error on High Sierra.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ruipacheco:

I get this error on High Sierra.

Yes, I expect all users building from source, on any system, will get this error. If you or anyone can figure out why, please let us know!

[mkoula (Miroslav Koula)]

I have the same issue with both version mariadb-10.0 and also mariadb-10.1... Because I need it urgently I finally compiled 10.2 from the source code. It was a bit challenging, but it's working :-) but still there is so many configs around/startup scripts etc and upgrading, so I would really appreciate to have it in MacPorts working ;-)

[vnyx]

Replying to mkoula:

I have the same issue with both version mariadb-10.0 and also mariadb-10.1... Because I need it urgently I finally compiled 10.2 from the source code. It was a bit challenging, but it's working :-) but still there is so many configs around/startup scripts etc and upgrading, so I would really appreciate to have it in MacPorts working ;-)

I was also able to build from source. Here is my script after downloading the source. I was testing Mariasb 10.2. It will install in /usr/local/mysql.

#!/bin/sh

sudo port install cmake jemalloc judy openssl boost
cd ${HOME}/Downloads
if [ -e mariadb-10.2.10.tar.gz ]; then
	gunzip mariadb-10.2.10.tar.gz
	tar -xf mariadb-10.2.10.tar
fi
if [ -d build-mariadb ]; then
	rm -r build-mariadb/*
else
	mkdir build-mariadb
fi
cd build-mariadb
cmake ../mariadb-10.2.10
make
sudo make install

[ryandesign (Ryan Carsten Schmidt)]

Has duplicates #55125 and #55428, the latter of which points to some solutions.

[Bradley Giesbrecht <brad@…>]

In 19a56080311ba14c125d9623e0eda83c89286e32/macports-ports:

Update mariadb-10.0 to 10.0.33
Update mariadb-10.1 to 10.1.29
Fix builds.

Closes: #54729