Re: ruby-select problem - Sonoma

[Chris F]

No Ryan, I didn't switch from zsh to bash as any user - after migration 
of users and apps, and my moving from a temporary user to my usual one, 
Terminal came up in bash with the usual zsh entreaty, and I left things 
that way. This was all a few hours before starting a "clean" install of 
MacPorts (from my usual user, using bash).


So the Macports install was from bash, and that session had picked up a 
.bash_profile dated 3 years ago which had no less than 3 
Macports-generated exports of PATH inserting the /opt/local/... stuff. 
And there were three .bash_profile.macports-saved files.


I've looked at the backups of those days and the day following my 
install of Macports there was no sign that anything had modified 
.bash_profile recently, nor was there a telltale 
.bash_profile.macports-saved... for any recent date. So I guess the 
MacPort installer post-flite did not detect the need to add the export 
of a modified PATH. (But then, maybe that part of the installer has been 
modified since I last used it, and won't attempt to add an unnecessary 
export PATH if there are suitable ones already there)


I can't see that it is relevant, but I did have a problem with my second 
port install, ImageMagick, which failed at Python311 because I had 
forgotten to remove /Applications/Macports - see #68494. I fixed that 
and completed the install of ImageMagick before starting on installing 
ruby31 (which installed without problems).




Chris F





On 22/10/23 7:12 am, Ryan Schmidt wrote:

On Oct 20, 2023, at 19:44, Chris F wrote:

I have created an appropriate .bash_profile (as described in the Guide) and 
everything appears normal now.

You are using bash on Sonoma? The default shell is zsh. The MacPorts installer 
is supposed to detect which shell you use and configure the appropriate shell 
startup file but maybe it's not identifying your shell properly. Of course, if 
you changed your shell from zsh to bash after installing MacPorts that would 
explain it.

Re: ruby-select problem - Sonoma

[Ryan Schmidt]

On Oct 20, 2023, at 19:44, Chris F wrote:
> 
> I have created an appropriate .bash_profile (as described in the Guide) and 
> everything appears normal now.

You are using bash on Sonoma? The default shell is zsh. The MacPorts installer 
is supposed to detect which shell you use and configure the appropriate shell 
startup file but maybe it's not identifying your shell properly. Of course, if 
you changed your shell from zsh to bash after installing MacPorts that would 
explain it. 

Help with legacysupport PortGroup for building GIMP for older MacOS's

[Lukas Oberhuber]

Hi,

Currently the legacysupport portgroup doesn't work with the setting
macosx_deployment_target in macports.conf. But would this be possible?

The legacy support package gets its platform indicator from this call in
the Makefile:

PLATFORM=shell $(UNAME) -r | $(SED) -ne 's/\([0-9][0-9]*\)\..*/\1/p'

but this value can be overridden according to BUILDING.txt. If MacPorts set
PLATFORM to the right darwin version, then all should be well, right?

I'd even be happy with a variant that had a variable
`legacy_support_deployment_target 17` which did the trick of setting
PLATFORM.

Anyway, 2 questions:

- Does this sound reasonable? As in, is it likely to work in principle.
- What would be the best way to add it if it was reasonable (say I were to
try).

A bit of background: GIMP requires a huge number of ports to build and
deploy. When any one of those ports breaks, the GIMP build breaks. And some
of them are now breaking for 10.13 (our x86 target OS) when there's no
legacysupport.

For now I'm having to shadow them, which is a painful exercise for me. If
they just worked, that would be amazing.

Thanks,

Lukas (GIMP Macos Maintainer - hence the question)

Re: problem with py311-scipy on M1 MacBook Pro

[Frank Schima]

I was finally able to build boost176 and now I’m stuck trying to build 
py311-scipy. I’m following #68329. 


-Frank

> 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: Clang 17.0.3 fails to build on Sonoma.

[Christopher Jones]

Sending a 31MB log to a mailing list is not a great idea..

Please open a trac ticket.

 https://trac.macports.org/

Chris

> On 20 Oct 2023, at 10:11 pm, doa via macports-users 
>  wrote:
> 
> 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