Re: OpenBLAS fixed in Xcode 11.2

2019-11-01 Thread Jack Howarth
The issues in gmp might not be fixed in Xcode 11.2. The exact issue isn't listed in the current gmp Portfile but 'sudo port test gmp' shows... PASS: bit ../../test-driver: line 107: 63647 Segmentation fault: 11 "$@" > $log_file 2>&1 FAIL: t-powm Jack On Thu, Oct 31, 2019 at 10:51 PM

Re: OpenBLAS fixed in Xcode 11.2

2019-11-01 Thread Saagar Jha
Does this match your stack trace? Saagar Jha > On Nov 1, 2019, at 02:09, Jack Howarth wrote: > > The issues in gmp might not be fixed in Xcode 11.2. The exact issue isn't > listed in the current gmp Portfile but 'sudo port test gmp' shows...

Re: OpenBLAS fixed in Xcode 11.2

2019-11-01 Thread Christopher Jones
Hi, Good to hear. However, Xcode 11.2 has not fixed everything, as x265 still seg. faults when build with clang from Xcode 11.2. cheers Chris > On 1 Nov 2019, at 12:49 am, Jack Howarth > wrote: > > Although it wasn't fixed in Xcode 11.2 beta 2, the -fcheck-stack issues > with OpenBLAS'

Re: OpenBLAS fixed in Xcode 11.2

2019-11-01 Thread Marcus Calhoun-Lopez
There is a pull request* that attempts to consolidate these fixes in a PortGroup. As always, any input is appreciated. -Marcus * https://github.com/macports/macports-ports/pull/5673 > On Nov 1, 2019, at 3:08 AM, Christopher Jones > wrote: > > Hi, > > Good to hear. However, Xcode 11.2 has no

Re: OpenBLAS fixed in Xcode 11.2

2019-11-01 Thread Jack Howarth
Is 'sudo port -d test gmp5' failing the t-powm test case for anyone else under Xcode 11.2? Jeremy isn't seeing this failure (which on mymachine is suppressed with -fno-stack-check). Jack On Fri, Nov 1, 2019 at 6:08 AM Christopher Jones wrote: > Hi, > > Good to hear. Howeve

Re: OpenBLAS fixed in Xcode 11.2

2019-11-01 Thread Marcus Calhoun-Lopez
Yes, I am seeing the same error. Like you, it is fixed for me with `-fno-stack-check`. -Marcus > On Nov 1, 2019, at 2:53 PM, Jack Howarth > wrote: > >Is 'sudo port -d test gmp5' failing the t-powm test case for anyone > else under Xcode 11.2? Jeremy isn't seeing this failure (which on