I’ve got it on an “ancient” 27” iMac running El Cap, and while I did run into
the permissions problem it did seem to go away without any noticeable (so far!)
impact after doing the suggested re-upgrade.
Jim
Seattle, WA
> On Oct 23, 2022, at 12:44 PM, Dave Horsfall wrote:
>
> High Sierra on an
Putting together a new machine (M2Pro Mini, Ventura 14.2) and have hit a snag
installing MacPorts. I’ve not installed Xcode on any of my systems for a
number of years now, I simply install the appropriate CLI package from the
Apple site. In this case, I downloaded and installed v14.2. I then
Ran for almost an hour, but finally did stop successfully. At this point I’m
just kinda curious as to what it was doing that took that long?
Jim
3222 NE 89th St
Seattle, WA 98115
(206) 430-0109
A related question - I install and use only the CLI toolkit for Xcode, not the
entire Xcode package. Does this linker problem also effect use of the CLI
toolkit, or can I safely upgrade to just the toolkit (I’m still on Ventura).
Jim
Seattle, WA
> On 10/07/2023, at 8:03 AM, Chris Jones wrote:
For those of us who are waiting for Apple to fix this problem before moving to
Sonoma, assuming it is Apple’s problem to fix, how will we know when it has
been fixed? Is there a MacPorts bug report that we can periodically check that
will alert us when the fix is in? Or are we going to need to
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 p
; 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 upgraded from a 2011 27” iMac running El Cap to an M2Pro Mini (16MB, external
2TB SSD) earlier this year. Since I don’t do any work requiring a high-end
monitor I use two 27” BenQ 4k monitors, which are working very nicely. Most of
the ports I have installed are simple tools used from the co
I just installed Ventura (13.6.3) on my M2Pro Mini and then the Xcode 15.1 CLI
toolkit. I then did a port update without any odd behaviors. However, when
linking (this is all gfortran stuff using mp-gcc12) I get the following
notifications when the link is completed:
-macosx_version_min has b
Are there negative side-effects to moving this largish subdirectory to an
external drive and connecting via soft link?
Jim
Seattle, WA
I’ve been running Xcode 15 (the CLI tools at any rate) on a Ventura system
since mid-Dec without any apparent problems.
Jim
Seattle, WA
> On 01/26/2024, at 9:29 PM, Sriranga Veeraraghavan via macports-users
> wrote:
>
> Hi,
>
> My primary Mac is currently running Venture (13.6.3) but I have
I’m setting up to use a collection of python codes developed by someone else,
and to run them I’ll need to use some python modules/packages that aren’t
available via MacPorts (nvector, pykml, and stripy). From looking over old
posts it appears that the best way to do this is to install all of t
I’m about to embark on a major mucking-out of my MacPorts installation on an El
Capitan system. I believe that if I make a copy of /opt/local that gives me
everything I need to recover if I find myself with a non-working setup after
this process. Is that right, or are there other directories I
>>> On May 7, 2022, at 14:10, James Secan wrote:
>>>>
>>>> Should have mentioned I’ve already done that as my final fall-back, but
>>>> I’d rather be able to get back to exactly where I was vis-a-vis MacPorts
>>>> if I step on something I shouldn’t hav
I’m a gfortran user and by no stretch of the imagination a guru on how the gcc
compilers are rigged up. I just recently did a full update of my MacPorts
codes, after which I get the following complaint whenever I try to run any
codes compiled and linked prior to the update:
dyld: Library not l
Yes. Appears to be working OK. Had two ports not build (netcdf-fortran and
antlr), both with existing tickets, and neither critical to my routine needs.
Jim
Seattle, WA
> On Jul 31, 2022, at 2:09 AM, Gerben Wierda via macports-users
> wrote:
>
> Has anyone been using Monterey 12.5 yet?
>
>
My Mac Mini server is running Mavericks (long story) and a recent update to
xorg-xorgproto to version 2022.2 (well, since my last full macports update on
the server) has decided it’s too good for Mavericks (10.9) and will only work
on 10.10 or later. I was hoping I could just jettison everythin
Seattle
> On Aug 19, 2022, at 3:00 PM, James wrote:
>
>
>
>> On 20 Aug 2022, at 2:34 am, Jim Secan wrote:
>>
>> My Mac Mini server is running Mavericks (long story) and a recent update to
>> xorg-xorgproto to version 2022.2 (well, since my last full ma
A co-worker sent me a python package that uses the nvector package, which does
not appear to have a MacPorts port. I've not been using pip to install
anything as yet, so I'm not sure how to get a pip-installed package to play
nice with my MacPorts-installed base. Is there any trick here?
Jim
has not been
approved for full disk access, which hangs the entire process.
Is there any way, other than manually putting each and every little binary into
the Full Disk Access list via System Settings, to proactively keep this from
happening?
Jim Secan
Seattle, WA
I put cron into the list many months ago when I first ran into this problem.
That did seem to help for a while (just checked - it's still in the list).
Jim
> On 12/01/2024, at 2:21 PM, Daniel J. Luke wrote:
>
> On Dec 1, 2024, at 12:49 PM, Jim Secan wrote:
>> I run sc
I have just upgraded from sonoma to sequoia (15.5) and to xcode 16.3.0, and I
used the macports migration tool to migrate to the new setup. Everything (so
far) seems to be OK except for gcc12. I have gone through the clean-install
cycle four times now with the same failure mode:
:info:build
22 matches
Mail list logo
