Re: Foiled Again

2024-10-01 Thread Joshua Root
On 2/10/2024 15:06, Michael Newman wrote: I did my best with the bug report. I had no idea what to put in the comments section. The Description field is for any additional information or analysis that is not present in the log and too long to put in the Summary. If you don't have anything to

Re: Foiled Again

2024-10-01 Thread Ryan Carsten Schmidt
On Oct 2, 2024, at 00:06, Michael Newman wrote: > I did my best with the bug report. Thanks! The ticket URL is https://trac.macports.org/ticket/71012

Re: Foiled Again

2024-10-01 Thread Michael Newman via macports-users
I did my best with the bug report. I had no idea what to put in the comments section. I attached what I hope is a gzip version of the main.log. I’m a bit gun shy about creating a ticket. Last time it turned out not to be a port problem, but something to do with the command line tools; a somethi

Re: Foiled Again

2024-10-01 Thread Joshua Root
Michael Newman wrote: This morning I upgraded my 2019 iMac to Sequoia and then did a port migrate. I think everything went OK, except for the following: The following ports could not be restored: - nbsmtp Failed: Unable to execute target 'activate' for port nbsmtp - see its

Re: Foiled Again

2024-10-01 Thread Ryan Carsten Schmidt
On Oct 1, 2024, at 22:22, Michael Newman wrote: > > :error:build Failed to build nbsmtp: command execution failed The relevant error will be somewhere before this line. If you file a ticket in the issue tracker and attach the main.log file we can try to figure it out.

Foiled Again

2024-10-01 Thread Michael Newman via macports-users
This morning I upgraded my 2019 iMac to Sequoia and then did a port migrate. I think everything went OK, except for the following: The following ports could not be restored: - nbsmtp Failed: Unable to execute target 'activate' for port nbsmtp - see its log for details When I

Re: Reply to Maxim Abalenkov + a pair of sad reflections

2024-10-01 Thread Ralph Seichter via macports-users
* P. Denti via macports-users: > Otherwise inconvenient is the building procedure of gcc and its library: > for around an hour the cpu cores temperature is 100-108 Kelvin, on > account that no fan is present in iMac ... Are you quite sure about that temperature? That would be one hell of an engin

Re: Reply to Maxim Abalenkov + a pair of sad reflections

2024-10-01 Thread Saagar Jha
That’s a rather cold Mac you’ve got there ;) > On Oct 1, 2024, at 09:36, P. Denti via macports-users > wrote: > > Hello Maxim, > thank you very much for indicating the article on Apple Developer. > I am final user of Fortran as a physicist who developed some research > software just in Fortr

Re: runtime failure at the start of a job with gfortran-mp-14

2024-10-01 Thread Dave Allured - NOAA Affiliate via macports-users
Paolo, you mentioned dealing with large matrices. Some modern platforms do not correctly handle extremely large static arrays. This matches your scenario very nicely. Most programs run fine, but nisclue.f is consistently the rogue. This is discussed competently in this post. Scroll down to "You

runtime failure at the start of a job with gfortran-mp-14

2024-10-01 Thread P. Denti via macports-users
Failure starting with OS Sonoma, now with Sequoia. Processor is M3 on iMac. The following message in Sonoma: paolo in ~/Desktop/nisclue240 $ ./nisclue dyld[78445]: dyld cache '(null)' not loaded: syscall to map cache into shared region failed dyld[78445]: Library not loaded: /usr/lib/libSystem.B

Reply to Maxim Abalenkov + a pair of sad reflections

2024-10-01 Thread P. Denti via macports-users
Hello Maxim, thank you very much for indicating the article on Apple Developer. I am final user of Fortran as a physicist who developed some research software just in Fortran. The hardware based on Intel CPU i7 is about nine-years-old, so that I bought a new iMac M3. The new software Sonoma, now

Re: rust port complaint at time of selfupdate

2024-10-01 Thread Kenneth Wolcott
HI Maxim; I guess my ticket search wasn't very thorough :-) Thanks for the link to the existing ticket. Ken W On Tue, Oct 1, 2024 at 8:54 AM Maxim Abalenkov wrote: > > Hello Kenneth et al., > > How are you? There is a ticket. Please see: > > https://trac.macports.org/ticket/70573 > > Thi

Re: rust port complaint at time of selfupdate

2024-10-01 Thread Maxim Abalenkov
Hello Kenneth et al., How are you? There is a ticket. Please see: https://trac.macports.org/ticket/70573 This issue is relevant for me too. But it seems no-one is working on its resolution. Because of it I cannot clean my MacPorts installation for a few weeks now. Thank you! — Best wishes,

Re: rust port complaint at time of selfupdate

2024-10-01 Thread Kenneth Wolcott
Hi; I don't see a ticket for the Rust issue, I guess I will create one. Ken Wolcott On Fri, Sep 20, 2024 at 12:04 PM Christopher Jones via macports-users wrote: > > > You should learn to check trac tickets. Or just check > > https://trac.macports.org/wiki/SequoiaProblems > > for the known pr

Re: runtime failure at the start of a job with gfortran-mp-14

2024-10-01 Thread Maxim Abalenkov
Hello Paolo, How are you? A quick search on the Internet results in the following links: https://stackoverflow.com/questions/74909796/missing-libsystem-b-dylib-file-on-macos https://stackoverflow.com/questions/70549365/why-are-my-system-libraries-and-frameworks-not-visible-in-macos-monterey https

MacPorts 2.10.2 has been released

2024-10-01 Thread Joshua Root
The MacPorts Project is pleased to announce the release of version 2.10.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new ins

Re: runtime failure at the start of a job with gfortran-mp-14

2024-10-01 Thread Saagar Jha
Try rebooting? Being unable to map the shared cache is a sign that something is very wrong. Saagar Jha > On Oct 1, 2024, at 02:16, P. Denti via macports-users > wrote: > > Failure starting with OS Sonoma, now with Sequoia. > Processor is M3 on iMac. > > The following message in Sonoma: > >