Re: ruby-select problem - Sonoma

[Chris F]

Thanks Bill, Chris - I have created an appropriate .bash_profile (as 
described in the Guide) and everything appears normal now.


I've searched back to the time when Migration Assistant restored my user 
directory. That .bash_profile had several comments made at the time(s) 
that MacPorts install post-flight added and export of an amended PATH, 
but I couldn't find a comment that corresponded to my most  recent 
Macports install (which was shortly after finishing with Migration 
Assistant). However, that absence could have been due to the timing of 
backups. In any case, the restored .bash_profile should have worked just 
fine, so I'm at a loss to know how my  .bash_profile became "corrupted" 
post restoration.


Never mind - all good now. Thanks again.

Chris F





On 20 Oct 2023, at 6:13 pm, Bill 
Cole  wrote:

On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300)
Chris F
is rumored to have said:


On 20/10/23 11:17 am, Chris Jones wrote:



On 19 Oct 2023, at 10:58 pm, Chris F  wrote:



I've just migrated to Sonoma 14.0 via a clean OS install plus Migration 
Assistant and I'm now reinstalling my ports one at a time.

Port ruby31 installed without problems but ruby-select doesn't seem to work/be effective 
- after ruby-select ruby31 runs successfully, command "ruby" still starts the 
OS default ruby 2.6.10

I've checked /opt/local/bin/ruby and it points (correctly?) to ruby3.1.

Any advice would be appreciated.


Did you start a new terminal session after run port select for ruby ?

Yes I did, Chris - I shut terminal down and restarted it a couple of times as 
well.  Chris F

Check the order of directories in your $PATH environment variable. If the 
sub-directories under /usr are listed before those under /opt/local, you will 
use the base install executables instead oF those installed by MacPorts.

Exactly. If once you have started a fresh terminal

  > which ruby

Doesn’t list the macports provided one, the issue is your personal PATH is not 
set correctly.

Chris




--
Bill Cole
b...@scconsult.com  orbillc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Clang 17.0.3 fails to build on Sonoma.

[doa via macports-users]

Attachment available until Nov 19, 2023
This port was recently outdated, so this seems rather strange. Attached is the 
log I received.



Thank you.

Diego Vicioso.

Email… viciosodi...@icloud.com
Click to Download
 
main.log
31.6 MB

Re: ruby-select problem - Sonoma

[Chris Jones]

> On 20 Oct 2023, at 6:13 pm, Bill Cole 
>  wrote:
> 
> On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300)
> Chris F 
> is rumored to have said:
> 
>>> On 20/10/23 11:17 am, Chris Jones wrote:
>>> 
>>> 
 On 19 Oct 2023, at 10:58 pm, Chris F  wrote:
 
 
 
 I've just migrated to Sonoma 14.0 via a clean OS install plus Migration 
 Assistant and I'm now reinstalling my ports one at a time.
 
 Port ruby31 installed without problems but ruby-select doesn't seem to 
 work/be effective - after ruby-select ruby31 runs successfully, command 
 "ruby" still starts the OS default ruby 2.6.10
 
 I've checked /opt/local/bin/ruby and it points (correctly?) to ruby3.1.
 
 Any advice would be appreciated.
 
>>> Did you start a new terminal session after run port select for ruby ?
>> 
>> Yes I did, Chris - I shut terminal down and restarted it a couple of times 
>> as well.  Chris F
> 
> Check the order of directories in your $PATH environment variable. If the 
> sub-directories under /usr are listed before those under /opt/local, you will 
> use the base install executables instead oF those installed by MacPorts.

Exactly. If once you have started a fresh terminal 

 > which ruby

Doesn’t list the macports provided one, the issue is your personal PATH is not 
set correctly.

Chris

> 
> 
> 
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Re: ruby-select problem - Sonoma

[Bill Cole]

On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300)
Chris F 
is rumored to have said:


On 20/10/23 11:17 am, Chris Jones wrote:




On 19 Oct 2023, at 10:58 pm, Chris F  wrote:



I've just migrated to Sonoma 14.0 via a clean OS install plus 
Migration Assistant and I'm now reinstalling my ports one at a time.


Port ruby31 installed without problems but ruby-select doesn't seem 
to work/be effective - after ruby-select ruby31 runs successfully, 
command "ruby" still starts the OS default ruby 2.6.10


I've checked /opt/local/bin/ruby and it points (correctly?) to 
ruby3.1.


Any advice would be appreciated.


Did you start a new terminal session after run port select for ruby ?


Yes I did, Chris - I shut terminal down and restarted it a couple of 
times as well.  Chris F


Check the order of directories in your $PATH environment variable. If 
the sub-directories under /usr are listed before those under /opt/local, 
you will use the base install executables instead oF those installed by 
MacPorts.




--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Re: problem with py311-scipy on M1 MacBook Pro

[Frank Schima]

https://trac.macports.org/ticket/68373
Since it is a dependency of py311-scipy, it will need to be fixed first before 
I can test scipy itself. 


> On Oct 20, 2023, at 11:02 AM, Christopher Jones  
> wrote:
> 
> 
> boost176 not building is a different issue to the one I was talking about, 
> which was the linker issue affecting a number of builds. So no, I don’t 
> necessarily expect Xcode 15.1 to help there.
> 
> Is there a ticket open with your problem with boost ? If not please open one.
> 
> Chris
> 
>> On 20 Oct 2023, at 5:04 pm, Frank Schima  wrote:
>> 
>> Correct. I installed the beta CLT (as I mentioned). 
>> 
>> No joy. boost176 does not build. 
>> 
>> 
>>> On Oct 20, 2023, at 2:26 AM, Christopher Jones  
>>> wrote:
>>> 
>>> 
>>> Do you also have CLT installed and updated to 15.1 as well (if there is a 
>>> version) ?
>>> 
>>> If you still have 15.0 CLT then likely it won’t help.
>>> 
 On 20 Oct 2023, at 1:23 am, Frank Schima  wrote:
 
 py311-scipy still does not build for me with the latest Xcode 15.1 beta 
 and associated CLT. I can only hope I’m doing something wrong. 
 
 I cannot even get past boost176 which is required. I modified my local 
 Portfile to use boost181 (which does build) but py311-scipy still does not 
 build. 
 
 
 
> On Oct 19, 2023, at 1:11 PM, Christopher Jones  
> wrote:
> 
> The fix is in Xcode 15.1, not 15.0.1
> 
> Chris
> 
>> On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
>> 
>> I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried 
>> that?
>> 
>> Jim
>> Seattle, WA
>> 
>>> On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
>>> 
>>> 
>>> 
>>> 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
>> 
> 
 
>>> 
>> 
> 

Re: problem with py311-scipy on M1 MacBook Pro

[Christopher Jones]

boost176 not building is a different issue to the one I was talking about, 
which was the linker issue affecting a number of builds. So no, I don’t 
necessarily expect Xcode 15.1 to help there.

Is there a ticket open with your problem with boost ? If not please open one.

Chris

> On 20 Oct 2023, at 5:04 pm, Frank Schima  wrote:
> 
> Correct. I installed the beta CLT (as I mentioned). 
> 
> No joy. boost176 does not build. 
> 
> 
>> On Oct 20, 2023, at 2:26 AM, Christopher Jones  
>> wrote:
>> 
>> 
>> Do you also have CLT installed and updated to 15.1 as well (if there is a 
>> version) ?
>> 
>> If you still have 15.0 CLT then likely it won’t help.
>> 
>>> On 20 Oct 2023, at 1:23 am, Frank Schima  wrote:
>>> 
>>> py311-scipy still does not build for me with the latest Xcode 15.1 beta and 
>>> associated CLT. I can only hope I’m doing something wrong. 
>>> 
>>> I cannot even get past boost176 which is required. I modified my local 
>>> Portfile to use boost181 (which does build) but py311-scipy still does not 
>>> build. 
>>> 
>>> 
>>> 
 On Oct 19, 2023, at 1:11 PM, Christopher Jones  
 wrote:
 
 The fix is in Xcode 15.1, not 15.0.1
 
 Chris
 
> On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
> 
> I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried that?
> 
> Jim
> Seattle, WA
> 
>> On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
>> 
>> 
>> 
>> 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
> 
 
>>> 
>> 
> 

Re: problem with py311-scipy on M1 MacBook Pro

[Frank Schima]

Correct. I installed the beta CLT (as I mentioned). 

No joy. boost176 does not build. 


> On Oct 20, 2023, at 2:26 AM, Christopher Jones  
> wrote:
> 
> 
> Do you also have CLT installed and updated to 15.1 as well (if there is a 
> version) ?
> 
> If you still have 15.0 CLT then likely it won’t help.
> 
>> On 20 Oct 2023, at 1:23 am, Frank Schima  wrote:
>> 
>> py311-scipy still does not build for me with the latest Xcode 15.1 beta and 
>> associated CLT. I can only hope I’m doing something wrong. 
>> 
>> I cannot even get past boost176 which is required. I modified my local 
>> Portfile to use boost181 (which does build) but py311-scipy still does not 
>> build. 
>> 
>> 
>> 
>>> On Oct 19, 2023, at 1:11 PM, Christopher Jones  
>>> wrote:
>>> 
>>> The fix is in Xcode 15.1, not 15.0.1
>>> 
>>> Chris
>>> 
 On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
 
 I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried that?
 
 Jim
 Seattle, WA
 
> On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
> 
> 
> 
> 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
 
>>> 
>> 
> 

Re: problem with py311-scipy on M1 MacBook Pro

[Christopher Jones]

Do you also have CLT installed and updated to 15.1 as well (if there is a 
version) ?

If you still have 15.0 CLT then likely it won’t help.

> On 20 Oct 2023, at 1:23 am, Frank Schima  wrote:
> 
> py311-scipy still does not build for me with the latest Xcode 15.1 beta and 
> associated CLT. I can only hope I’m doing something wrong. 
> 
> I cannot even get past boost176 which is required. I modified my local 
> Portfile to use boost181 (which does build) but py311-scipy still does not 
> build. 
> 
> 
> 
>> On Oct 19, 2023, at 1:11 PM, Christopher Jones  
>> wrote:
>> 
>> The fix is in Xcode 15.1, not 15.0.1
>> 
>> Chris
>> 
>>> On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
>>> 
>>> I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried that?
>>> 
>>> Jim
>>> Seattle, WA
>>> 
 On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
 
 
 
 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
>>> 
>> 
>