Re: Apple Silicon Hardware and MacPorts
My reply wanders OT but may be of interest to the OP. Certainly would have been useful to me 2 weeks ago > On Nov 15, 2023, at 11:04, Alexander Newman via macports-users > wrote: > > Hello All, > > I hope that this is the right place to ask a few questions about Apple > Silicon Hardware and MacPorts - I won’t be offended if this post is ignored. > > I’ve trawled through the FAQs but can’t find any references to Apple Silicon > hardware, which I assume is a good thing. I do realise that a number of > MacPorts ports appear not to be compilable for AS systems, yet. I’ve had no issues with my ports: qt6, bash, qt6-charts, curl, inkscape but I needed the full XCode. Using a macbook pro, M3, sonoma. I used some unix thuggery to rid of SIP, install a root password etc. > I currently have a mid-2010 27” i7 iMac (32 MB RAM) that is running Ventura > on top of OCLP On my 2011 iMac27 (i5) I was unable to get OCLP to work. Could not get past “No Such File” or similar. Only difference I see is a 2T samsung flash (Which makes the machine a pleasure to use.) > (and doing much better than it did natively running High Sierra with the last > security updates). I am using this solution until I can figure out what Apple > Silicon best meets my needs with respect to compiling MacPorts ports (I use > Inkscape, R and Octave, amongst other things). The middle range 14 Core M3 is faster than 6 core i7. I use mythtv and that is on par with the best I’ve seen. > I should also say that an entry-level 2017 21.5” iMac (bottom spec) that one > of my family members acquired is without doubt the worst computer that I’ve > ever used, and that includes 8088/6 DOS machines. Nice screen, but a horror > to do try and do anything on. > > I have been waiting for several years to see what I can replace the 27” iMac > with - the Mac Studio is probably over-powered for my requirements, the Mac > mini M2 needs an external display (finding a decent quality 27”+ display > seems to be difficult here were I live, in Australia, Scortptec have nice 27” and 32” samsung 4K monitors for under AU$300 > and the Apple Studio Display is wickedly expensive), and I wasn’t at all sure > that the M1 iMac would cut it, especially after the experiences with the > ghastly 21.5” iMac. > > The M3 iMac is out now, which may or may not change things, so I am currently > pondering whether I should plump for a specced-out M3 iMac now, wait to see > what sort of mini (M3, M3 Pro?) comes out next year (presumably), or wait for > a lower-end M3 Max Studio (again, next year, and least preferred option). > > Are large-ish MacPorts ports going to compile all right on a 24 MB RAM iMac > with, say, a 2TB SSD, without the hardware throttling? The same with running > R. Do many people on this list use AS machines, and what are their > experiences and advice regarding MacPorts on them? Am I in fact over-thinking > it? Mine is a M3 14core with 36G RAM but is certainly quick, quicker than a 6 core i7. So far the only issue that has beaten me: I cannot install a Case Sensitive file system on sonoma, allthough I have read: Format the disk Case Sensitive then do a timemachine restore. I can’t imagine discent in this forum but let me say in unix-land INSTALL and install are quite different files. James
Sonoma
Pardon being OT to a bunch of clever people who may be able to help … Googling yields little more than a bunch of cretins proclaiming the apple gods have spoken saying DO NOT GO THERE (Darling not even even Hitler can be dregs and scum at the same time, so the irony is not lost on me) I want Sonoma on apple silicon installed with a Case Sensitive file system Easy I thought format as case sensitive then install Install reformats as Case InSensitive then installs Formatting each sub volume ?? Thanks James
OT maybe interesting
I've been a long time macports user. My mid 2011 iMac27 is pegged at High Sierra. I can't build recent mythtv and other woes, after a fail flirt with opencore I installed linux. I asked on the various user forums, but got only well intentioned naive answers. Is fan control done by hardware? If so why: https://github.com/Hipuranyhou/macfand I did a faily heavy shotcut render. At the point I chickened out cpu fan was at minimum (1200 rpm) and core were at 55C Do I need to do sw control of the fans? (Chickened out means I dialed the fans to FSD and temp came down to 40C) James
ImageMagick and rust?
Continuing to install all my MacPort ports on the new M2Pro Mini. I’m watching ImageMagick install, and suddenly I’m seeing that rust is being installed. I was not expecting that. Is ImageMagick being ported to rust? All in all I’m pretty impressed with the new machine. In loading MacPorts on new machines in the past, there’s always one or two port builds where the fans start spinning like a turbofan about to take off. So far I’ve not heard any fan noise from this new machine, and the outer case has been only slightly warm at one point (although it’s warming up again on the rust build). Jim Seattle, WA > On Feb 2, 2023, at 9:12 PM, Joshua Root wrote: > > 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
Thanks for all the info. I had just updated the new machine from macOS 13.1 to 13.2 before the MacPorts install and the download time was pretty normal. I’m now installing all my ports on the new machine and it seems to be moving along at a good clip (over 200 ports). This new Mac Mini is pretty nice (M2Pro base model). When I’ve done this sort of initial install on Intel-CPU Macs the fans start spinning. I’m about 2/3 through the list, and so far not a fan noise to be heard. Jim > On Feb 2, 2023, at 9:12 PM, Joshua Root wrote: > > 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
git sync
I've been building mythtv from John Hoyt's script (it uses macports extensively). I have made a successful build but there we minor isssues on redoing I forgot to sync with git, with rsync update the build failed with a missing file. I followed https://trac.macports.org/wiki/howto/SyncingWithGit uninstalled all ports $ sudo port -fp uninstall installed and ... ws102:sources jam$ ls -l total 0 drwxr-xr-x 2 jam admin 64 25 Dec 23:03 github.com drwxr-xr-x 3 root wheel 96 23 Dec 22:57 rsync.macports.org ws102:sources jam$ git clone https://github.com/macports/macports-ports.git github.com/macports/macports-ports/ Cloning into 'github.com/macports/macports-ports'... remote: Enumerating objects: 1375190, done. remote: Counting objects: 100% (278/278), done. remote: Compressing objects: 100% (143/143), done. remote: Total 1375190 (delta 115), reused 251 (delta 104), pack-reused 1374912 Receiving objects: 100% (1375190/1375190), 326.20 MiB | 2.12 MiB/s, done. Resolving deltas: 100% (788236/788236), done. Updating files: 100% (24358/24358), done. ws102:sources jam$ sudo port sync -v Password: ---> Updating the ports tree Now waits for ever Can anybody guide me please James
High Sierra
Hi many folk here run older macos. Perhaps someone can help me I've a 2011 iMac27 pegged at High Sierra I was trying to build mythtv; all my attempts to create a High Sierra VM failed, and I caused great chaos on my main machine. Naw wurries I'll just reinstall. All the gods snicked and nudged each other! A long time later I have a working High Sierra. Now I'm trying to install macports. I glean that I need xcode 10.4 Which I've got on timemachine, but apple does not list as available. https://developer.apple.com/download/all/ <https://developer.apple.com/download/all/> I cant access old time machine images :-( Apple Support Community suggest restoring THAT image on a usb drive to get the image. I can access the archive directly but with strange ACL permissions. Any suggestion on how to get xcode 10.4 What about CLI tools Thanks James
Re: Error installing Kampose
Ranga, Thanks! I'll give it a try. Jim On Fri, Oct 28, 2022 at 6:15 PM Sriranga Veeraraghavan < srira...@berkeley.edu> wrote: > Hi James, > > I think the problem you are having is that a Ventura package for kompose > has been built yet. The packages available for kompose look like they > range from Darwin 10 (MacOSX 10.6 Snow Leopard, I believe) through Darwin > 21 (Monterey). > > I'm not sure when a Ventura package might be built, but you could try to > build one locally: > > sudo port clean kompose > sudo port -d build kompose > > If kompose builds, then you can try an install, which should install your > locally build kompose instead of trying to fetch it from the server: > > sudo port install kompose > > I tried this on my M1 Mac, but it doesn't work because of some issue with > go and kompose being x86_64 (intel) only. I don't know enough about either > to track it down further. > > Best, > > -ranga > > On Oct 28, 2022, at 14:25, James McManus wrote: > > I had not tried that, but I just did, and am still getting the error > message. > > The first errors in the log 404 errors: > > :msg:archivefetch ---> Fetching archive for kompose > :debug:archivefetch Executing org.macports.archivefetch (kompose) > :debug:archivefetch euid/egid changed to: 0/0 > :debug:archivefetch chowned /opt/local/var/macports/incoming to macports > :debug:archivefetch euid/egid changed to: 503/501 > :info:archivefetch ---> kompose-1.24.0_0.darwin_22.x86_64.tbz2 doesn't > seem to exist in /opt/local/var/macports/incoming/verified > :msg:archivefetch ---> Attempting to fetch > kompose-1.24.0_0.darwin_22.x86_64.tbz2 from > https://packages.macports.org/kompose > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 > :msg:archivefetch ---> Attempting to fetch > kompose-1.24.0_0.darwin_22.x86_64.tbz2 from > https://ywg.ca.packages.macports.org/mirror/macports/packages/kompose > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 > :msg:archivefetch ---> Attempting to fetch > kompose-1.24.0_0.darwin_22.x86_64.tbz2 from > https://mse.uk.packages.macports.org/kompose > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 > :debug:archivefetch Privilege de-escalation not attempted as not running > as root. > > I did use sudo when running the command. > > Thanks > Jim > > On Fri, Oct 28, 2022 at 4:17 PM Mircea Trandafir > wrote: > >> Did you clean compose before retrying? >> >> sudo port clean kompose >> sudo port install kompose >> >> Also, the actual error is in the lines above what you sent. Could you >> check in the log where you see the *first* error message? >> >> -- >> Mircea Trandafir >> Senior researcher >> Rockwool Foundation Research Unit >> Ny Kongensgade 6 >> DK 1472, Copenhagen >> Denmark >> Web: http://www.mirceatrandafir.com >> >> On Oct 28, 2022, at 7:23 PM, James McManus wrote: >> >> I followed the instructions at: https://trac.macports.org/wiki/Migration >> and did the migration. I've been able to use macPorts to install ports such >> as wget and ffmpeg, which were not previously installed on my mac, so it >> looks like macPorts is working. >> >> However, I am still not able to install Kompose. I'm still getting the >> not a git repository error message: >> >> :info:build Executing: cd >> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ >> github.com/kubernetes/kompose" && make -j8 -w bin >> :debug:build system: cd >> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ >> github.com/kubernetes/kompose" && make -j8 -w bin >> :info:build fatal: not a git repository (or any of the parent >> directories): .git >> :info:build make: Entering directory >> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ >> github.com/kubernetes/kompose' >> >> The directory path listed above does exist. >> >> The I'm also getting a build error: >> >> :info:build ../../../../pkg/mod/ >> golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3: >> too many errors >> :info:build make: *** [bin] Error 2 >> :info:build make: Leaving directory >> `/opt/local/var/macpo
Re: Error installing Kampose
I had not tried that, but I just did, and am still getting the error
message.
The first errors in the log 404 errors:
:msg:archivefetch ---> Fetching archive for kompose
:debug:archivefetch Executing org.macports.archivefetch (kompose)
:debug:archivefetch euid/egid changed to: 0/0
:debug:archivefetch chowned /opt/local/var/macports/incoming to macports
:debug:archivefetch euid/egid changed to: 503/501
:info:archivefetch ---> kompose-1.24.0_0.darwin_22.x86_64.tbz2 doesn't
seem to exist in /opt/local/var/macports/incoming/verified
:msg:archivefetch ---> Attempting to fetch
kompose-1.24.0_0.darwin_22.x86_64.tbz2 from
https://packages.macports.org/kompose
:debug:archivefetch Fetching archive failed: The requested URL returned
error: 404
:msg:archivefetch ---> Attempting to fetch
kompose-1.24.0_0.darwin_22.x86_64.tbz2 from
https://ywg.ca.packages.macports.org/mirror/macports/packages/kompose
:debug:archivefetch Fetching archive failed: The requested URL returned
error: 404
:msg:archivefetch ---> Attempting to fetch
kompose-1.24.0_0.darwin_22.x86_64.tbz2 from
https://mse.uk.packages.macports.org/kompose
:debug:archivefetch Fetching archive failed: The requested URL returned
error: 404
:debug:archivefetch Privilege de-escalation not attempted as not running as
root.
I did use sudo when running the command.
Thanks
Jim
On Fri, Oct 28, 2022 at 4:17 PM Mircea Trandafir wrote:
> Did you clean compose before retrying?
>
> sudo port clean kompose
> sudo port install kompose
>
> Also, the actual error is in the lines above what you sent. Could you
> check in the log where you see the *first* error message?
>
> --
> Mircea Trandafir
> Senior researcher
> Rockwool Foundation Research Unit
> Ny Kongensgade 6
> DK 1472, Copenhagen
> Denmark
> Web: http://www.mirceatrandafir.com
>
> On Oct 28, 2022, at 7:23 PM, James McManus wrote:
>
> I followed the instructions at: https://trac.macports.org/wiki/Migration
> and did the migration. I've been able to use macPorts to install ports such
> as wget and ffmpeg, which were not previously installed on my mac, so it
> looks like macPorts is working.
>
> However, I am still not able to install Kompose. I'm still getting the not
> a git repository error message:
>
> :info:build Executing: cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
> github.com/kubernetes/kompose" && make -j8 -w bin
> :debug:build system: cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
> github.com/kubernetes/kompose" && make -j8 -w bin
> :info:build fatal: not a git repository (or any of the parent
> directories): .git
> :info:build make: Entering directory
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
> github.com/kubernetes/kompose'
>
> The directory path listed above does exist.
>
> The I'm also getting a build error:
>
> :info:build ../../../../pkg/mod/
> golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3:
> too many errors
> :info:build make: *** [bin] Error 2
> :info:build make: Leaving directory
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
> github.com/kubernetes/kompose'
> :info:build Command failed: cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
> github.com/kubernetes/kompose" && make -j8 -w bin
> :info:build Exit code: 2
> :error:build Failed to build kompose: command execution failed
> :debug:build Error code: CHILDSTATUS 13579 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec -callback
> portprogress::target_progress_callback build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
>
> :debug:build "$procedure $targetname"
>
> Jim
>
> On Thu, Oct 27, 2022 at 1:23 PM Chris Jones
> wrote:
>
>>
>>
>> On 27 Oct 2022, at 4:45 pm, James McManus wrote:
>>
>>
>> I just upgraded the OS and then reinstall MacPorts.
>>
>>
>> So you did not remove all your ports and reinstall them, as per the
>> migration
Re: Error installing Kampose
I followed the instructions at: https://trac.macports.org/wiki/Migration
and did the migration. I've been able to use macPorts to install ports such
as wget and ffmpeg, which were not previously installed on my mac, so it
looks like macPorts is working.
However, I am still not able to install Kompose. I'm still getting the not
a git repository error message:
:info:build Executing: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose" && make -j8 -w bin
:debug:build system: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose" && make -j8 -w bin
:info:build fatal: not a git repository (or any of the parent directories):
.git
:info:build make: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose'
The directory path listed above does exist.
The I'm also getting a build error:
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3:
too many errors
:info:build make: *** [bin] Error 2
:info:build make: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose'
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose" && make -j8 -w bin
:info:build Exit code: 2
:error:build Failed to build kompose: command execution failed
:debug:build Error code: CHILDSTATUS 13579 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback
build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
Jim
On Thu, Oct 27, 2022 at 1:23 PM Chris Jones
wrote:
>
>
> On 27 Oct 2022, at 4:45 pm, James McManus wrote:
>
>
> I just upgraded the OS and then reinstall MacPorts.
>
>
> So you did not remove all your ports and reinstall them, as per the
> migration instructions ?
>
> https://trac.macports.org/wiki/Migration
>
> If not, please follow those instructions correctly, to see if it address
> your issues. If not report back.
>
> Chris
>
>
> On Thu, Oct 27, 2022 at 9:28 AM Lenore Horner
> wrote:
>
>> Did you follow the migration instructions or just upgrade the OS and then
>> reinstall MacPorts?
>>
>> On Oct 27, 2022, at 08:56, James McManus wrote:
>>
>> I'm trying to install Kampose using MacPorts on my MacBook Pro. I
>> recently updated maxOS to Ventura. This required me to reinstall MacPorts.
>> After installing MacPorts I also updated outdated packages using the
>> following command:
>>
>> *sudo port upgrade outdated*
>>
>>
>> When I tried to install Kompose using this command:
>>
>> sudo port install kompose
>>
>> I got the following error:
>>
>> Error: Failed to build kompose: command execution failed
>> Error: See
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/main.log
>> for details.
>> Error: Follow https://guide.macports.org/#project.tickets if you believe
>> there is a bug.
>>
>> Error: Processing of port kompose failed
>>
>> Looking at the log file the following errors occurred:
>>
>> :info:build Executing: cd
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
>> github.com/kubernetes/kompose" && make -j8 -w bin
>> :debug:build system: cd
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
>> github.com/kubernetes/kompose" && make -j8 -w bin
>> :info:build fatal: not a git repository (or any of the parent
>> directories): .git
>> :info:build make: Entering directory
>> `/opt/local/var/macports/build/_op
Re: Error installing Kampose
I just upgraded the OS and then reinstall MacPorts. On Thu, Oct 27, 2022 at 9:28 AM Lenore Horner wrote: > Did you follow the migration instructions or just upgrade the OS and then > reinstall MacPorts? > > On Oct 27, 2022, at 08:56, James McManus wrote: > > I'm trying to install Kampose using MacPorts on my MacBook Pro. I recently > updated maxOS to Ventura. This required me to reinstall MacPorts. After > installing MacPorts I also updated outdated packages using the following > command: > > *sudo port upgrade outdated* > > > When I tried to install Kompose using this command: > > sudo port install kompose > > I got the following error: > > Error: Failed to build kompose: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > > Error: Processing of port kompose failed > > Looking at the log file the following errors occurred: > > :info:build Executing: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ > github.com/kubernetes/kompose" && make -j8 -w bin > :debug:build system: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ > github.com/kubernetes/kompose" && make -j8 -w bin > :info:build fatal: not a git repository (or any of the parent > directories): .git > :info:build make: Entering directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ > github.com/kubernetes/kompose' > :info:build CGO_ENABLED=0 GO111MODULE=on go build -ldflags="-w -s -X > github.com/kubernetes/kompose/pkg/version.GITCOMMIT=" -o kompose main.go > :info:build # golang.org/x/sys/unix > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/syscall_darwin.1_13.go:29:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.1_13.go:27:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.1_13.go:40:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:28:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:43:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:59:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:75:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:90:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:105:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3: > //go:linkname must refer to declared function or variable > :info:build ../../../../pkg/mod/ > golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3: > too many errors > :info:build make: *** [bin] Error 2 > :info:build make: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ > github.com/kubernetes/kompose' > > :info:build Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/ > github.com/kubernetes/kompose" && make -j8 -w bin > :info:build Exit code: 2 > :error:build Failed to build kompose: command execution failed > :debug:build
Error installing Kampose
I'm trying to install Kampose using MacPorts on my MacBook Pro. I recently
updated maxOS to Ventura. This required me to reinstall MacPorts. After
installing MacPorts I also updated outdated packages using the following
command:
*sudo port upgrade outdated*
When I tried to install Kompose using this command:
sudo port install kompose
I got the following error:
Error: Failed to build kompose: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe
there is a bug.
Error: Processing of port kompose failed
Looking at the log file the following errors occurred:
:info:build Executing: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose" && make -j8 -w bin
:debug:build system: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose" && make -j8 -w bin
:info:build fatal: not a git repository (or any of the parent directories):
.git
:info:build make: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose'
:info:build CGO_ENABLED=0 GO111MODULE=on go build -ldflags="-w -s -X
github.com/kubernetes/kompose/pkg/version.GITCOMMIT=" -o kompose main.go
:info:build # golang.org/x/sys/unix
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/syscall_darwin.1_13.go:29:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.1_13.go:27:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.1_13.go:40:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:28:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:43:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:59:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:75:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:90:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:105:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3:
//go:linkname must refer to declared function or variable
:info:build ../../../../pkg/mod/
golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3:
too many errors
:info:build make: *** [bin] Error 2
:info:build make: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose'
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/
github.com/kubernetes/kompose" && make -j8 -w bin
:info:build Exit code: 2
:error:build Failed to build kompose: command execution failed
:debug:build Error code: CHILDSTATUS 4875 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback
build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
:error:build See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/main.log
for details.
Jim
Catelina xcode
Hi slightly OT for macports but definitly onT. :) My wife’s machine is Catelina (and Ends at Big Sur). It has, and I/She uses lots of ports and IIRC we have used Qt before, but when I try to build something I get the XCode license dialog. No worries, accept. "Something is wrong see the log” The something wrong turn out to be Certificate Expired. After spelunking I got an Xcode for catelina. Install. "Something is wrong see the log” Again Certificate Expired. OK I’m starting to fumble. Setting her date back for a build is like a lead balloon. A VM with no internet sccess ? Any body able to guide me please? James
update and gimp
I installed Gimp, but had no joy with 'open with ...' Ryan explained how the system worked. Eventually I un-installed the macports version, installed Gimp's dmg and for ages everything 'just worked' I'm a believer in 'if it aint broke, don't fix it'. Time passed and all was well. Eventually I was persuaded to selfupdate and update outdated. My gimp dmg was removed !! the macports version was re-installed !! together with the broken 'open with ...' behavior. Can anyone tell me what I must have done to achive this, certainly nothing deliberate. A comment for Ricardo, I spend 1/2 my day working at NOT the keyboard/console of TheMachineImWorkingOn so X11 is important. Remote Desktop is plain horrid, nomachine is better but straight X11 is by far the nicest. James
Re: update
> On 15 Sep 2022, at 4:14 pm, Ryan Schmidt wrote: > > Please keep replies on the mailing list by using Reply All. > > On Sep 15, 2022, at 01:15, James wrote: > >> On 15 Sep 2022, at 12:30 pm, Ryan Schmidt wrote: >> >>> On Sep 12, 2022, at 16:56, James wrote: >>>> >>>> ... >>>> checking for xcode-select... /usr/bin/xcode-select >>>> checking macOS version... 12.4 >>>> checking Xcode location... /Applications/Xcode.app/Contents/Developer >>>> checking Xcode version... 13.4.1 >>>> checking whether the C compiler works... no >>>> configure: error: in >>>> `/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base': >>>> configure: error: C compiler cannot create executables >>>> See `config.log' for more details >>> >>> We'll need to see what's in the config.log to be able to diagnose this. I >>> expect it'll be in the directory >>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base. >> >> I've looked but being a bear of little brain ... little sticks out except >> -qversion not --version > > The errors about -qversion are not relevant. A configure script's purpose is > to determine your system's capabilities for example by trying various > commands with various arguments and seeing what works and what doesn't. Here, > the configure script learned that your compiler doesn't accept the -qversion > argument, which is fine and normal. > > The relevant error from the log about why the compiler could not create > executables is: > > ld: library not found for -lSystem > > On macOS, the System library is the C library, a rather essential library for > any software written in C. There's no way it can't be there; nothing would > work if it weren't. In macOS 12 none of the libraries that ship with macOS > are present in the filesystem anymore but they are in the dynamic library > cache and stubs are in the SDK (so you won't see it if you look in /usr/lib > and that's ok). > > I'm not really sure why you would be getting this error. There are many hits > for this error on Google but most relate to Fortran which is not applicable > here. Make sure you've installed the version of the command line tools that > matches your Xcode version as closely as possible. There was no 13.4.1 > version of the CLT so you'd want the 13.4 version. "xcode-select --install" > can sometimes lie about whether the CLT are installed, so the simplest way to > make sure they're installed would be to just redownload the installer and run > it again. > > https://developer.apple.com/download/all/?q=command%20line%20tools%2013.4 I'd not have thought of trying that, but it worked, thanks (Ive been using macports on this machine, without any changes or updates for a year or so) James
update
I believe 'if it aint broke, don't fix it'. After installing QT6, which works, I was nagged to selfupdate which failed. Can anyone hep me to understand, thanks. ... checking for xcode-select... /usr/bin/xcode-select checking macOS version... 12.4 checking Xcode location... /Applications/Xcode.app/Contents/Developer checking Xcode version... 13.4.1 checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base': configure: error: C compiler cannot create executables See `config.log' for more details Command failed: CC=/usr/bin/cc SDKROOT=/Library/Developer/CommandLineTools/SDKs/MacOSX12.0.sdk ./configure --prefix=/opt/local --with-install-user=root --with-install-group=wheel --with-directory-mode=0755 --enable-readline && SDKROOT=/Library/Developer/CommandLineTools/SDKs/MacOSX12.0.sdk make SELFUPDATING=1 && make install SELFUPDATING=1 Exit code: 77 Error: Error installing new MacPorts base: command execution failed ... I can also compile an arbituary program which does work! [plasma] /Users/jam [511]% /usr/bin/cc fiforead.c [plasma] /Users/jam [512]% James
Re: gimp open with
On May 31, 2022, at 18:40, James wrote:
>
>> On 1 Jun 2022, at 7:19 am, Ryan Schmidt wrote:
>>
>>> I have not used gimp often enough to be familiar with the option you're
>>> referring to so I'm not sure I can advise you properly. However it may be
>>> significant that gimp can be compiled either in x11 mode or with a native
>>> macOS user interface, which we refer to as quartz mode. It may be the case
>>> that the disk image distributed by the developers of gimp was compiled in
>>> quartz mode, while the default in MacPorts is x11 mode, which may account
>>> for some of the discrepancies you're experiencing. You can install gimp in
>>> quartz mode with MacPorts by using the +quartz variant, however if you wish
>>> to switch from x11 mode to quartz mode you should decide to do so for all
>>> of your installed ports at once, and it is recommended to uninstall all
>>> ports, edit variant.conf to add +quartz, and then reinstall the ports you
>>> want. That way, ports that have quartz variants that require some of their
>>> dependencies to have quartz variants enabled will get built correctly.
>>>
>>> In MacPorts gimp in x11 mode, I just tried saving a file, and then I tried
>>> save-as with the same filename, and it prompted me about whether I wanted
>>> to overwrite the existing file. If this is not the capability you're
>>> seeking, please clarify.
>>
>> We just had a massive lightning strike that took out lots (apple tv,
>> ethernet on my mac, printer, nucs, blackmagic boxes, usb keyboard ...) so I
>> might be confused in my overloaded state :-) The real issue is the open
>> event.
>>
>> I can't find how to remove a single port, google has oodles to say on how to
>> remove ALL ports, but nothing about 1.
>
> To uninstall a port named foo and a port named bar, "sudo port uninstall foo
> bar".
>
> You can also specify pseudo portnames like "installed" or "inactive" ("sudo
> port uninstall inactive").
>
>
>> I will compile gimp with +quartz but most of my ports do use X11 so I don't
>> want quartz versions. SSH from other machines!
>> nomachine and remote desktop from other macs are cludgy.
>
> I don't think you will have success attempting to install gimp2 with +quartz
> while retaining the +x11 variant of other ports. In particular, gimp2 and
> gtk2 will need to be installed with the same variant (either +quartz or
> +x11), and whatever variant you install gtk2 with will need to be set on all
> other ports that use gtk2. That's why we suggest to decide which variant you
> want before installing any ports (or uninstall all ports and reinstall if you
> change your mind).
>
> If you want to use some ports with +x11 and some with +quartz, one
> oft-suggested idea is to keep your main MacPorts installation at /opt/local
> using +x11 (so that you can receive binaries from us) and build a second
> MacPorts installation from source in a different prefix (/opt/quartz, say)
> and configure that one with +quartz.
>
> Ideally we would reengineer this situation so that quartz and x11 things
> could coexist. It's been a long-term wish that nobody worked on yet, though
> Chris says he will work on it.
Ryan thanks!
It's all confusing:
On my macbook (monterey) gimp (x11)(I can see xquartz open) works as expected.
On my iMac (high sierra : end of line) it does not.
rather than playing with all my ports I download gimp.dmg from gimp, which
works properly.
James
gimp open with
The gimp.dmg version behaves as expected. The macports version does not File->save->Overwrite option is missing Finder->open with gimp Opens gimp without opening the picture. (I've not investigated, but it smells of cli phreaks ie gimp %f is not picking up the file name) Is there a simple fix or do I need the original dmg? James
Re: Quick Question
Thanks, I’ll check those other items out. Jim Seattle, WA > On May 7, 2022, at 11:24 AM, chilli.names...@gmail.com wrote: > > Sorry I did not address your question. Though I've never tried that method, > my understanding is that everything MacPorts is in /opt/local owned by > root:wheel and 755, so I have always assumed, for at least a decade now, that > what you intend should just work, because I've had those thoughts before as > well, I just prefer to watch code build for days rather than copy a folder > for a few minutes. > > I always backup macports.conf separately, along with .bash_profile (not > really part of MacPorts but sourcing it keeps $PATHs how I want them). > > Also, for the system proper, I install everything that is not required to be > installed in /Applications into ~/Applications, so when migrating I just copy > over my user folder and then nearly all my applications are already installed. > > Which reminds me, you may have some MacPorts application builds in > /Applications/MacPorts > > > > >> 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 have. >> >> Jim >> Seattle, WA >> >>> On May 7, 2022, at 11:00 AM, chilli.names...@gmail.com wrote: >>> >>> May want to save a copy of output of >>> >>> port list requested >>> >>> to make it easy to restore if it all goes South. When I'm migrating, I take >>> that list and turn it into an install script. >>> >>>>> On May 7, 2022, at 13:55, Jim Secan wrote: >>>> >>>> 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 >>>> should backup as well? >>>> >>>> Jim >>>> Seattle, WA >>>> >>
Re: Quick Question
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 have. Jim Seattle, WA > On May 7, 2022, at 11:00 AM, chilli.names...@gmail.com wrote: > > May want to save a copy of output of > > port list requested > > to make it easy to restore if it all goes South. When I'm migrating, I take > that list and turn it into an install script. > >> On May 7, 2022, at 13:55, Jim Secan wrote: >> >> 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 >> should backup as well? >> >> Jim >> Seattle, WA >>
Re: High Sierra Install
> On 2 May 2022, at 7:43 am, James wrote: > > Hi > I've had a torrid time. > > I've got an iMac stuck at High Sierra. > > I tried to build mythtv using John Hoyt's script that gets lots from macports. > It failed. > > Lots of (help from Craig) clean, reset, some failed eg inkscape, gimp but > some eg curl qt5 worked. > > I then totally removed macports as per the wiki. > I reinstalled and the re-install is stuck at "Running package scripts" > > I can limp back to a timemachine backup or continue with major surgery, This > machine is stuck ar High Sierra so I need a fix for the rest of this > machine's life. > I put in a 2T flash so the machine is nice to use! An hour later - a lil green tick :-) Then tried to install inkscape - sucess James
High Sierra Install
Hi I've had a torrid time. I've got an iMac stuck at High Sierra. I tried to build mythtv using John Hoyt's script that gets lots from macports. It failed. Lots of (help from Craig) clean, reset, some failed eg inkscape, gimp but some eg curl qt5 worked. I then totally removed macports as per the wiki. I reinstalled and the re-install is stuck at "Running package scripts" I can limp back to a timemachine backup or continue with major surgery, This machine is stuck ar High Sierra so I need a fix for the rest of this machine's life. I put in a 2T flash so the machine is nice to use! James
Re: Somewhat off topic - keeping older Macs running
> On 25 Apr 2022, at 1:44 pm, Dave Horsfall wrote: > > On Mon, 25 Apr 2022, James wrote: > >> I too have old macs that cant be updated. I just keep a time machine >> backup and if ever I get hacked a quick restore will fix. For 10 years >> I've had no issues !! > > Your "old macs" are not protected by a firewall? One day... > > As for backups, consider malware that will not trigger until well and > truly embedded into your backups; not much use then, are they? Dave methinks there is lots of hysteria in the arena I have no firewall on my modem and no firewall on any of my machines. Yet the world is full of stories about exploits! Most of those are windows exploits! Lets consider firewalls: By RFC no router on the internet may route a private IP. So *every* router between you and bad guys is broken! A firewall allows ESTABLISHED,RELATED traffic back, so if you've got a bad machine then bad guys can get to that machine and from there to your macs. If you have a compromised machine then it is a target. A decade ago one of the anti-virus companies offered $10 000 and a Sony Viao to first person to hack their honeypots. The windows honeypot was hacked in under an hour, the mac in a week (a flaw in safari) and the linux 'pot has never been hacked. They ascribed this to being unkewl to hack linux. Nonsense you'd be a hero for exposing a flaw (as has happened a couple of times.) If you enjoy playing then by all means, if not then enjoy an icecream, except if you have windows machines on your network forget the icecream. I guess IPV6 will change the landscape somewhat. The subtle comment about ring 0: linux and mac work in a way that is very limited, what disk?, whereas widows you are not allowed, here is $100, well ok. Query: heresay not allowed, who has ever had a mac hacked? James
Re: Somewhat off topic - keeping older Macs running
> On 25 Apr 2022, at 2:18 am, bunk3m wrote: > > Hi all, > > Now and again, I read of people on the list keeping older Macs running using > Macports. > > I have a perfectly functioning iMac which can't update past 10.13.6, yet > there are nearly monthly security issues. > > I have been running Ubuntu on an older Macbook Pro with a C2D processor but > the change to Ubuntu Linux might be too much of a challenge for my wife on > the iMac. > > Is there a discussion forum or website that people recommend where there are > suggestions on how to keep older Mac hardware running and secure? I've done > some Googling but I can't seem to find anything. (It is probably an issue of > not knowing the right search terms) > > Or are there recommendations on how to use Macports with these older devices > to keep them operating securely? I'm always concerned that the older > unsecure software in the /System and /Library folders are used as default > instead of the updated Macport versions. I too have old macs that cant be updated. I just keep a time machine backup and if ever I get hacked a quick restore will fix. For 10 years I've had no issues !! Except for apple silly's (sic) there is little to worry about (ring 0 et al). I expect Bad Guys would put their efforts into modern exploits not ones from 'olden days'. My only issue with perfectly functioning iMacs is that my wife want's lightroom. and photoshop (which demand the 'latest' os) whereas I prefer gimp. At least thee and me are free of apple's incessant nagging :-) BTW if you are not using flash do your self a mighty favour (mac fancontrol) Another point if anyone reading wants opinion: (How it pains me to not say VirtualBox!) running a VM under parallels is probably nicer than native hardware for linux (pad gestures and touch-feel, bluetooth, heat come to mind) and speed is quite excellant eg M2 speed is 1800 MB/s on my macbook) James
Re: curl and openSSL
Thanks. I’ll pass that along to the person from NASA who contacted me. Jim > On Apr 13, 2022, at 1:07 AM, Clemens Lang wrote: > > On Tue, Apr 12, 2022 at 02:16:08PM -0700, James Secan wrote: >> It’s a US Gov’t site (NASA): cddis.nasa.gov. I’m accessing data on >> their Space Geodesy Data archive, pulling files from directory >> archive/gnss/products/ionex. I filed an initial complaint with them >> yesterday before I knew in detail what was going on and had a response >> asking for more info this morning. I’ve sent them everything I know, >> but have heard nothing back. That was just this morning, so it’s too >> soon to be getting antsy about a response from them. > > Their server does not include a RFC5746 renegotiation_info extension in > its ServerHello message. Modern TLS clients such as OpenSSL 3 consider > this insecure. See https://datatracker.ietf.org/doc/html/rfc5746 for > more details. > > -- > Clemens
Re: curl and openSSL
It’s a US Gov’t site (NASA): cddis.nasa.gov. I’m accessing data on their Space Geodesy Data archive, pulling files from directory archive/gnss/products/ionex. I filed an initial complaint with them yesterday before I knew in detail what was going on and had a response asking for more info this morning. I’ve sent them everything I know, but have heard nothing back. That was just this morning, so it’s too soon to be getting antsy about a response from them. Jim > On Apr 12, 2022, at 1:19 PM, Clemens Lang wrote: > > Hi, > > On Tue, Apr 12, 2022 at 09:17:03AM -0700, James Secan wrote: >> I switched from using the macOS-supplied curl to MacPorts curl >> recently, and one of my download scripts which uses curl immediately >> stopped working. The error message from curl was: >> >> curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation >> disabled >> >> From some googling it sounds like this is a problem on the server end >> and not on my end. Am I reading this right (I am NOT any kind of >> expert on SSL)? > > Yes, mostly. Unsafe legacy renegotiation is a mechanism that is > vulnerable to man in the middle attacks. Can you share which server your > script was talking to, so I could take a closer look? > > >> I’ve switched back to the macOS version of curl for now, but I may try >> downloading a MacPorts version of curl that doesn’t use openSSL as >> suggested in a StackExchange post I found. > > This is a message caused by OpenSSL 3.x, so not using OpenSSL will "fix" > the issue, but leave you vulnerably to the man-in-the-middle vulnerable > renegotiation. > > -- > Clemens
curl and openSSL
I switched from using the macOS-supplied curl to MacPorts curl recently, and one of my download scripts which uses curl immediately stopped working. The error message from curl was: curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled From some googling it sounds like this is a problem on the server end and not on my end. Am I reading this right (I am NOT any kind of expert on SSL)? I’ve switched back to the macOS version of curl for now, but I may try downloading a MacPorts version of curl that doesn’t use openSSL as suggested in a StackExchange post I found. Jim Seattle, WA
Re: PHP8 and Apple Apache
Thanks. I suspected as much, but wanted to ask first. Jim > On Apr 8, 2022, at 3:58 PM, Ryan Schmidt wrote: > > On Apr 8, 2022, at 17:40, James Secan wrote: > >> I’m just getting started on php, and started by putting php81 on a Big Sur >> system. While looking at how to tweak the configuration on this setup, I >> find that I need libphp8.0.so. The Apple setup for apache2 has libphp7.so, >> but nothing for 8. This was not part of the Macports-installed php81 >> package, so where does this come from? > > The php81 port provides only the PHP 8.1 command line. If you want other PHP > Server APIs (SAPIs) install the corresponding other ports. For example, the > PHP 8.1 Apache 2 handler is in the php81-apache2handler port. Installing this > will also install the MacPorts apache2 port, if you don't already have it > installed. It will not use an existing Apple install of Apache. >
PHP8 and Apple Apache
I’m just getting started on php, and started by putting php81 on a Big Sur system. While looking at how to tweak the configuration on this setup, I find that I need libphp8.0.so. The Apple setup for apache2 has libphp7.so, but nothing for 8. This was not part of the Macports-installed php81 package, so where does this come from? Jim Seattle, WA
Re: Python
I just recently upgraded one of my machines to macOS 12.3. It has Python 3.8.9 installed in /usr/bin as python3. Being a backsliding miscreant, I have the MacPorts Python 2.7 installed as my default (and 3.10 for testing). Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 17, 2022, at 9:57 PM, Ryan Schmidt wrote: > > Sure. But Tom specifically asked for a Python replacement for macOS 12.3. > What happened in macOS 12.3 is that Apple removed /usr/bin/python which was > Python 2.7 so I assumed that's what Tom was asking about. If Tom wants to use > Python 3, I assume macOS still provides a version of that in > /usr/bin/python3. Or he can install any of the python3x ports as you > mentioned.
Re: port diagnose and xcode
It is a macOS alias. I use soft links a lot, but only for items that I’m accessing when working in a Unix shell. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 13, 2022, at 1:46 PM, xpl...@wak.co.nz wrote: > > I forgot to ad, the reason, at a unix level, the Finder alias just just > another boring file, not the intended alias. This is similar to how Windows > shortcuts look on Macs, where they come through as a .lnk file that the Mac > doesn’t understand. > > -- > Richard Smith > xpl...@wak.co.nz > > > > >> On 14/03/2022, at 09:43, xpl...@wak.co.nz wrote: >> >> Is it a Mac Alias, or a unix ln ? (i.e. the former is created with a >> drag-n-drop of the App holding down the Command & Option keys, while the >> former is created with the command ln -s /path/to/app lnfile, and that is a >> lowercase L, not an uppercase i). MacPorts will work better with the latter >> ln alias, not the former finder created alias. >> >> -- >> Richard Smith >> xpl...@wak.co.nz >> >> >> >> >>> On 14/03/2022, at 06:41, James Secan wrote: >>> >>> I do have the full Xcode package installed (8.2.1) on the El Capitan >>> system, although I have it as an alias in the Applications directory (on a >>> smallish SSD) linking to the actual Xcode files on an internal HD because >>> it requires a lot of disk real estate and I never use Xcode. Would that >>> confuse port diagnose? (I just checked, and if I click on the Xcode alias >>> it works just as one would expect, so the alias linkage is OK.) >>> >>> Jim >>> 3222 NE 89th St >>> Seattle, WA 98115 >>> (206) 430-0109 >>> >>>> On Mar 12, 2022, at 6:42 PM, Ryan Schmidt wrote: >>>> >>>> On Mar 10, 2022, at 18:40, James Secan wrote: >>>> >>>>> In working my way through my recent “phantom ports” issue I ran the >>>>> command “port diagnose” and was more than a bit surprised by the output >>>>> line: >>>>> >>>>> Error: currently installed version of Xcode, none, is not supported by >>>>> MacPorts. >>>>> >>>>> followed by a list of the version supported under my version of macOS (El >>>>> Capitan, in this case). Where is port getting this information? I have >>>>> Xcode 8.2.0 installed, and none of my attempts to install ports have run >>>>> into any trouble related to Xcode not being installed. I ran "pkgutil -v >>>>> --pkg-info=com.apple.pkg.CLTools_Executables” which shows that I have >>>>> 8.2.0 installed, and the appropriate MacOSX.sdk files are in >>>>> /Library/Developer/CommandLineTools/SDKs. I also tried this on my test >>>>> Catalina system, with the same result. >>>>> >>>>> Is something wrong with my ports setup? >>>> >>>> >>>> Both com.apple.pkg.CLTools_Executables and >>>> /Library/Developer/CommandLineTools/SDKs are related to the Xcode command >>>> line tools, which are separate from Xcode. So I guess you have the Xcode >>>> command line tools installed but do not have Xcode installed. For many >>>> ports, this is fine. For those where it is not, they should tell you to >>>> install Xcode. >>>> >>> >> >
Re: port diagnose and xcode
I do have the full Xcode package installed (8.2.1) on the El Capitan system, although I have it as an alias in the Applications directory (on a smallish SSD) linking to the actual Xcode files on an internal HD because it requires a lot of disk real estate and I never use Xcode. Would that confuse port diagnose? (I just checked, and if I click on the Xcode alias it works just as one would expect, so the alias linkage is OK.) Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 12, 2022, at 6:42 PM, Ryan Schmidt wrote: > > On Mar 10, 2022, at 18:40, James Secan wrote: > >> In working my way through my recent “phantom ports” issue I ran the command >> “port diagnose” and was more than a bit surprised by the output line: >> >> Error: currently installed version of Xcode, none, is not supported by >> MacPorts. >> >> followed by a list of the version supported under my version of macOS (El >> Capitan, in this case). Where is port getting this information? I have >> Xcode 8.2.0 installed, and none of my attempts to install ports have run >> into any trouble related to Xcode not being installed. I ran "pkgutil -v >> --pkg-info=com.apple.pkg.CLTools_Executables” which shows that I have 8.2.0 >> installed, and the appropriate MacOSX.sdk files are in >> /Library/Developer/CommandLineTools/SDKs. I also tried this on my test >> Catalina system, with the same result. >> >> Is something wrong with my ports setup? > > > Both com.apple.pkg.CLTools_Executables and > /Library/Developer/CommandLineTools/SDKs are related to the Xcode command > line tools, which are separate from Xcode. So I guess you have the Xcode > command line tools installed but do not have Xcode installed. For many ports, > this is fine. For those where it is not, they should tell you to install > Xcode. >
Re: port diagnose and xcode
I truly appreciate everyone who maintains things for MP - couldn’t live without this stuff. My initial query was just trying to understand whether ‘port diagnose’ was telling me something I should be concerned about. I think the answer was ‘no’. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 11, 2022, at 2:21 PM, Dave Horsfall wrote: > > On Fri, 11 Mar 2022, Chris Jones wrote: > >> MacPorts is not (just) 'a simple package manager'. Yes, it performs this >> function, but first and foremost (and long before we even had binary >> tarballs to distribute as a 'package mnager') it is a system for >> building packages and their dependencies. To build something you require >> a compiler. Many ports will build fine with just the Apple CLT package, >> but some indeed require the full Xcode installation in order to be built >> (and Xcode also is not just an IDE, but is also a command line build >> system). > > I couldn't have put it better myself; the fact that some packages > (contributed to MacPorts) require Xcode is hardly MacPorts' fault. > > I dips me lid to the MP maintainers for what is obviously a thankless job. > > -- Dave
Re: Remove "Phantom" Ports
Good point. I set up my routine upgrade script many years ago, before I understood much about how MacPorts (and port) works. While fixing this disconnect I found a couple of other usages that weren’t quite what I wanted. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 10, 2022, at 12:34 AM, Ryan Schmidt wrote: > > On Mar 9, 2022, at 17:13, James Secan wrote: >> >> when I run "port upgrade installed -u outdated” > > This command doesn't make a great deal of sense. You're asking MacPorts to > upgrade the "installed" ports (which includes those those that are outdated > and those that aren't) and also the "outdated" ports (those that are > outdated). It would be simpler and more efficient to just run "sudo port -u > upgrade outdated". Single-dash/single-letter flags like "-u" go after "port" > and before the action (the action in this case being "upgrade"). > > For completeness, "-u" means "uninstall inactive ports"; if you want to keep > inactive ports, for example as a safeguard so that you could return to them > in case something is wrong with the new version, then don't use "-u". When > you eventually run "sudo port reclaim", that will get rid of the inactive > versions. > > MacPorts reminds to run "sudo port reclaim" if you have not done so in a few > weeks, unless you have configured MacPorts not to remind you.
Re: Remove "Phantom" Ports
(Resending, because I didn’t respond to the list) Just tried, and it listed far too many ports as “Unrequested ports without requested dependents found” along with the p5.26 ports for me to allow the wholesale deletion to go forward. Looked like most of the ports I have installed. I decided to go brute force. I made a list of all p5.26 ports installed and ran through “port unstall” for each one individually. After running through the list three times I’ve been able to get rid of the whole set. Hopefully that hasn’t broken anything. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 9, 2022, at 3:42 PM, Peter West wrote: > > Have you tried > port reclaim > ? > > — > Peter West > p...@ehealth.id.au > “Then the kingdom of heaven will be like ten virgins who took their lamps and > went to meet the bridegroom. Five of them were foolish, and five were wise.” > >> On 10 Mar 2022, at 9:13 am, James Secan wrote: >> >> I have a number of apparently old/replaced ports (p5.26-*) that have been >> replaced at some point by their p5.28-* updates that are still in some way >> “alive” on my system. They show up when I run "port upgrade installed -u >> outdated” as follows: >> >> Warning: No port p5.26- found in the index >> >> I’ve tried various ways to get rid of these phantoms, but nothing I’ve tried >> (like a simple port uninstall) is willing to admit that any p5.26-* ports >> are around, although a ‘port installed’ command will list all of them and >> note that they are active. I am by no stretch an expert in portsmanship, so >> I could easily be missing some simple answer. >> >> Thanks. >> Jim >> 3222 NE 89th St >> Seattle, WA 98115 >> (206) 430-0109 >> >
Remove "Phantom" Ports
I have a number of apparently old/replaced ports (p5.26-*) that have been replaced at some point by their p5.28-* updates that are still in some way “alive” on my system. They show up when I run "port upgrade installed -u outdated” as follows: Warning: No port p5.26- found in the index I’ve tried various ways to get rid of these phantoms, but nothing I’ve tried (like a simple port uninstall) is willing to admit that any p5.26-* ports are around, although a ‘port installed’ command will list all of them and note that they are active. I am by no stretch an expert in portsmanship, so I could easily be missing some simple answer. Thanks. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109
Variance Handling Question
I’m moving to a Big Sur system, and since I don’t use Xcode for anything I manually download and install the CLI tools by themsleves. I installed v12.5.1 as per the info on the MacPorts wiki (https://trac.macports.org/wiki/XcodeVersionInfo) about which Xcode goes with which macOS. Now the softwareupdater is nagging me to update to v13.0 (along with the already annoying nag to update to Monterey). I am assuming that this upgrade to CLI toolkit v13.0 is not a good idea until I move up to Monterey. Is this correct? If so, is there some way to may the softwareupdater stop the nagging? Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109
Re: provide latest OS root certificates via port?
> On 30 Oct 2021, at 12:02 am, Richard L. Hamilton wrote: > > I have VMs of a couple of old macOS / OS X versions, because I want continued > access to the features that have been removed in more recent versions (32-bit > user land support in Mojave, ability to run PowerPC apps and executables in > Snow Leopard). > > But the old machine that ran Snow Leopard is pretty much dead (why I built a > Snow Leopard VM with all its apps copied over to replace it before it died > completely). So everything runs on newer systems, but I can still run the old > OS versions as VMs if I need them. > > One might of course need more $$ to obtain a newer system (although one can > probably scrounge a deal on a newer enough used one, if one is careful). > > So I'm not sure what the limitation would be to ONLY using an old system - > although if businesses or bureaucrats are involved, limitations may not be > sensible. What VMs do you use. I find VBox unusable Parallels works nicely, but John Hoyt, doing stuff for mythtv found VBox to be ok.. James
Variance Handling Question
I have a port installed with a default variant which I want to override. Do I need to uninstall the current port with that variant prior to installing without the variant, or just go on to “port install prog -variant”? Also, from here on do I need to specify in some manner that I’ve disabled a default variant when I run “port upgrade installed”? Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109
Update on Big Sur Problems
I just checked the MacPorts wiki page for Big Sur problems and noted that it hasn’t been updated for three months (at least that’s what the wiki page says). With the possibility that new M1 iMacs might show up soon can you provide a short update on where things stand vis-a-vis Big Sur and M1-based Macs? I’m most interested in where things stand on the gcc compiler package (gfortran in particular). Thanks. Jim Seattle, WA
Re: sudo port install plplot +fortran
Isn’t the +g95 variant what he needs? Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 31, 2021, at 9:03 AM, Ryan Schmidt wrote: > > On Mar 31, 2021, at 10:53, Brian Miller wrote: > >> When running your program sudo port install plplot +fortran, I do not get >> any results. Can you recommend something other than +fortran that I might >> try? > > According to: > > port variants plplot > > the plplot port does not have a variant called "fortran". But it looks like > if you use one of the variants whose names begin with "gcc" then fortran > support will be enabled. >
Re: OS Platform mismatch - while installing stm32flash
Not sure I understand this. Do we now need to “migrate” when we update from x.x.y to x.x.y+1? Has Apple fouled things up that badly? I thought migration was only needed in a major OS upgrade, which I would consider to be from macOS x to maxOS x+1. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 11, 2021, at 6:44 AM, Chris Jones wrote: > > Hi, > > Looks like at some point you did not follow the migration instructions > correctly. You should do so now. > > Chris > >> On 11 Mar 2021, at 2:41 pm, Christoph P.U. Kukulies >> wrote: >> >> Of course the error (OS platform mismatch) occurs on every command I'm >> running on port, >> >> like >> >> port info >> >>> Am 11.03.2021 um 14:20 schrieb Christoph Kukulies: >>> Tried to do >>> >>> >>> $ sudo port install stm32flash >>> Password: >>> Error: Current platform "darwin 20" does not match expected platform >>> "darwin 19" >>> Error: If you upgraded your OS, please follow the migration instructions: >>> https://trac.macports.org/wiki/Migration >>> OS platform mismatch >>> while executing >>> "mportinit ui_options global_options global_variations" >>> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform >>> mismatch >>> >>> >>> Did an os update from macOS 12.2.2 to 12.2.3 right before. >>> >>> >>> — >>> Christoph >>> >>> >> >
Re: Build servers offline due to failed SSD
James, Thanks for the Tower of Hanoi reminder. I used that many (many) years ago with 9" tapes on a Big Iron machine but had forgotten the technique. I’ve been using a FIFO seven-day rotation backup of my main user directory (using CCC), but I’m going to reconfigure it to get the longer backup “tail” provided by the ToH approach. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 8, 2021, at 6:55 PM, James Linder wrote: > > All considered I’d take SSD for work disks and HD for long term backup > Heck in my day (ouch) we’d teach 'tower of hanoi' backup stratedgy using > tape. why not do likewise with HDs. Timemachine certainly make that easy. > > James
Re: Build servers offline due to failed SSD
> On 9 Mar 2021, at 5:53 am, Dave C via macports-users > wrote: > > Old technology drives use magnetism to hold bits. This works for decades, or > so I’ve read. Usually the motor or bearings die before the magnetic medium > fails. > > Solid State Drives use memory chips to hold bits. These “bit holders” can > wear out after a few trillion transitions (changing from 1 to 0 and 0 to 1). > I’d you’re using it in your laptop or PC, you’ll likely have no problems for > many years. In an internet-connected server, you may exceed those maximum > write cycles sooner rather than later. > Dave I was just reading up, interesting info … SSDs work (as do eproms) by having an isolated ‘chamber’. You get electrons in or out of the chamber using quantum tunneling [it disapears here and teleports there] based on probability, higher with an electric field Repeated used breaks down the insulation of the isolated ‘chamber’ SLC (the lowest capacity and most expensive) store 0 or 1 (volts or whatever unit) and are most tolerant of damage 0 is 0, 1, 2, 3 units, 1 = 6, 7 8 units with 4 more likely a 0 and 5 more likely a 1 (say) DLC store 0, 1 2 ,3 units and are less tolerant of an extra, or a fewer u TCL DLC store 0, 1, 2, 3 … 13, 14, 15 units. Are the cheapest but most fragile ie 13 can leak away to 12, or gain from 13 to 14 But the link earlier is discuusion showed drives rated at 300 TBW going well past that to 1 or 2 PBW (Peta is 1000 times Tera) In use a HD (specially with lots of them) is more likely to fail than SSD. Seagates old paper ‘ATA more than an interface’ says this: Drive 1 seeks and the bump knocks others off track. They seek back knocking others off track. Process continues until a disk fails. Their 10 year old assesment of reasons is even more relevant on todays drives. SSDs generally give more warning that ’the end is nigh’ All considered I’d take SSD for work disks and HD for long term backup Heck in my day (ouch) we’d teach 'tower of hanoi' backup stratedgy using tape. why not do likewise with HDs. Timemachine certainly make that easy. James > Dave > > - - - > >>> On Sun, 7 Mar 2021, Michael A. Leonetti via macports-users wrote: >>> >>> I’d really love to know more about what you’re saying here. Up until I just >>> read what you wrote, I thought SSDs were the savior of HDDs. >> >> Real disk drives [tm] have their N/S magnetic poles lined up pretty much >> forever; SSDs rely upon capacitors storing their charge forever (hah!). >> >> You need to have an electronics background to understand... >> >> -- Dave (VK2KFU) >
Re: migration hickup
> On 9 Mar 2021, at 4:12 am, joerg van den hoff wrote: > > > > On 08.03.21 21:01, Rainer Müller wrote: >> On 08/03/2021 17.44, joerg van den hoff wrote: >>> Now, after the data transfer completed, on the new machine I do have a >>> (seemingly/so far) working Macports installation: Migration Assistant >>> actually >>> transferred the stuff in /opt, too. >>> >>> BUT, when now trying to selfupdate on the new machine, I get the >>> message/warning: >>> >>> Warning: Failed to copy com.apple.dt.Xcode.plist to >>> /opt/local/var/macports/home/Library/Preferences: could not set owner for >>> file >>> "/opt/local/var/macports/home/Library/Preferences/com.apple.dt.Xcode.plist": >>> user "macports" does not exist >>> >>> although `finger macports' reports for the new machine that the user is >>> known >>> >>> Login: macports Name: MacPorts >>> Directory: /opt/local/var/macports/homeShell: /usr/bin/false >>> Never logged in. >>> No Mail. >>> No Plan. >>> >>> as does `id macports'. >>> >>> what am I missing? > > thanks for your reply. > >> I am not sure, but it might be that the message shown above is a bit >> inaccurate >> and it is the "macports" group that is missing? > > the message says it can't set the *owner* so it seems to actually mean _user_ > does not exist, no? > >> Please check that the user and group do exist for dscl (Directory Services): >> dscl . -read /Users/macports >> dscl . -read /Groups/macports > > yes, they do (no error messages, some reporting of properties). so I really > don't see what is missing or has been broken by an seemingly incomplete > transfer of information from the old machine basically, I don't > understand how the machine can complain about "non-existent user macports" > despite this seemingly not being true. > >> In any case, running the MacPorts install either from the .dmg or from source >> once again should recreate both the user and group named "macports". > > just to be sure: re-installing will not confuse/corrupt the database > regarding what is already installed via macports? I would prefer to keep > /opt/local intact and usable... Jorge you are brave, perhaps foolhardy. The wiki tells you exactly what to do. Basically * get a list of ports from the old machine * install macports on new * restore your ports I have found this to be far less time consuming than troubleshooting. That said a timemachine backup (on the same os version) works perfectly. James
Re: Build servers offline due to failed SSD
> On 7 Mar 2021, at 3:26 pm, Dave C via macports-users > wrote: > > This applies to affordable SSDs. As you say, the ones that are on par (re. > reliability) with HDDs are $pendy. > > It’s something to do with an SSD’s limited number of write cycles, if I > remember... > > Dave > > - - - > >> Isn’t SSD a bad choice for server duty? No server farms use them, apparently >> due to short lifespan. The reality needs to be carefully weighed up SSDs are rated in TBW. That is Terrabytes Written The Cheaper SSDs may be 300 or 600 TBW the more expensive may be 1200 TBW or even 2500 TBW. The TBW rating depends on size, I’ve put a 2T SSD (600 TBW) in my iMac and after a year i see life expected of 65 years. So no SSD for a build farm is not a bad idea. The performance benefits far outweigh the 50+ year hastle of replacing. The MTBF of spinning rust is 10 odd years, ssd is many times that. But remembering my uni stats the chance of a light globe, with a life of 1000 hours failing, when you have a few dozen bulbs (in my test question) was 20 min !!! Enterprize Disks have a longer life, but as I said it is complicated. James
Re: ARM gdb compilation fails with implicit function declaration error ioctl
> On 23 Feb 2021, at 10:08 pm, Rainer Müller wrote: > > On 19/02/2021 22.14, Dave Horsfall wrote: >> On Fri, 19 Feb 2021, Ryan Schmidt wrote: >> >> [...] >> >>> As I said in my previous message from December: >>> >>> * Don't forget to Reply All so the conversation stays on the list. >> >> Better still, set the reply to the list only? I have a beef with "Reply >> All" because I don't need my own personal copy. I looked, and looked at the forums how do I reply to list only? james
Re: Build servers going offline due to inclement weather
> On 17 Feb 2021, at 12:25 pm, Richard Bonomo TDS personal <mailto:bon...@tds.net>> wrote: > > > Clearly, Texas needs new nuclear power plants! > > During the Blizzard of 1978, coal barges were frozen in the Ohio River. Ohio > (and the eastern grid in general) managed to keep things > going because places like Wisconsin had enough nuclear power plants in those > days (no longer, though) to take up the slack from the coal-fired > electrical generation plants there were idled or operating at reduced power > output because it was not possible to get coal to them for > some weeks. > > Rich > > - Original Message - > From: "Dave Horsfall" mailto:d...@horsfall.org>> > To: "macports-users" <mailto:macports-users@lists.macports.org>> > Sent: Tuesday, February 16, 2021 10:00:50 PM > Subject: Re: Build servers going offline due to inclement weather > > [ Power cuts in Texas ] > > Amazing what you can learn here :-) Seriously, I really feel for you > guys; I've seen the stuff on TV, and, well... Rich while macports servers are in a chaotic state it's fun to play completely OT. The single (engineering, real) problem with nuclear power is that it makes a mess that lasts millions of years. The consequence of this is it turns out to be a very expensive way to go. (The 100 year.cost of the, now abandonedish Yucca Mountain repository (politics) was estimated at $100 billion) "Earth scientist discovered how to turn them (aliens) into disgusting lumps of jelly ..." Even if the touted thorium reactors can render waste short lived the question is "who pays" again making the nuclear option very expensive. This shows a bad idea happening https://www.forbes.com/sites/trevornace/2019/05/27/fears-grow-that-nuclear-coffin-is-leaking-waste-into-the-pacific/?sh=4eefc1537073 <https://www.forbes.com/sites/trevornace/2019/05/27/fears-grow-that-nuclear-coffin-is-leaking-waste-into-the-pacific/?sh=4eefc1537073> So we need a solution, not condemnation of those who try (ie Germany) james
xorg
I decided to use org rather than XQuartz But a check shows ssh sandypit [sandypit] /home/jam [1001]% xeyes Error: Can't open display: I have enabled auth ssh_config … Host * SendEnv LANG LC_* XAuthLocation /opt/X11/bin/xauth Any hints please James
Re: It was a dark and stormy night ...
About->system report Says APO512N I’ve never noticed, very sorry about the noise James > On 10 Feb 2021, at 2:22 pm, james wrote: > > The captain said to his men “Gather round my merry men I’ve a terrible tail > to tell”. This is the tail he told … "It was a dark and stormy night …” > > Once upon a time Craig did a port for mythtv. It was too hard to maintain and > building mythtv was incredibly hard. John Hoyt set about making an ansible > build that was a) much much easier b) made extensive use of macports. > > A recent change to macports jpeg library meant that the mythtv bundle used > the macports jpeg library. John has resolved this but (before he did) in > trying to track down and fix the issue I caused chaos on my MacBook. > > No worries, inconvenient, but I’ll just re-install. Gods snicker. > > I created a bootable Catalina disk and tried that way. Soon to learn the > error of my ways (explains: security stops booting from an external drive) > > I used the online tools to > a) format the disk as a case sensitive apfs drive > b) re-install Catalina (and there are reasons for not embracing Big Sur) > > After restoring some of my stuff I had no space !! > I have 2 Mac OS - Data volumes. After much cleaning and fiddling it I have > 1/2 drive space. > > Who should I go to to ask for help on disk stuff (And the dark and stormy is > about going round and round eg enter passed to change security to allow ext > boot when main disk is blank. So Install os to change security ..) > > Thanks James > > [plasma] /Users/jam [63]% df -h > Filesystem Size Used Avail Capacity iused ifree %iused Mounted > on > /dev/disk1s7 466Gi 10Gi 193Gi 6% 488254 48819646260% / > devfs 189Ki 189Ki0Bi 100% 654 0 100% /dev > /dev/disk1s6 466Gi 182Gi 193Gi49% 636680 48818162000% > /System/Volumes/Data > /dev/disk1s5 466Gi 1.0Gi 193Gi 1% 1 48824528790% > /private/var/vm > /dev/disk1s1 466Gi 19Gi 193Gi10% 95000 48823578800% > /Volumes/Macintosh HD — Data > /dev/disk1s2 466Gi 59Gi 193Gi24% 1118568 48813343120% > /Volumes/Macintosh HD - Data > map auto_home0Bi0Bi0Bi 100% 0 0 100% > /System/Volumes/Data/home > [plasma] /Users/jam [64]% ls /Volumes/ |od -atx1 > 000M a c i n t o s h sp H D nl M a c > 4d 61 63 69 6e 74 6f 73 68 20 48 44 0a 4d 61 63 > 020i n t o s h sp H D sp - sp D a t a > 69 6e 74 6f 73 68 20 48 44 20 2d 20 44 61 74 61 > 040 nl M a c i n t o s h sp H D sp � 80 > 0a 4d 61 63 69 6e 74 6f 73 68 20 48 44 20 e2 80 > 060 94 sp D a t a nl > 94 20 44 61 74 61 0a > 067 > [plasma] /Users/jam [65]%
It was a dark and stormy night ...
The captain said to his men “Gather round my merry men I’ve a terrible tail to tell”. This is the tail he told … "It was a dark and stormy night …” Once upon a time Craig did a port for mythtv. It was too hard to maintain and building mythtv was incredibly hard. John Hoyt set about making an ansible build that was a) much much easier b) made extensive use of macports. A recent change to macports jpeg library meant that the mythtv bundle used the macports jpeg library. John has resolved this but (before he did) in trying to track down and fix the issue I caused chaos on my MacBook. No worries, inconvenient, but I’ll just re-install. Gods snicker. I created a bootable Catalina disk and tried that way. Soon to learn the error of my ways (explains: security stops booting from an external drive) I used the online tools to a) format the disk as a case sensitive apfs drive b) re-install Catalina (and there are reasons for not embracing Big Sur) After restoring some of my stuff I had no space !! I have 2 Mac OS - Data volumes. After much cleaning and fiddling it I have 1/2 drive space. Who should I go to to ask for help on disk stuff (And the dark and stormy is about going round and round eg enter passed to change security to allow ext boot when main disk is blank. So Install os to change security ..) Thanks James [plasma] /Users/jam [63]% df -h Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/disk1s7 466Gi 10Gi 193Gi 6% 488254 48819646260% / devfs 189Ki 189Ki0Bi 100% 654 0 100% /dev /dev/disk1s6 466Gi 182Gi 193Gi49% 636680 48818162000% /System/Volumes/Data /dev/disk1s5 466Gi 1.0Gi 193Gi 1% 1 48824528790% /private/var/vm /dev/disk1s1 466Gi 19Gi 193Gi10% 95000 48823578800% /Volumes/Macintosh HD — Data /dev/disk1s2 466Gi 59Gi 193Gi24% 1118568 48813343120% /Volumes/Macintosh HD - Data map auto_home0Bi0Bi0Bi 100% 0 0 100% /System/Volumes/Data/home [plasma] /Users/jam [64]% ls /Volumes/ |od -atx1 000M a c i n t o s h sp H D nl M a c 4d 61 63 69 6e 74 6f 73 68 20 48 44 0a 4d 61 63 020i n t o s h sp H D sp - sp D a t a 69 6e 74 6f 73 68 20 48 44 20 2d 20 44 61 74 61 040 nl M a c i n t o s h sp H D sp � 80 0a 4d 61 63 69 6e 74 6f 73 68 20 48 44 20 e2 80 060 94 sp D a t a nl 94 20 44 61 74 61 0a 067 [plasma] /Users/jam [65]%
Re: Lots happening
> On 8 Feb 2021, at 9:57 pm, james wrote: > > After some rather traumatic shennagins with Mythtv I formatted my disk then > reinstalled Catalina, Xcode and command line tools. > I installed macports and began restoring only to get > > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > ---> Computing dependencies for curlWarning: All compilers are either > blacklisted or unavailable; defaulting to first fallback option > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > Warning: All compilers are either blacklisted or unavailable; defaulting to > first fallback option > And lots more > OK I *did* but clearly fumbled something. Accept license and all is well James
Lots happening
After some rather traumatic shennagins with Mythtv I formatted my disk then reinstalled Catalina, Xcode and command line tools. I installed macports and began restoring only to get Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option ---> Computing dependencies for curlWarning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option And lots more What is happening Thanks James
religious crap
I'm offended by having somebody tout their beliefs in a technical forum. De Grass Tyson presents argument that it is genetic, and I will not discriminate on genetics. But touting a belief is not genetic, it is for a purpose, and I think it spoils the forum. Please don't. James
mac build
I posted this to mythtv-users, but I wondered in anyone had any interest. The obvious first step is wrapping John's work in a port. - John (Hoyt) did a stellar job getting the macos/ansible build proceess to work and in no way is this critique any reflection on his effort. (and all his work is here https://sourceforge.net/projects/mythtvformacosx/) Mythfrontend on mac is aweful! What we need is someone who understands the gubbins of macos to take an interest and lead us from the wilderness :-) The app is slow to start and to stop (talking 20, 30 seconds)(cf 1-2 sec: linux) Cutlist editor core dumps *every time* editing a HD (h254) recording On linux scan of video fills in meta data. On macos it often does not. I->Change Details->Retrieve often works, often on 2nd or 3rd try. Sometimes at least the text is set but the image is not. There are also funnies with regard to season vs episode meta data retrieved. I->C->R retrieves season meta data, scan retrives episode meta data. This occurs on linux too. A workaround is to reset metadata and scan until succces. -- James
Re: macports-users Digest, Vol 172, Issue 7
Sorry about the subject line: macports is my only digest mail and I keep forgetting :-( James
Re: macports-users Digest, Vol 172, Issue 7
> On 8 Dec 2020, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > > > Does anybody have any configuration that would allow for running X11 in > a window-as-display? That is, a single Mac window would display an X11 > session: window manager, multiple windows, etc. > > Ie: X11.app can do windowed mode where each X-window is a Mac-window, or > root where the entire display is owned by X11 (full screen), but cannot > have root-in-a-window, where a single MacOS window would contain an X11 > session (window manager, windows, etc). > > Alternately, I could start a VNC server, and connect to localhost via a > VNC client. > > I have tried: > > - X11.app does not have window-as-screen mode > - Xnest does not appear to have a port (ie: tell X11.app to run Xnest > and let it then run a window manager) > - Couldn't find any Xnest-equivalent ports > - packages category:vnc: > - tightvnc fails to build > - tigervnc is viewer only > - vnc fails to build > - cotvnc is viewer > - vineserver appears to be a vnc server to allow access to the Mac At risk of sounding flippent the old "How do you get an elephant into a refridgerator"? "Open the door and put it in. Don't look for complications" likewise here $ ssh othermachine othermachine> xprogram To get (and/or share a complete desktop) nomachine is easy and works well. Fullscreen or window. James
Re: info
I think a large number of us are very interested in the status of ports vis-a-vis both Apple Silicon (M1) and Big Sur. Some sort of simple red-yellow-green status board for ports that have been checked would be very useful. Verified support for the MacPorts codes I use regularly is a major check-box on my buy-now list for a new M1 machine. I suspect this is more easily visualized than actually produced and maintained. Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Dec 4, 2020, at 1:50 PM, Mojca Miklavec wrote: > > On Fri, 27 Nov 2020 at 16:27, Giovanni Cantele wrote: >> >> Dear All,. >> >> I’m searching the web but I cannot find any response to the following >> question: >> >> is there any ongoing project for porting the whole macports staff on the new >> Apple silicon architecture? > > There is no "special ongoing project". There are volunteer owners of > Apple silicon trying to fix the bugs they encounter. > MacPorts itself should work, lots of ports work, some complex software > requires non-trivial patches from upstream. > >> What happens to those who extensively make use of macports and have bought >> the recent released MacBook Pro running on the new processors? > > You should be able to install MacPorts and many ports. But you should > not be surprised if you hit some that will refuse to build and you may > need to wait for upstream to fix the issue (or try to fix it yourself > and submit a patch or find someone else capable of fixing it ...). > > You brought up an interesting point though, we should probably publish > some official statement about arm support on our main website. > > On Fri, 4 Dec 2020 at 16:19, Alejandro Imass wrote: >> >> What you are saying suggests that nothing major has changed except the LLVM >> target to arm64, is this correct? > > Disclaimer: I don't have any experience with an arm-based mac. > > As far as MacPorts is concerned, I would say that indeed "almost > nothing major" has changed in principle (other than the processor, > which is ... well, a really major change). > > A lot of relatively simple, well-written software with a well-written > build system should often work out of the box. > > But a lot of software may either have some hard-coded assumptions in > either their build system or the source, it may require some > intel-specific intrinsics, or it may depend on some complex > third-party library that doesn't compile. Apple also likes to increase > security standards each year which may break many ports in various > ways. > > If you have your favourite port, you can quickly check the build > results on, say, >https://ports.macports.org/port/wget/stats > and check for either green port status or some reported installations > on arm64, check for open tickets etc. Keep in mind that many port > builds haven't been attempted yet. > > (I also see that some builds like wget were successful, but missing on > the list, while some like youtube-dl are redirected to the x86_64 > builder and also don't end up on that list.) > > Mojca
Re: macports-users Digest, Vol 170, Issue 19
Appologies for the stupid Subject. I went away from a digest for mythtv (so you just reply to a thread) and the rot siezed my brain James
Re: macports-users Digest, Vol 170, Issue 18
> I just upgraded my MacBook to Catalina 10.15.7 from 10.14.6 and I installed > the latest Xcode 12.1. I started Xcode and agreed for it to install required > components. When I tried to run ?xcode-select ?install? it asked me to agree > to the license for the command-line tools and tried to install but then said > ?Can?t install the software because it is not currently available from the > Software Update server.? I went to the Software Update control panel and it > said that it had an update for my command-line tools, and I told it to go > ahead and update them. After a while, it said that the command-line tools are > no longer required or something like that. > > I decided to go ahead and try to install MacPorts with the Catalina MacPorts > installer and it showed me the license, asked about the installation type and > destination, but then when it got to the install step it says ?Waiting for > other installations to complete?. I don?t think I have any other > installations still going on. Wait, after twenty minutes, it now says it is > ?running package scripts? and then finished. I guess it was installing > something after all. > > Maybe the Xcode installation instructions need an update for Catalina Eric I know that 'me tooo' posts are a pain but at least this will give you confidance. I did for my laptop and for a VM to play with mythtv. Clean Install of catelina Clean install of xcode Clean install of macports I don't recall where, maybe on license accept, but certainly following the wiki, command line tools were installed. Macports just works James
Re: Ubuntu 18.04.4 on older Apple hardware
> On 6 Apr 2020, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > > Initially I burned the 64bit Ubuntu 18 version, but it wouldn't boot on my > 32bit EFI Mac. > > There was no 32bit version of Ubuntu 18.04.4 that I saw, so I booted the > Ubuntu 16.x 32bit version without trouble. But I didn't want to install that, > as that seems doomed and out of date. > > And then I stumbled across a small C program that tweaks the ISO image in > such a way that it allows the 64bit Ubuntu to boot on a 32bit EFI Mac. > <https://github.com/demonicsweaters/make_single_eltorito.c> I risked one more > DVD and to my modest surprise, it worked very well. I can't tell you exactly > what it does, but someone on this list likely does know exactly what it does. > > Quite possibly it might work with the USB boot method as well, but I didn't > try that as yet. > > To get the camera working on this older MacBook, there is software in Ubuntu > that takes a driver from your existing MacOS installation and tweaks it > slightly. "isight-firmware-tools". > > For newer MacBooks, there is another project to make the HD camera work. I > did't try that. > > I did boot the 64bit DVD on another newer MacBookPro I have, and it booted > up. I'm not sure at this second just which graphics card it is using. > > It's certainly not MacOS -- the trackpad is jittery, the mouse moves a bit > clumsily, setting up hardware is easy if it "just works" but not so easy if > it doesn't -- you have to edit conf files, etc. The microphone works in some > applications but not other applications (what is that about)? SO yeah -- it's > Linux, with all it's benefits and all the warts I remember. > > But it may be useful for some things, like the applications I need to use now > that we're all at home with everyone in the house doing videoconferencing > with different groups, and we all of a sudden have a need for many current > computers with this capability. > > I'm glad I have it as an option -- I partitioned my SSD and with a bit more > software that I plan to tweak today, I'm supposed to be able to dual boot > without trouble. I’ve got a new MBP which does not play at all nicely with linux (no trackpad, keyboard, network I did not even try bluetooth. I’m a fan of VirtualBox but I bought Parallels since it’s disk io was much nearer NVME native speeds. I run full screen SuSE on 1 desktop, where it behaves beautifully: Fast, no noticeable impact on the rest of the system. I’m using Rosegarden and the USB transfer seems good. The few niggles are: Setup is good but much more obscure than VirtualBox If I plug in a mem stick OSX wont see it until Parallels releases it. Ubuntu seems to have adopted many mac features eg toolbar menu on the focus’d app, dock etc But this seems a way of getting all the pros without the cons James
Can anyone see why
I had a hierarchy of MythA-C, MythD-F for my recordings I changed the hierarchy to Myth-A, Myth-B etc The first transcode I did failed I tried another from another chanel. That too failed, but I see nothing wrong. Anybody see my error Thanks James [sandypit] /store/jam [1003]% ffprobe /store/1092_20200315123600.ts ffprobe version 4.2.1 Copyright (c) 2007-2019 the FFmpeg developers built with gcc 9 (SUSE Linux) ... [mp3float @ 0x560306e93e00] Header missing [mpegts @ 0x560306e8db40] PES packet size mismatch Last message repeated 1 times [mpegts @ 0x560306e8db40] Could not find codec parameters for stream 3 (Unknown: none ([5][0][0][0] / 0x0005)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 0x560306e8db40] Could not find codec parameters for stream 4 (Unknown: none ([11][0][0][0] / 0x000B)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 0x560306e8db40] Could not find codec parameters for stream 5 (Unknown: none ([12][0][0][0] / 0x000C)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, mpegts, from '/store/1092_20200315123600.ts': Duration: 03:04:28.69, start: 8823.395622, bitrate: 2938 kb/s Program 1 Stream #0:0[0x204]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, top first), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x28d](eng): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, fltp, 192 kb/s Stream #0:2[0x243](eng): Subtitle: dvb_teletext ([6][0][0][0] / 0x0006) Stream #0:3[0x321]: Unknown: none ([5][0][0][0] / 0x0005) Stream #0:4[0x322]: Unknown: none ([11][0][0][0] / 0x000B) Stream #0:5[0x323]: Unknown: none ([12][0][0][0] / 0x000C) Unsupported codec with id 94215 for input stream 2 Unsupported codec with id 0 for input stream 3 Unsupported codec with id 0 for input stream 4 Unsupported codec with id 0 for input stream 5 [sandypit] /store/jam [1004]% ... + mythtranscode -i /store/1092_20200315123600.ts -o '/store/Movies/MythJ/You Only Live Twice.avi' --honorcutlist --showprogress -m 2020-03-22 17:32:29.752980 C mythtranscode version: fixes/29 [v29.1-60-gaf5d819671] www.mythtv.org 2020-03-22 17:32:29.752999 C Qt version: compile: 5.12.3, runtime: 5.13.1 2020-03-22 17:32:30.783886 E No locale defaults file for en_AU, skipping 2020-03-22 17:32:30.816580 E Skipping unsupported codec 3 on stream 2 2020-03-22 17:32:30.816584 E Skipping unsupported codec 2 on stream 3 2020-03-22 17:32:40.976172 E Couldn't open input file, error #-2 2020-03-22 17:32:40.977115 E Transcoding /store/1092_20200315123600.ts failed + stat=128 + [[ 128 == 0 ]] + echo transcode failed try recode needed for some h264 transmissions of HD transcode failed try recode needed for some h264 transmissions of HD nothing here has changed [sandypit] /store/jam [1004]% ls -l /store/1092_20200315123600.ts -rw-r--r-- 1 jam video 4066154240 Mar 15 23:40 /store/1092_20200315123600.ts
Re: catalena
Thanks for the answer, to Chris too. When catalena was relrased there were a flurry of ‘don’t rush’ type posts. I was checking if ‘dont rush to catelena’ was still the general opinion. I have not yet even received my macbook (tomorrow :-) so it is that new. From an engineering point of view it makes sense to limit the os but is still um irritating James > On 24 Feb 2020, at 1:10 am, Mojca Miklavec wrote: > > Given that you have an OS installed, just try to install whatever you > need and if you run into any serious issues, ask about specific > problems. > > (It might be true what Chris said and that you won't be able to go > back in time, not sure when the hardware was released, so maybe 10.14 > still works, but if you have 10.15 installed, try to check if you see > any problems first. The OS has been around for a while, so most > pressing problems were solved in the meantime. You won't be able to > build or run 32-bit software though.) > > Mojca > > On Sat, 22 Feb 2020 at 14:14, James Linder wrote: >> >> Hi All >> >> After 6 years my macbook battery is really past it’s use-by. >> The keyboard has become a sea of >> won’t-push-this-week-and-hard-to-get-a-keypush so I decided to get a new >> laptop, but of course it comes with catalena. >> I’ve been using high sierra and all my ports are good. Is catalena now >> stable enough to ‘just work’ or need I consider installing (say) high sierra. >> >> James >>
catalena
Hi All After 6 years my macbook battery is really past it’s use-by. The keyboard has become a sea of won’t-push-this-week-and-hard-to-get-a-keypush so I decided to get a new laptop, but of course it comes with catalena. I’ve been using high sierra and all my ports are good. Is catalena now stable enough to ‘just work’ or need I consider installing (say) high sierra. James
Re: no destroot found (was: help please)
mac > On 15 May 2019, at 4:22 pm, Joshua Root wrote: > >> what does this mean … >> >> [haycorn] /Users/jam/DEVEL [580]% sudo port install qt511-qtwebkit >> ---> Computing dependencies for qt511-qtwebkit >> ---> Installing qt511-qtxmlpatterns @5.11.3_0 >> Error: Failed to install qt511-qtxmlpatterns: no destroot found at: >> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt511/qt511-qtxmlpatterns/work/destroot > > It's a bug. Quite a few people have encountered it, but we've never been > able to reproduce it. If you know how to reproduce it, please add that > information to <https://trac.macports.org/ticket/55445>. > > The workaround is simple however: clean the affected port. Thanks that did indeed work. In tems of doing something funny - I think I did not, but here goes port install qt5 qt5-qtwebkit Hmmm 12 did not work (I’ll go back to see why - mysql plugins) port uninstall `port installed |grep qt5` port install qt511 qt511-qtwebkit James
Re: help please
Hi what does this mean … > [haycorn] /Users/jam/DEVEL [580]% sudo port install qt511-qtwebkit > ---> Computing dependencies for qt511-qtwebkit > The following dependencies will be installed: > qt511-qtdeclarative > qt511-qtgraphicaleffects > qt511-qtimageformats > qt511-qtlocation > qt511-qtmultimedia > qt511-qtquickcontrols > qt511-qtquickcontrols2 > qt511-qtsensors > qt511-qtserialport > qt511-qtwebchannel > qt511-qtwebsockets > qt511-qtxmlpatterns > Continue? [Y/n]: y > ---> Installing qt511-qtxmlpatterns @5.11.3_0 > Error: Failed to install qt511-qtxmlpatterns: no destroot found at: > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt511/qt511-qtxmlpatterns/work/destroot > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt511/qt511-qtxmlpatterns/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > Error: Processing of port qt511-qtwebkit failed Does this help? ls /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt511/qt511-qtxmlpatterns/work [haycorn] /Users/jam [503]% Thanks James
help please
Hi what does this mean … [haycorn] /Users/jam/DEVEL [580]% sudo port install qt511-qtwebkit ---> Computing dependencies for qt511-qtwebkit The following dependencies will be installed: qt511-qtdeclarative qt511-qtgraphicaleffects qt511-qtimageformats qt511-qtlocation qt511-qtmultimedia qt511-qtquickcontrols qt511-qtquickcontrols2 qt511-qtsensors qt511-qtserialport qt511-qtwebchannel qt511-qtwebsockets qt511-qtxmlpatterns Continue? [Y/n]: y ---> Installing qt511-qtxmlpatterns @5.11.3_0 Error: Failed to install qt511-qtxmlpatterns: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt511/qt511-qtxmlpatterns/work/destroot Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt511/qt511-qtxmlpatterns/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port qt511-qtwebkit failed Thanks James
help for the ignorant
Hi Craig pointed me at this https://github.com/macports/macports-ports/pull/2214 an un-commited port. I want to play with it. How do I checkout? James
Re: completely OT
Hi > > I have a mid 2011 iMac. I setup a SSD on usb3 over thunderbolt. > All good EXCEPT that it wont boot. Will boot on the usb2 ports but they are > slower than usb3. > I'm looking for a pointer or advice on how to boot on diskA say the internal > disk, but run (root on) diskB > I can't find a thunderbolt 1 disk or adapter > > Can anybody point me at where I could ask these sort of questions > sorry for last-resort posting here Dave > macsupportcent...@yahoogroups.com > > Mac Support Central, a Yahoo group, is a great resource for all Mac owners. > Many Mac users and professional repair techs. Even an author of a self-repair > book series. Thank you. Al > I have the same iMac and it's not capable of booting USB3, even with a > Thunderbolt or hub. Afraid you are stuck with USB2. > > There are plenty of Thunderbolt drives available. I used one from LaCie. I believe it is a CPU issue, older CPUs can’t, newer can. Every LaCie drive I google is thunderbolt 3. I need 1 or 2. Spelunking I found a very interesting (and unlikely) site that delves deeply into technical stuff like booting. But they raise the issue of codesigning, https://eclecticlight.co/2019/04/10/macs-move-closer-to-compulsory-notarization/ and the potential to codesign an executable which would have a major impact on macports Again thanks to the list for indulging OT stuff James
completely OT
Hi I have a mid 2011 iMac. I setup a SSD on usb3 over thunderbolt. All good EXCEPT that it wont boot. Will boot on the usb2 ports but they are slower than usb3. I'm looking for a pointer or advice on how to boot on diskA say the internal disk, but run (root on) diskB I can't find a thunderbolt 1 disk or adapter Can anybody point me at where I could ask these sort of questions sorry for last-resort posting here Thanks James
Re: Restarting from scratch on Snow Leopard
> On 1 Mar 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >>> is llvm39 still the one to be used? >> >> I still use +llvm39 >> >> $ port -v installed | grep ld64 >> ld64 @3_1+universal-ld64_127-ld64_236-ld64_97 (active) platform='darwin 10' >> archs='i386 x86_64' date='2018-09-20T16:56:39-0700' >> ld64-latest @274.2_2+llvm39+universal-llvm34 (active) platform='darwin 10' >> archs='i386 x86_64' date='2017-11-26T13:19:27-0800' >> >> >> One thing you learn in this, is to be current but not too current. There is >> no benefit to trying to ride the dragon's tale here -- you just run into a >> lot of new errors that haven't been dealt with yet. >> >> llvm3.9 is about equal to Sierra. That's a pretty good spot. I haven't >> really tried anything newer yet. >> >> I was configured to use clang-3.9 as my primary compiler up until a few >> weeks ago, when I fixed clang-5.0+ to enable thread_local storage, and so >> have just recently set clang-5.0 as my default compiler. > > > Right now I’ve finished the whole procedure described in > > <https://trac.macports.org/wiki/LibcxxOnOlderSystems> > > > without hitting any issue (unlike when I had Xcode 4.2 installed). Will now > attempt installing the usual packages I need. > > Thanks for your help, Ken! I bought a mac. It came with Snow Leopard CDs. I cleaned the disk and want to re-install Snow Leopard. I can’t “Certificate Expired”. Google: easy: iTunes -> purchased: download (ooops I never purchesed or downloaded a copy, I have the CDs), OK Apple Download: only the earliest is later than that. (IIRC Yosemite) Oh Apple! he politely lamented So how does the poor boy install Snow Leopard? Brain surgery on the CD springs to mind but that is too involved for moi. No network and fiddle the date? James
OT upgrade nag
Hi some folk here choose to not upgrade their macos. How do you folk get rid of Apples uphrade nag? James
Re: A general philosophical question about MacPorts
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> So my philosophical question is “Why MacPorts these days?” > > Because running the tools it provides in a VM is a grotesque waste of > RAM and disk space and puts a wall up between tools I want to use > occasionally and the UI where I prefer to work mostly. Bill I disagree! What is a waste? I typically give my VMs 2G from a 32G pool. I run 2 or 3 VMs without noticeing. You *can* get apple ram from not-apple that is quite cheap. > Also, on one old 1st generation Core Duo iMac, it helps me to build and > run a suite of server software and other key tools that can face the > Internet with reasonable safety A couple of years ago one of the anti-virus companies offered $10 000 and a Sony Viao to the first person to hack their honeypot Windows, Max and Linux boxes. The Windows reward was claimed within hours The Mac was hacked in a week (a flaw in safari) The linux prize is still unclaimed. Detractors opined that ir was unkewl (sic) to hack linux. Rubbish! It would be very kewl to be the one who found an exploitable flaw in linux. Yesterday News: Canberra parliment in massive hack. Makes you wonder. > and an attack surface that doesn't quite > look like any other machine while seeming irresistible to a certain > class of miscreants. I have a professional interest in the unique > behavioral intelligence I get from that machine that I cannot get > anywhere else. It would be a serious chore to maintain that host as > 'live bait' without MacPorts and I hate the idea of just discarding a > machine that would otherwise have no practical use. I guess the subject is dear to my heart that explains me waxing (so) lyrical. James
Re: A general philosophical question about MacPorts
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >>> >>> So my philosophical question is “Why MacPorts these days?”. >> >> Same reason as always: to help you install software on your Mac. If >> you prefer installing software in a VM running a different OS, by all >> means do so, but it's not the same thing. > > Another philosophical question you might want to ask > yourself is "Why macOS these days?" That's only a bit > facetious (a large bit, admittedly). If you mostly use > a VM, you might be better off just installing that OS > on the hardware and replacing macOS. Just a thought. I’ve tried linux on my iMac27. While it works, Apple for all their faults do a much better job of managing the hardware: Bluetooth pre boot. MacOS fiddles the sound to make it ‘sound’ nice, on linux it is tinny. MacOS sleeps the unused cpu cores, linux throttles them. The linux way runs much hotter. I use MS word occasionally. MS in their anti-linux mode don’t do a Word. I use CrossOver but a native toolset is noticeably nicer. I sat my wife, as a totally naive user in front of Word and OpenOffice and she quickly gravitated one way. I have to accept that being a borg does not stop ypu writing nice software. If you use a touch pad the MacOS gestures are much better managed than linux making a VM attractive, There is a whole world I have not explored using a VM app in a native window. (think it is called seamless mode on VirtualBox) > The only reason I use macos at all is because it's > unixy. I spend most of my time in full screen X11 using > many programs and languages from macports. I assume that the general anti-X11 rant comes from people who have no idea! The whole wayland push fills me with dread. I use multiple computers, usually from one seat. (X11 lets you do that) for all the Mac stuff I resorted to nomachine. Thats a poor subsitute. Again much of macports let you choose X11. > Even without > X11, macports makes it easy to install and upgrade lots > of software that would otherwise be cumbersome to > install individually, let alone keep up to date. I > wasn't even aware that Apple supported macports. Apple > doesn't really support X11 like it used to either and > it doesn't work quite as well as it does under Linux > but it'll do. > >> From my point of view, macports makes it possible to > keep using macOS. Without it, Linux in a VM or > replacing macOS altogether would be hard to resist. James
Re: A general philosophical question about MacPorts
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > > First let me say I have used MacPorts since 10.6.8. > > Recently, given the overall Apple direction for MacOS I stopped and asked > myself “Why am I doing this?”. > I started using Mint Linux on VirtualBox and ported a couple of the simpler > apps I use. > Mint has come a long way and runs very well on a VBox instance. Data can move > easily from MacOS to Mint and vice-versa. > True, I have been a *nix user for decades, but a novice (non-*nix user) > wouldn’t be using MacPorts anyway. > > I appreciate all the work the developers have put into MacPorts but to me the > handwriting on the wall was when Apple pulled the MacPorts informal support > they provided for years. > So my philosophical question is “Why MacPorts these days?”. I wonder if I’ll tread on toes: In order to seamlessly drain all your money Apple need to make nice hardware that works well. They do. I run a doz or so linux VMs, yet having macports provide many of the daily tools I use is incredibly useful. James
Re: whew
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > > > OK > Your inbox has 14500 mail. > mail->backup size exceeded (after 20%) > > So I was trying to save all your mail using thunderbird > > The flash in the corner was “m...@tigger.ws: junk mail” not as in mail ‘from > mary’ > still trying to backup > > XX That was a problem between seat and keyboard. I don’t know how I miss posted. Appologies James
whew
OK Your inbox has 14500 mail. mail->backup size exceeded (after 20%) So I was trying to save all your mail using thunderbird The flash in the corner was “m...@tigger.ws: junk mail” not as in mail ‘from mary’ still trying to backup XX
browser recomendations
Hi I’ve been using firefox for a while. but increasingly it is getting draconian. From firefox’s forums: Ah, I see Mozilla is adopting the Microsoft Windows 10 attitude: “We know what’s best for you. Turn off updates completely? What folly! We reserve the right to nag you incessantly until you comply! Use a feature which we deem obsolete or not important enough to support anymore (cough, RSS, cough)? We’ll dump it and you’ll learn to live with it.” Oh, and we have this neato new thingy we’re just dying to try out on you. You’ll just LOVE it, promise! Even if you don’t, hey, we’re getting a nice kickback from a third party for including it, so WE’LL love it.” Good luck with that strategy, guys. You’re going to need it. Are there any ports or browsers that you folk can recomend: I want RSS feeds I want NO search in URL bar I want a search bar I want the choice of updates free of nags James
Re: gdb
> On 9 Jan 2019, at 12:48 am, Ken Cunningham
> wrote:
>
> fyi
>
> I updated gdb last night, to the current version.
>
> so it might be worth trying again
>
> gdb and lldb are both good debuggers, but they are different, and it takes a
> while to get facile with either.
>
> K
>
>
> On 2019-01-08, at 6:34 AM, Ryan Schmidt wrote:
>
>> I don't know why gdb isn't working for you. From what I've been able to
>> find, it should be able to debug programs built by clang.
>>
>> But have you considered trying lldb instead?
I suspect the codesign but I am confused:
I am using 10.13.6 and have seen the warnings that 8.1 is not compatable, is
8.2 ok?
[Haycorn] /Users/jam [517]% sudo codesign -s gdb-cert /opt/local/bin/ggdb
Password:
/opt/local/bin/ggdb: is already signed
[Haycorn] /Users/jam [518]% ggdb a.out
GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin17.7.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from a.out...Reading symbols from
/Users/jam/a.out.dSYM/Contents/Resources/DWARF/a.out...done.
done.
(gdb) l
1 #include
2 int main ()
3 {
4 printf ("Hello world\n");
5 }
(gdb) r
Starting program: /Users/jam/a.out
Unable to find Mach task port for process-id 771: (os/kern) failure (0x5).
(please check gdb is codesigned - see taskgated(8))
James
PS Ryan I will use lldb as a last resort, but baby-duck symdrome does rear it’s
head. Thanks.
Re: gdb
> On 6 Jan 2019, at 1:00 am, Mojca Miklavec wrote: > > Dear James, > > I don't quite understand what your question/problem is. Can you please > be more explicit (ideally on the mailing list). > > Mojca > > On Sat, 5 Jan 2019 at 15:11, James Linder wrote: >> >> Hi >> >> can anybody show me mt errant ways >> >> I installed gdb >> codesigned as per >> https://sourceware.org/gdb/wiki/BuildingOnDarwin#Giving_gdb_permission_to_control_other_processes >> I get >> >> [Haycorn] /Users/jam/nodups [510]% ggdb nodups.app/Contents/MacOS/nodups >> GNU gdb (GDB) 8.0.1 >> Copyright (C) 2017 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. Type "show copying" >> and "show warranty" for details. >> This GDB was configured as "x86_64-apple-darwin17.2.0". >> Type "show configuration" for configuration details. >> For bug reporting instructions, please see: >> <http://www.gnu.org/software/gdb/bugs/>. >> Find the GDB manual and other documentation resources online at: >> <http://www.gnu.org/software/gdb/documentation/>. >> For help, type "help". >> Type "apropos word" to search for commands related to "word"... >> Reading symbols from nodups.app/Contents/MacOS/nodups...(no debugging >> symbols found)...done. >> (gdb) q >> >> [Haycorn] /Users/jam/nodups [511]% port list gdb >> Warning: port definitions are more than two weeks old, consider updating >> them by running 'port selfupdate'. >> gdb@8.0.1 devel/gdb >> >> nodeps IS compiled with -g >> Anybody please /Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile all /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -c -pipe -stdlib=libc++ -g -std=gnu++11 -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -mmacosx-version-min=10.12 -Wall -W -fPIC -DQT_DEPRECATED_WARNINGS -DQT_GUI_LIB -DQT_CORE_LIB -I. -I. -I/opt/Qt5.12.0/5.12.0/clang_64/lib/QtGui.framework/Headers -I/opt/Qt5.12.0/5.12.0/clang_64/lib/QtCore.framework/Headers -I. -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/OpenGL.framework/Headers -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/AGL.framework/Headers -I/opt/Qt5.12.0/5.12.0/clang_64/mkspecs/macx-clang -F/opt/Qt5.12.0/5.12.0/clang_64/lib -o main.o main.cpp [Haycorn] /Users/jam/nodups [511]% lldb nodups.app/Contents/MacOS/nodups (lldb) target create "nodups.app/Contents/MacOS/nodups" warning: (x86_64) /Users/jam/nodups/nodups.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui empty dSYM file detected, dSYM was created with an executable with no debug info. warning: (x86_64) /Users/jam/nodups/nodups.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore empty dSYM file detected, dSYM was created with an executable with no debug info. Current executable set to 'nodups.app/Contents/MacOS/nodups' (x86_64). But elsewhere this does work: [Haycorn] /Users/jam/nodups [512]% cat nodups.pro TEMPLATE = app TARGET = nodups INCLUDEPATH += . CONFIG += debug <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< and there IS a -g DEFINES += QT_DEPRECATED_WARNINGS # Input SOURCES += main.cpp James
gdb
Hi can anybody show me mt errant ways I installed gdb codesigned as per https://sourceware.org/gdb/wiki/BuildingOnDarwin#Giving_gdb_permission_to_control_other_processes I get [Haycorn] /Users/jam/nodups [510]% ggdb nodups.app/Contents/MacOS/nodups GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-apple-darwin17.2.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from nodups.app/Contents/MacOS/nodups...(no debugging symbols found)...done. (gdb) q [Haycorn] /Users/jam/nodups [511]% port list gdb Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'. gdb @8.0.1 devel/gdb nodeps IS compiled with -g Anybody please James
Re: Help please
> On 18 Nov 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >>>> The new bit is a Telstra NBN modem (for Aus’s new high speed broadband.) >>>> If any Aus user has tamed the Telstra NBN modem please tell me what and >>>> how. >>> Have you tried using a closer mirror instead of the master (which is in >>> Germany)? >>> >>> https://trac.macports.org/wiki/Mirrors >>> >>> You can separately configure where base is downloaded from during >>> selfupdate (macports.conf) and where ports are downloaded from during >>> selfupdate or sync (sources.conf). >>> >>> We have a mirror in Australia, unfortunately for some reason they don't >>> mirror base. I'll have to have a word with them about that. Maybe there is >>> another mirror that's closer to you than the master. Maybe try the one in >>> New Caledonia. >>> >>> The Australian mirror does mirror ports, so you could use it for that. >>> >>> Trying different servers could also be a troubleshooting step to narrow >>> down whether it's a problem with all rsync traffic or just with reaching >>> specific servers. >> Ryan thanks. >> The problem is definately the modem. I turned OFF the firewall (actually I >> need to think thru, why would the modem have a firewall at all, unless bad >> guys can login to the modem …) and rsync ran perfectly. I tried but was not >> able to make a modem firewall rule for rsync. >> So turn off firewall, selfupdate, turn on is pretty painless. >> >> James > > Have you tried explicitly opening 873/tcp outgoing? > > Have you tried using iftop or wireshark to see what is/isn't being > connected to? Russel I did explicitly make a rule for tcp/873, which surprised me by not working!! After some thought I did not bother with wireshark, Since my modem is only NAT for machines on my network * RFC state that no router (on internet) may route a private address packet * The modem must dump any un ESTABLISHED,RELATED packet The firewall could only assist if * I had machine(s) with a public IP * All the internet routers were broken and routed private IP packets to me * My modem was broken and sent unknown packets to SOME MACHINE on my network * I had an infected machine that tried to call out (to disclose keystrokes or infect other machines) So just turning off the firewall is the easist way and pretty safe (If my modem was broken then why cant you hack it to have no firewall anyway.) I think the huge amount of dis-infomation on the subject is akin to saying if you go hiking without a defibulator you are certain to die. James
Re: Help please
> On 17 Nov 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> The problem is definately the modem. I turned OFF the firewall (actually >> I need to think thru, why would the modem have a firewall at all, unless >> bad guys can login to the modem …) and rsync ran perfectly. I tried but >> was not able to make a modem firewall rule for rsync. So turn off >> firewall, selfupdate, turn on is pretty painless. > > Again, as an Aussie NBN user I have had zero problems with it, and I > didn't have to do anything special (other than port-redirects to my > FreeBSD server). You are with T$, aren't you, with the Fast 5355 router? > > And yes, you *do* need the firewall enabled, to at least "Medium" i.e. > inbound traffic only in response to outbound traffic, and block everything > below NetBIOS. > > You do have remote access disabled, don't you? And even then, T$ can > "upgrade" your firmware in the middle of the night, and the first you know > about it is when the Mac has dropped the WiFi connection and failed to > restart (you need to disable/enable it, and hope that it gloms onto the > right service). My motivation in continuing this thread is that unless macports users are rare in Aussie (how sad that would be) then other macport users are certain to have the magic big T$ modem. (T$ is joke reference to Telstra) I do not use the modem wifi, apple do not play nice with furren AC modems (my tests are 5Mb / sec close to a tp link and 35Mb to an airport using my macbook) Dave I do not understand your > And yes, you *do* need the firewall enabled Any out going packet will be NAT’d and allowed back Any intruding packet will not be NAT’d and dumped by the router. There is no pathway from the internet to any of mymachine unless the packet is ESTABLISHED, RELATED The best answer that I can find is that if you have and infected machine the firewall prevents it calling other machines. Well my network is linux and mac machines only, so I guess that is of little concern James
Re: Help please
> On 16 Nov 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> I can’t believe that I am the only Aussie macports user plagued by the >> problem. > > Apparently... > >> I went to Access Control->firewall and turned it OFF during the >> selfupdate. I was not able to make a rule that worked for rsync > > What about the Mac's built-in firewall? I have it turned off, because I > don't need it (the Fast-5355 router supplied with the NBN does that for > me; nothing can reach the Mac except in response to outbound traffic). This drifts to OT sorry. My mac(s) have no firewall on. I speculate that if the problem is not widespread then telstra delivered other modems with the firewall switched off. I have a single port forward on port (what the heck) 2234 for ssh. That is the only access from outside to my mac. Why on earth would would the modem have a firewall? (but their firmware is ratty so maybe thet are protecting their modem) Their technical support is of the ‘connect your windows machine to the modem’ level, not more. In any event the macports rsync issue is the modem firewall Thanks for the help James
Re: Help please
> On 16 Nov 2018, at 11:14 am, Ryan Schmidt wrote: > > > > On Nov 15, 2018, at 00:51, j...@tigger.ws wrote: > >> The new bit is a Telstra NBN modem (for Aus’s new high speed broadband.) If >> any Aus user has tamed the Telstra NBN modem please tell me what and how. > > Have you tried using a closer mirror instead of the master (which is in > Germany)? > > https://trac.macports.org/wiki/Mirrors > > You can separately configure where base is downloaded from during selfupdate > (macports.conf) and where ports are downloaded from during selfupdate or sync > (sources.conf). > > We have a mirror in Australia, unfortunately for some reason they don't > mirror base. I'll have to have a word with them about that. Maybe there is > another mirror that's closer to you than the master. Maybe try the one in New > Caledonia. > > The Australian mirror does mirror ports, so you could use it for that. > > Trying different servers could also be a troubleshooting step to narrow down > whether it's a problem with all rsync traffic or just with reaching specific > servers. Ryan thanks. The problem is definately the modem. I turned OFF the firewall (actually I need to think thru, why would the modem have a firewall at all, unless bad guys can login to the modem …) and rsync ran perfectly. I tried but was not able to make a modem firewall rule for rsync. So turn off firewall, selfupdate, turn on is pretty painless. James
Re: How Mojave-ready is MacPorts?
> On 13 Nov 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > > On Nov 11, 2018, at 14:36, Dave Horsfall wrote: > >> On Sat, 10 Nov 2018, Bill Cole wrote: >> >>>> OK, I've been talked out of trying Mojave on this thing (it's unlikely to >>>> work) >>> >>> Indeed. https://support.apple.com/kb/SP777?locale=en_US says it definitely >>> won't. >> >> So I see; well, it's served me well for nine years... I only upgrade >> hardware when forced to, so I guess it's time to put some of my pension >> aside for a MacBook Air or something. > > There are usually ways of shoehorning newer operating systems into > unsupported older systems, at the expense of some performance problems or > other issues. I’m technical and dont use my machine for all the wizz bang social media stuff so I find that mojave offers me very little and infact the screen blanker kicks in intermittently while watching mythtv and my wakeup from sleep is 10 secs ! instead of un-noticably short (a sec or two) that it was on high sierra. So a cute experiment but I’ll go back to high sierra. (https://support.apple.com/en-au/HT208969) James
Re: quite OT [solved] but interesting
After lots of hunting I re-installed high sierra from scratch. Public key DID work. I slowly restored from a time machine backup until it stopped working. The culprit was .ssh directory. I put the working .ssh dir back and copied my id’s and config to the working .ssh dir. Public key still worked. Using ls -l and ignoring ACLs the working and non working dirs and files look identical (content and permissions) This smacks of Schrödinger's cat James Lots of noise about public key login ... >> Password-less login to 10.13.6 works for me just fine, >> with the method described above (put your *.pub to the authorized_keys). >> That's the system /usr/sbin/sshd, which is OpenSSH_7.6, LibreSSL 2.6.2. >> Below is a log of such a session, from OpenBSD 6.3 to MacOS 10.13.6. >> >>> hell 40 years experience using unix and I have and do do many many >> >> I'm sure you do do. >> >>>> On 3 Sep 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: >>>> What port? >>> >>> actually openssh which works everywhere ( where works == password-less >>> login NB nothing to do with pass-phrase) does not work on high sierra >> >> In the current port tree, that's OpenSSH 7.6p1r5 (right?). >> Have you tried the same with the system OpenSSH? >> Have you tried with the OpenSSH port built upon the LibreSSL port, >> as opposed to the OpenSSL port? What is the difference? >> >>>>> i usually copy the public key by hand, but I also used ssh-copy-id >>>>> from 1_mac to another >>>>> from 1_mac to itself >>>>> from 1_mac to a plethora of linux machines and virtual machines >>>>> >>>>> 1_mac cannot login passwd-less to another. >>>> To another what? >>> >>> The original post made clear I called the first mac "mac-1" >>> and the second mac “another" >> >> What happens when you try a 10.13.6 server with a different client? >> >>>>> 1_mac CAN login to the linux boxes passwdless >>>>> The logs show nothing of interest >> >> Well, there must be a message about what failed with the keys, right? >> >>> Umm I’m confused. I see a password prompt not a shell prompt. I see too >>> public_key auth failed wthi error 51 before password auth gets tried >> >> So show us the full -v -v log. >> >>> I can see my suspition is not happening >>> which was blank pass phrase is not allowed. >> >> That would be a restriction of the _client_ (which I doubt), >> and the client log would surely say so. > > Thanks to every one for suggestions and help. I’ll stop abusing the list > > > I have two machines upgraded to high sierra (that did work once upon a time) > and one clean install (the machine was formatted ext4 and ran linux). None > work! > > for interest > > [haycorn] /Users/jam [263]% ls -lR .ssh > total 40 > -rw--- 1 jam staff 1014 3 Sep 19:08 authorized_keys > -rw-r--r-- 1 jam staff 130 4 Sep 2017 config > -rw--- 1 jam staff 1679 17 Feb 2018 id_rsa > -rw-r--r-- 1 jam staff 398 17 Feb 2018 id_rsa.pub > -rw-r--r-- 1 jam staff 2342 7 Oct 2016 known_hosts > > [haycorn] /Users/jam [264]% cat .ssh/authorized_keys > ssh-rsa > B3NzaC1yc2EDAQABAAABAQC7Nq44JqKYYGNHMzotos6xmDkeI/2KVKIWcEz36TXqJsZxms39HuTpky5lP56gDnmXdBe8fSDi6ZJbSONZ5sMmS8XG0QqxDQufJIuoQrmgGXFhE8jcrbPAixGhX5fmBOPgFa5JgWDD9caYhpbxTfl2GoAu6Pe0u7paCaMyxD9KNAMk8oBzfkQFU3KMiK+0rB+/UI5lEyAJLCPW2WzFlF8N5iBjocvoDqx2slATfjKPx85VrdS5hVjKHcJjlpgEJ4a5+fcjlpAq/A2AKEQbzXfK1Tpb5PtyhRTIhjDufCZbgSdZlRC8fnm/iDXkwWDmkwCVYhyPAy5P4ecPpihzP6hF > jam@twill > > [haycorn] /Users/jam [265]% > > To high sierra > > [twill] /Users/jam [230]% ssh -vv haycorn.home > OpenSSH_7.6p1, LibreSSL 2.6.2 > debug1: Reading configuration data /Users/jam/.ssh/config > debug1: /Users/jam/.ssh/config line 2: Applying options for * > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 49: Applying options for * > debug2: ssh_connect_direct: needpriv 0 > debug1: Connecting to haycorn.home port 22. > debug1: Connection established. > debug1: identity file /Users/jam/.ssh/id_rsa type 0 > debug1: key_load_public: No such file or directory > debug1: identity file /Users/jam/.ssh/id_rsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /Users/jam/.ssh/id_dsa type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /Users/jam/.ssh/id_dsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: iden
Re: quite OT (James)
Hi All just in case this is the issue, both machines being “up to date”, and it affects others it is not an issue no more noise I promise --- This works (passwd-less login): [pussycat] /Users/mary [501]% sshd --help OpenSSH_7.5p1, LibreSSL 2.5.4 This does not (identical keys and config files) [haycorn] /Users/jam [291]% sshd --help OpenSSH_7.6p1, OpenSSL 1.0.2p 14 Aug 2018 James
Re: nmap
ma > On 5 Sep 2018, at 10:01 pm, Daniel J. Luke wrote: > > On Sep 4, 2018, at 9:46 PM, James Linder wrote: >>> On 5 Sep 2018, at 4:45 am, Daniel J. Luke wrote: >>> On Sep 4, 2018, at 4:39 PM, Ryan Schmidt wrote: >>>> It looks like he's showing us that nmap on his Linux machine found 11 >>>> hosts while on his Mac it only found 6 hosts. >>> >>> maybe? and there a lots of reasons why that might be the case. >> >> Just to be more exact the linux machine is a vm on my mac with a bridged >> network. >> Daniel what can the ‘lots of reasons’ be? > > I can think of many, but it's probably not going to be helpful for you to > enumerate the possible issues as the start of determining what's happening. > > I would probably start with seeing if I can ping all the hosts I expect to be > able to ping from both the linux VM and from the Mac. Daniel thanks. Yup ofcourse I can ping every host, it is a bridged VM. Stephen’s explanation seems very likely. “the the kernel limits ICMP rate" Thanks Steven. James
Re: nmap
> On 5 Sep 2018, at 4:45 am, Daniel J. Luke wrote: > > On Sep 4, 2018, at 4:39 PM, Ryan Schmidt wrote: >> It looks like he's showing us that nmap on his Linux machine found 11 hosts >> while on his Mac it only found 6 hosts. > > maybe? and there a lots of reasons why that might be the case. Just to be more exact the linux machine is a vm on my mac with a bridged network. Daniel what can the ‘lots of reasons’ be? Thanks James
Re: quite OT
... debug1: rekey after 134217728 blocks debug2: key: /Users/jam/.ssh/id_rsa (0x7fb4d5f01360) debug2: key: /Users/jam/.ssh/id_dsa (0x0) debug2: key: /Users/jam/.ssh/id_ecdsa (0x0) debug2: key: /Users/jam/.ssh/id_ed25519 (0x0) debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:/FjP5L3Grrw1P4KXIq5SsfkEy5RWhmeVehgG5+8k5rk /Users/jam/.ssh/id_rsa debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg rsa-sha2-512 blen 279 debug2: input_userauth_pk_ok: fp SHA256:/FjP5L3Grrw1P4KXIq5SsfkEy5RWhmeVehgG5+8k5rk debug1: Authentication succeeded (publickey). Authenticated to sandypit.home ([192.168.5.33]:22). debug1: channel 0: new [client-session] debug2: channel 0: send open debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: exec debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug2: channel_input_open_confirmation: channel 0: callback start debug1: No xauth program. Warning: No xauth data; using fake authentication data for X11 forwarding. debug1: Requesting X11 forwarding with authentication spoofing. debug2: channel 0: request x11-req confirm 1 debug2: fd 5 setting TCP_NODELAY debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug1: Sending environment. debug1: Sending env LANG = en_AU.UTF-8 debug2: channel 0: request env confirm 0 debug2: channel 0: request shell confirm 1 debug2: channel_input_open_confirmation: channel 0: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel_input_status_confirm: type 99 id 0 debug2: X11 forwarding request accepted on channel 0 debug2: channel_input_status_confirm: type 99 id 0 debug2: PTY allocation request accepted on channel 0 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: shell request accepted on channel 0 Last login: Tue Sep 4 19:51:13 2018 from 192.168.5.61 Have a lot of fun... [sandypit] /home/jam [587]% So I’ll carefully read all the replies James
Re: no longer quite OT
> On 3 Sep 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > > System Settings -> Sharing -> Remote Access > > ...or something close to that will dis/enable native sshd in OSX (not on my > laptop, so may be a wee bit imprecise). > >> On Sep 2, 2018, at 10:04 PM, James mailto:j...@tigger.ws>> >> wrote: >> >> Hi All >> since I’ve been unable to solve passwd-less login on High Sierra I installed >> port openssh. >> >> All good except I have two daemons waiting on port 22. I can easily find >> the LaunchDaemon for openssh but I cannot fathom how apple run their ssh >> daemon, or even what it is called. >> >> I miss linux’s netstat -anp. Bill thanks, obvious answer Richard thanks for teaching me stuff about lsof James
Re: quite OT
Top Posting as all the noise below may be of interest, but it may not be. Actually re-reading my post shows my irritation with Jan’s post. I guess that I’m here because of a significant and so far insoluable problem and I welcome any ideas or caveats, I think his tone trivializes my angst, appologies! Jan I must assume that you have never done a password-less login to a high sierra machine and the tone of your questions betrays that. I have mumble (aah hell 40 years experience using unix and I have and do do many many password-less logins eg gathering data frrom an embedded logger) so the stock right-way is cute, but moot > On 3 Sep 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> but directly related to a port > > What port? actually openssh which works everywhere ( where works == password-less login NB nothing to do with pass-phrase) does not work on high sierra > >> I want password-less ssh login > > Create a password-less key and copy it into > ~/.ssh/authorized_keys on the remote site. > > Make sure that ~/.ssh is chmod 700 and authorized_keys is chmod 600 > if you are creating them from scratch. (The OS possibly did that for you > upon user creation.) > >> i usually copy the public key by hand, but I also used ssh-copy-id >> from 1_mac to another >> from 1_mac to itself >> from 1_mac to a plethora of linux machines and virtual machines >> >> 1_mac cannot login passwd-less to another. > > To another what? The original post made clear I called the first mac "mac-1" and the second mac “another" > What happens if you copy the key by hand, not relying on ssh-copy-id? > Have you checked that the key is actually installed there? By hand and with ssh-copy-id achieves identical results. I’ve also generated id_rsa and id_rsa.pub on linux machines (In case apple does something bizare) >> Passwd is requested then all is well. > > What password, if it's a password-less key? if public key auth fails then you fall back to password auth >> 1_mac CAN login to itself passwdless And with openssh that happens too. I’ve not tried user a login to user b, I shall try in the morning >> 1_mac CAN login to the linux boxes passwdless >> >> The logs show nothing of interest (-vvv, not tried to get server logs yet) > > You have succesfully logged in. The logs will say so. > What else do you expect to see there? Umm I’m confused. I see a password prompt not a shell prompt. I see too public_key auth failed wthi error 51 before password auth gets tried >> Google is full of stuff, eg since High Sierra Apple silently enforces a 2048 >> bit key, but nothing that actually solves the problem > > What problem? Again u. Password-less login. I can see my suspition is not happening which was blank pass phrase is not allowed. > On Sep 01 17:45:13, d...@horsfall.org <mailto:d...@horsfall.org> wrote: >>> I want password-less ssh login >>> i usually copy the public key by hand, but I also used ssh-copy-id >> >> I've done that, but I think it involved temporarily enabling TELNET etc, >> then ye olde copy/paste of the public key. > > Why would you use TELNET to transfer your ssh key? > To completely defeat the purpose? I think one of the answers mentioned telnet, I certainly did not. James
no longer quite OT
Hi All since I’ve been unable to solve passwd-less login on High Sierra I installed port openssh. All good except I have two daemons waiting on port 22. I can easily find the LaunchDaemon for openssh but I cannot fathom how apple run their ssh daemon, or even what it is called. I miss linux’s netstat -anp. Can anyone help thanks James
nmap
Hi All still in pursuit of passwd-less logins to High Sierra. Here fire is a VM on haycorn with bridged network (VirtualBox) [fire] /home/jam [1798]% cat /etc/issue Ubuntu 18.04.1 LTS \n \l haycorn is my high sierra machine [fire] /home/jam [1804]% nmap --help Nmap 7.60 ( https://nmap.org ) [haycorn] /Users/jam [182]% nmap --help Nmap 7.70 ( https://nmap.org ) [fire] /home/jam [1796]% nmap -sP 192.168.5.1-254 |grep -v Host Starting Nmap 7.60 ( https://nmap.org ) at 2018-09-03 11:11 AWST Nmap scan report for _gateway (192.168.5.1) Nmap scan report for haycorn.home (192.168.5.31) Nmap scan report for sandypit.home (192.168.5.33) Nmap scan report for fire.home (192.168.5.36) Nmap scan report for 192.168.5.99 Nmap scan report for ws103.home (192.168.5.103) Nmap scan report for ws108.home (192.168.5.108) Nmap scan report for printer.home (192.168.5.180) Nmap scan report for gold.home (192.168.5.182) Nmap scan report for fibaro.home (192.168.5.197) Nmap scan report for divectl.home (192.168.5.200) Nmap done: 254 IP addresses (11 hosts up) scanned in 5.22 seconds [fire] /home/jam [1797]% exit logout Connection to fire closed. [haycorn] /Users/jam [184]% nmap -sP 192.168.5.1-254 |grep -v Host Starting Nmap 7.70 ( https://nmap.org ) at 2018-09-03 11:11 AWST Nmap scan report for 192.168.5.1 Nmap scan report for haycorn.home (192.168.5.31) Nmap scan report for sandypit.home (192.168.5.33) Nmap scan report for 192.168.5.99 Nmap scan report for printer.home (192.168.5.180) Nmap scan report for fibaro.home (192.168.5.197) Nmap done: 254 IP addresses (6 hosts up) scanned in 5.23 seconds It seems the port of nmap is quite different to linux nmap. What is happening Thanks James
quite OT
but directly related to a port Where can I ask questions on mac stuff? I elaborate: I want password-less ssh login i usually copy the public key by hand, but I also used ssh-copy-id from 1_mac to another from 1_mac to itself from 1_mac to a plethora of linux machines and virtual machines 1_mac cannot login passwd-less to another. Passwd is requested then all is well 1_mac CAN login to itself passwdless 1_mac CAN login to the linux boxes passwdless The logs show nothing of interest (-vvv, not tried to get server logs yet) Google is full of stuff, eg since High Sierra Apple silently enforces a 2048 bit key, but nothing that actually solves the problem Surely someone somewhere has solved the issue And I don’t which way to turn, clearly some apple magic is happening James
Re: vnc
> On 25 Jul 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> What exactly is your question ? The macPorts build of cotvnc is 64-bit and >> no warnings are offered running it. > > Agreed. I use cotvnc all the time and I've seen no problems with it on High > Sierra so far. Actually I use the cotvnc-devel port, to get the latest > development version. My question was exactly what Ryan answered. Thanks Ryan. I installed and everything is perfect. James
Re: vnc
> On 24 Jul 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> For ages I have used Chicken but High Sierra warns me of it being a 32bit >> app. >> macports has cotvnc and also vnc >> Any opinio,ns sage words or other > > Usually I use the builtin VNC client of macOS. You can launch it by > opening a vnc:// URL from Finder's "Connect to Server" dialog or with > open(1) from a terminal window, for example: > , > open vnc://hostname:5190 > Alas the built-in server does not play nicely with the other kids Conmection failed to ‘sandypit.home' Make sure Screen Sharing or Remote Management (in the Sharing section of System Preferences) is enabled on the remote computer. One of my linux boxes running xvnc Chicken DOES connect James
vnc
For ages I have used Chicken but High Sierra warns me of it being a 32bit app. macports has cotvnc and also vnc Any opinions sage words or other Thanks James PS Chicken means ‘Chicken of the VNC’ and cotvnc is a port of it. I assume one can build it in 64bit mode
Re: macports-users Digest, Vol 138, Issue 15
> On 20 Feb 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> This happens recurrently to me, usually after significant updates. >> >> The last time was some months ago, so I forget exactly what I did, but it >> involved the location of xauth and the ssh config on the target machine, if >> I recall correctly. >> >> So that's where I would start to google, (and will, the next time I have >> this issue). >> >> I hope this helps. >> >> Ken >> >> >> On 2018-02-16, at 10:33 AM, Gustavo Seabra wrote: >> >>> Hi all, >>> >>> I understand this may not be a real Macports problem, but I suspect someone >>> here may know the solution. I have googled a bit about this, but the >>> solutions I found do not really apply to that problem. Here it is: >>> >>> I have 3 machines: >>> >>> A: My Mac >>> B: A Unix machine that serves as firewall to other computers >>> C: The computer I want to access. >>> >>> SO, If I do: >>> >>> A]$ ssh -Y B >>> B]$ echo $DISPLAY >>> localhost:10.0 >>> B]$ xmgrace >>> >>> I get a nice window from xmgrace, as expected. >>> >>> However, If I try to open xmgrace from C using B as a jump, I get: >>> >>> A]$ ssh -Y B >>> B]$ echo $DISPLAY >>> localhost:10.0 >>> B]$ ssh -Y C >>> C]$ echo $DISPLAY >>> localhost:10.0 >>> C]$ xmgrace >>> Can't open display >>> Failed initializing GUI, exiting >>> C]$ >>> >>> I suspect there’s something ill-configured in C, but don’t know what could >>> it be or where to look. Could someone there please help me here? I found a bunch of X11 localhost configs in /etc/ssh/ssh_config that can/must be changed. My 27” takes long for the first connection My laptop is always fast James
