Re: Install on Ventura 14.2
On 3/2/2023 14:22, Ryan Schmidt wrote: Generating the portindex from scratch takes hours, but just updating a slightly out-of-date portindex with the latest changes shouldn't take that long. Also, the slightly outdated portindex on the public rsync servers should correspond exactly to their slightly outdated collection of ports so no updating should be needed. I was avoiding going into too much detail before, but depending on the exact timing of the power going out and the mirror syncing from the origin, it's possible that the indices for some subset of OS versions could be one update behind the ports tree. But I haven't checked whether that's actually the case. - Josh
Re: Install on Ventura 14.2
On Feb 2, 2023, at 20:58, Joshua Root wrote: > >> 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 >> downloaded the MacPorts install package for Ventura and started it up. >> Twenty minutes later I’m still waiting for “Running Package Scripts …” to >> finish up. >> >> Not being a MacPorts guru of any sort, I’m not sure what I should look at to >> see what’s up. One thing I did find is that a file named .base.tar.ZqfTHz >> is slowly growing larger. This file is in: >> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs >> >> I’m just letting it run for now, but I don’t ever recall this happening in >> other new installs. Any ideas? > The installer's postflight script runs 'port selfupdate' in order to download > the ports tree. It's a reasonably big file at just over 100 MB, so it could > take a while depending on network performance between you and our server. > It's also possible that you had to regenerate part of the PortIndex because > the machine that updates it is currently without power, and that can also be > a lengthy operation. Generating the portindex from scratch takes hours, but just updating a slightly out-of-date portindex with the latest changes shouldn't take that long. Also, the slightly outdated portindex on the public rsync servers should correspond exactly to their slightly outdated collection of ports so no updating should be needed. If the installer takes a long time and you want to know what it is doing you can choose Installer Log from the menu and then change the drop-down menu from showing only errors to showing everything. If your network connection to our primary public server rsync.macports.org (in Germany) is slow you can configure MacPorts to use a closer server from among these choices: https://trac.macports.org/wiki/Mirrors
Re: Install on Ventura 14.2
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 downloaded the MacPorts install package for Ventura and started it up. Twenty minutes later I’m still waiting for “Running Package Scripts …” to finish up. Not being a MacPorts guru of any sort, I’m not sure what I should look at to see what’s up. One thing I did find is that a file named .base.tar.ZqfTHz is slowly growing larger. This file is in: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs I’m just letting it run for now, but I don’t ever recall this happening in other new installs. Any ideas? The installer's postflight script runs 'port selfupdate' in order to download the ports tree. It's a reasonably big file at just over 100 MB, so it could take a while depending on network performance between you and our server. It's also possible that you had to regenerate part of the PortIndex because the machine that updates it is currently without power, and that can also be a lengthy operation. - Josh
Re: Install on Ventura 14.2
Guessing that the file you saw growing might have been a temporary name for a large archive file being downloaded, and for whatever reason (not necessarily on your end) the download was very slow. > On Feb 2, 2023, at 8:54 PM, Jim Secan wrote: > > 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 > >
RE: Install on Ventura 14.2
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
Install on Ventura 14.2
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 downloaded the MacPorts install package for Ventura and started it up. Twenty minutes later I’m still waiting for “Running Package Scripts …” to finish up. Not being a MacPorts guru of any sort, I’m not sure what I should look at to see what’s up. One thing I did find is that a file named .base.tar.ZqfTHz is slowly growing larger. This file is in: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs I’m just letting it run for now, but I don’t ever recall this happening in other new installs. Any ideas? Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109
Re: port install of xemacs fails due to failure to install Xaw3d
On Jan 31, 2023, at 01:21, Kenneth Wolcott wrote: > > I get a different error now when trying to install xemacs: > > *** PANIC *** Configure tests are not working - compiler is broken. > *** PANIC *** Please examine config.log for compilation errors. The preceding line was: :info:configure checking size of short... 0 The config.log says that test failed because: configure:4511: checking size of short configure:4525: /usr/bin/clang -o conftest -pipe -Os -std=gnu89 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch arm64 -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-no_pie -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -Xlinker -arch -Xlinker arm64 -L/opt/local/lib conftest.c 1>&5 configure:4519:11: error: implicitly declaring library function 'exit' with type 'void (int) __attribute__((noreturn))' [-Werror,-Wimplicit-function-declaration] if (!f) exit(1); ^ configure:4519:11: note: include the header or explicitly provide a declaration for 'exit' This is https://trac.macports.org/ticket/61383.
