problem with py311-scipy on M1 MacBook Pro

Chris Jones jonesc at hep.phy.cam.ac.uk
Thu Oct 19 15:00:58 UTC 2023



On 19/10/2023 3:59 pm, Chris Jones wrote:
> 
> 
> On 19/10/2023 3:09 pm, Artemio González López via macports-users wrote:
>> I just realized that my problem could exactly be the one reported in 
>> ticket #68329 (py311-scipy @1.10.1_0+gfortran+openblas not building on 
>> Sonoma apple silicon). Indeed, I just spotted the following lines in 
>> my main.log:
>>
>> :info:build ld: duplicate LC_RPATH '/opt/local/lib/libgcc' in 
>> '/opt/local/lib/libopenblas-r1.dylib'
>> :info:build clang: error: linker command failed with exit code 1 (use 
>> -v to see invocation)
>>
>> Short of waiting for Apple to release XCode 15.1, is there any quick 
>> fix for this?
> 
> The canocial fix is to tell the build to use the classic linker option. 
> 'Well behaved' builds will respect the following setting in the Portfile
> 
> configure.ldflags-append  -Wl,-ld_classic
> 
> This has worked for me in a few places, like the root6 port. I did 
> actually try it in py-scipy and there it did not work, and nor did a 
> handful of other tricks I have to get the build to use a certain linker.
> 
> In my experience python based builds are not that well behaved when it 
> comes to things like respecting the macports build flags...
> 
> At this point I am in the 'wait for Xcode 15.1' camp. Usually the first 
> X.1 OS release comes along relatively soon after the initial X.0 
> release, so I would anticipate it relatively soon, most likely.

b.t.w. If it is urgent for you, there is I believe a beta version of 
Xcode 15.1 available you could try. Its not the urgent for me so I am 
just waiting for it to become public..

> 
> cheers Chris


More information about the macports-users mailing list