GDB fails to build on High Sierra (fwd)
Anyone? -- Dave -- Forwarded message -- Date: Fri, 6 Sep 2024 07:54:18 +1000 (AEST) From: Dave Horsfall To: macports-users Subject: GDB fails to build on High Sierra (fwd) Re-submitted, this time with a compressed main.log... -- Dave -- Forwarded message -- Date: Fri, 6 Sep 2024 07:40:10 +1000 (AEST) From: Dave Horsfall To: macports-users Subject: GDB fails to build on High Sierra On the off-chance that this is a known problem with a known fix... MacBook Pro (13-inch, Mid 2010), running High Sierra 10.13.6 Karks it around here (building zlib): :info:build fatal error: error in backend: Cannot select: intrinsic %llvm.x86.sha1rnds4 :info:build clang: error: clang frontend command failed with exit code 70 (use -v to see invocation) I see no point in submitting a bug report to Apple as this is an obsolete system... The main.log is attached. -- Dave main.log.gz Description: main.log.gz
GDB fails to build on High Sierra (fwd)
Re-submitted, this time with a compressed main.log... -- Dave -- Forwarded message -- Date: Fri, 6 Sep 2024 07:40:10 +1000 (AEST) From: Dave Horsfall To: macports-users Subject: GDB fails to build on High Sierra On the off-chance that this is a known problem with a known fix... MacBook Pro (13-inch, Mid 2010), running High Sierra 10.13.6 Karks it around here (building zlib): :info:build fatal error: error in backend: Cannot select: intrinsic %llvm.x86.sha1rnds4 :info:build clang: error: clang frontend command failed with exit code 70 (use -v to see invocation) I see no point in submitting a bug report to Apple as this is an obsolete system... The main.log is attached. -- Dave main.log.gz Description: main.log.gz
Re: XV and GV hanging
On Thu, 5 Sep 2024, Ken Cunningham wrote: > 1. Do you have an X11 server installed? Look in /Applications/MacPorts > for it. Mine is called X11.app. Yep. > 2. Does it run if you double click it? Yep. > 3. If it does run, open an xterm terminal from the "Applications" menu > in the X11.app. (you obviously do need xterm installed for it to open). Hmmm... Nope (and neither does "xlogo" nor "xman" from that menu. > 4. If xterm does open -- try running your xeyes or other x11 > applications from the xterm terminal. That often works even when the > Terminal application won't open them. Looks like X11 is well and truly nobbled (but as I said it used to work). > NB having two different X11 infrastructures installed, eg MacPorts X11 > and another one like XQuartz or Apple's X11 infrastructure, is just a > recipe for disaster. Many folks have solved their X11 headaches by > stripping out everything except the one they want (usually the MacPorts > one is the one you want). Agreed; is there a way to get things to build with XQuartz, or will that "just work" if I blow away X11 without dragging it in? -- Dave
Re: XV and GV hanging
On Thu, 5 Sep 2024, Chris Jones via macports-users wrote: > p.s. As much as you probably want to fix your X11 server, you do not > need it just to print a file. > > Install ghostscript, use 'ps2pdf' to convert the file to PDF then just > open that and print it using the standard OS tools. Bingo! I can live without X11 for the time being (I'll get back to GDB later, and see where the hangup is), but I really want my man pages... Thanks! -- Dave
Re: XV and GV hanging
On Thu, 5 Sep 2024, Chris Jones via macports-users wrote: > Sounds like you have an issue with your X11 server, as these > applications are perhaps hanging at the point they are waiting for it to > start up. Sounds about right (it used to work). > 1. Does it automatically start if you run a very basic X11 application, > like xeyes ? > > > sudo port install xeyes > > xeyes > > If that does not trigger the X11 server to start, then the issue is with > that. It hangs as well... > 2. can you manually start the X11 server instead of relying on the > automatic startup via the DISPLAY socket ? I ran "startx", and the applications still hang. I even rebooted the Mac (it was up for nearly 3 weeks!), to no effect. I took a coredump of one process (with CTL-\) and then found that GDB won't compile (a separate issue which I'm looking at -- it used to work too)... -- Dave
XV and GV hanging
13" mid-2010 MacBook Pro, running High Sierra 10.13.6. Did a graphics library change recently, and broke something? Both XV and GV are now hanging on startup, with no output; I don't know where to start with this. Hmmm... GIMP is also hanging? My needs are simple: I am trying to print a PS file produced by "man -t" on another box. Thanks. -- Dave
2.10.0 looks OK
No trouble upgrading on this ancient MBP running High Sierra. -- Dave
Re: C++ exception handling on PPC with gcc 6.4.0 doesn't work
In this case, I was running Unify (an old RDBMS) on a 386, and it kept failing in mysterious ways. So, I bought a book on programming the 386 (ugh!), inspected the assembler code before and after "-O", and noticed that a crucial instruction had been optimised right out of existence... Hey, who needs that floating point ADD instruction? I've already done it! I've never trusted optimisers since... On Wed, 26 Jun 2024, Richard L. Hamilton wrote: > Optimizers definitely are not perfect. Making alterations for efficiency that > are always identical in well defined meaning to the original code is bound to > be difficult to get right. Think of it as a challenge on the order of > translating poetry in a way that preserves all of meaning, tension/pacing, > and rhyme; sometimes that's not possible because poetry overloads language > with all those attributes at once, and you may have to degrade one in > translation to preserve the others. > > And in your example, I think it probably is the optimizer at fault (I didn't > read up on everything necessary to be sure, but it's such a simple example > that it seems likely). > > But C and C++ have situations where something is not strictly a syntax error > in the language but results in undefined (and possibly inconsistent!) > behavior, that the compiler may not even warn you about. You may tend to get > away with more of that without the optimizer than with; but that sort of > issue, if you track it down and rewrite to avoid the undefined behavior, is > likely to work properly with or without optimizer. At least some of these are > arguably faults in the standard(s), but some may be allowed to keep compiler > implementations from being prohibitively difficult. > > There is some interesting discussion of related subjects out there. > > https://stackoverflow.com/questions/7237963/is-there-a-c-implementation-that-detects-all-undefined-behavior#:~:text=However%2C%20it%20is%20possible%20to,the%20code%20has%20undefined%20behavior. > > has some, and some links to promising resources. I haven't investigated > deeply, nor am sure I even understand it all, but its something to think > about. > > Ancient CPUs had less issues. But modern CPUs for efficiency and capability > have multiprocessing, multithreading, memory caches (which in combination > with multiple CPU chips may require extra hardware effort to be kept > consistent), branch prediction, sometimes out-of-order execution, and other > behaviors that if care is not taken, lead to inconsistent results. > > If you need absolutely exact behavior, you probably need to understand your > CPU and code in assembler; esp. if you need exact timing (insofar as that's > even possible on a modern CPU, where instruction times may depend on whether > an addressed value is in cache). Or at the very least, have read not only the > relevant language standard but any implementation specific compiler notes. > > > On Jun 25, 2024, at 23:01, Dave Horsfall wrote: > > > > On Tue, 25 Jun 2024, Andreas Falkenhahn wrote: > > > > [...] > > > >> So the good news is that I've found a workaround. Turning the optimizer > >> off will make exceptions work again but the bad news is that of course > >> it looks like there is some major issue in the optimizer because > >> enabling it seems to break exceptions... > > > > I've overcome all sorts of obscure problems by simply turning off the > > optimiser; face it: do you really want some unknown third party mucking > > around with your carefully-crafted algorithm? > > > > -- Dave > > > > > -- Dave
Re: C++ exception handling on PPC with gcc 6.4.0 doesn't work
On Tue, 25 Jun 2024, Andreas Falkenhahn wrote: [...] > So the good news is that I've found a workaround. Turning the optimizer > off will make exceptions work again but the bad news is that of course > it looks like there is some major issue in the optimizer because > enabling it seems to break exceptions... I've overcome all sorts of obscure problems by simply turning off the optimiser; face it: do you really want some unknown third party mucking around with your carefully-crafted algorithm? -- Dave
Re: Preventing other software from linking against MacPorts libraries
> > Sometimes I just end up deleting /opt/local to get it to build and > > then re-install MacPorts, which can be painful or at least tiresome. The question has since been answered, but what was wrong with merely renaming /opt/local temporarily? That's what I would've done... -- Dave
Re: what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?)
On Thu, 11 Apr 2024, Kenneth Wolcott wrote: > Interesting...I've been using Emacs for years and this file suddenly > appears for the first time. Hmm...I don't even know how to use tags in > emacs...I'll look in the emacs manual. Must have been some key I pressed > by accident... EMACS: Esc Meta Alt Ctl Shift :-) -- Dave
Re: MacPorts 2.9.3 has been released
On Mon, 8 Apr 2024, Dave Horsfall wrote: > Smooth as usual on this ancient box... Thanks, all. And I've just realised that everything was installed from packages this time; I was wondering why it only took a quarter of an hour... -- Dave
Re: MacPorts 2.9.3 has been released
Smooth as usual on this ancient box... Thanks, all. -- Dave
Re: MacPorts 2.9.3 has been released
On Thu, 4 Apr 2024, Joshua Root wrote: > The MacPorts Project is pleased to announce the release of version > 2.9.3. This is a bugfix release with small changes only. See the > ChangeLog [1] for the list of changes. [...] I hadn't got around to installing 2.9.2 yet (I do those admin tasks on Mondays); will 2.9.3 drop cleanly onto 2.9.1? I ask because I got bitten by a Linux upgrade; apparently Debian (if not all of them) requires all intermediate upgrades be performed... -- Dave
Re: ld: can't write output file for architecture ppc
On Mon, 18 Mar 2024, raf via macports-users wrote: > I've been told that macports needs to be selfupdated at least annually. > If it's been too long between selfupdates, it can fail (It did for me > once on 10.6.8). You might need to reinstall macports instead of > selfupdate. Annually? Yikes; I run it weekly... -- Dave
Building "poppler" failed
High Sierra 10.13.6 on ancient MBP. Doing my weekly "port upgrade outdated", it went belly-up here: - ---> Building poppler Error: Failed to build poppler: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_poppler/poppler/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. ---> Some of the ports you installed have notes: libomp has the following notes: To use this OpenMP library: * For clang-3.8+, or clang-3.7 with +openmp variant: add "-fopenmp" during compilation / linking. * For clang-3.7 without +openmp variant, use: "-I/opt/local/include/libomp -L/opt/local/lib/libomp -fopenmp" libpsl has the following notes: libpsl API documentation is provided by the port 'libpsl-docs'. Mon Mar 11 06:41:15 AEDT 2024 bash-3.2% locate charconv /opt/local/include/gcc/c++/bits/charconv.h /opt/local/include/gcc/c++/charconv /opt/local/include/libcxx/v1/charconv - The main.log is attached (and I have no idea what "poppler" is). Thanks. -- Dave main.log Description: main.log
Re: [MacPorts-announce] MacPorts 2.9.0 has been released
On Wed, 24 Jan 2024, Joshua Root wrote: > The MacPorts Project is happy to announce that the 2.9.0 version has now > been released. It is available via the usual methods: [...] Smooth as usual, on this ancient MBP w/ High Sierra; well done, all. -- Dave
Re: Can't build "mpv"
On Sun, 24 Dec 2023, Ryan Schmidt wrote: > That log doesn't seem to say much, other than that the real error may be > in the file meson-log.txt. Aha; thanks. I couldn't see the wood for the trees... meson-log.txt: --- stderr --- env: python3: No such file or directory Hmmm... Looks like I lost python3 somehow; well, it's not urgent, so it can wait. Thanks again. -- Dave
Can't build "mpv"
MacBook Pro (13-inch, Mid 2010), High Sierra 10.13.6. Dunno what it is so it must be a dependency of something, but it fails with: :info:configure meson.build:1474:21: ERROR: Command `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/work/mpv-0.37.0/TOOLS/macos-sdk-version.py` failed with status 127. It's so verbose that I can't figure out what's wrong; the "main.log" is attached. Thanks. -- Dave---> Computing dependencies for mpv ---> Fetching archive for mpv ---> Attempting to fetch mpv-0.37.0_0+audiocd+bluray+bundle+dvd+libarchive+network+opengl+osd+python311+rubberband.darwin_17.x86_64.tbz2 from http://packages.macports.org/mpv ---> Attempting to fetch mpv-0.37.0_0+audiocd+bluray+bundle+dvd+libarchive+network+opengl+osd+python311+rubberband.darwin_17.x86_64.tbz2 from http://kmq.jp.packages.macports.org/mpv ---> Attempting to fetch mpv-0.37.0_0+audiocd+bluray+bundle+dvd+libarchive+network+opengl+osd+python311+rubberband.darwin_17.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/mpv ---> Fetching distfiles for mpv ---> Attempting to fetch mpv-0.37.0.tar.gz from http://distfiles.macports.org/mpv ---> Verifying checksums for mpv ---> Extracting mpv ---> Applying patches to mpv ---> Configuring mpv Error: Failed to configure mpv: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/work/build/meson-logs/meson-log.txt Error: Failed to configure mpv: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Re: Sonoma support?
On Tue, 26 Sep 2023, Chris Jones wrote: > B.t.w. Ryan sent a detailed email on this very point only last week. > Please go back read the thread “ Timing of MacPorts Support for New > macOS Versions” before posting any further follow up questions. Odd; I never saw it... Anyone else not see it? -- Dave
Re: would like to download the source of a port, but not install it (I already have installed it)
On Sat, 1 Jul 2023, Kenneth Wolcott wrote: > How to just download the source of a port? [...] "port fetch"? fetch Fetches the distribution files required to build portname. -- Dave
Re: Cannot build glib2
On Mon, 24 Apr 2023, Dave Horsfall wrote: > [ Disabling "+universal" ] > > Yes, that seems to be it; thanks. Now, is there a way to globally > disable "universal" without cleaning every port and rebuilding with > "-universal"? Anyone? -- Dave
Re: sockstat
On Fri, 12 May 2023, André-John Mas wrote: > I was looking for it based on a stack overflow article, indicating how to > check a server I’d is responding on a given port. > Previously I was using telnet for this. Will "nmap" do what you want? It's in MacPorts. -- Dave
Re: How can I restore /opt/local from time machine backup drive?
On Sat, 29 Apr 2023, Tao Zhang wrote: > I want to follow the following procedure to restore /opt/local to > previous date from time machine external drive, > > but I get “Time Machine” can’t be modified or deleted because it’s > required by macOS." error message after I click "restore" button. > > Do you know how to fix it? That would make sense because Time Machine is active at the time; the only way that I've been able to restore files outside my home directory is by logging off then on again as "root" (you may need to enable "root" or something) then bringing up Time Machine. Of course, I wasn't trying to restore TM at the time... I'd be interested in the answer from more knowledgeable people than me. -- Dave
Re: Cannot build glib2
On Sun, 16 Apr 2023, Richard L. Hamilton wrote: > That may mean you tried to install glib2 with +universal but did not > previously install dbus with +universal. Or something like that which > has similar results. [...] Yes, that seems to be it; thanks. Now, is there a way to globally disable "universal" without cleaning every port and rebuilding with "-universal"? -- Dave
Cannot build glib2
Early MacBook Pro (13", mid 2010), High Sierra 10.13.6 (as far as it will go). When doing my weekly port upgrade, it bombs out with: ---> Building glib2 Error: Failed to build glib2: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log for details. I see a lot of warnings in main.log such as: :info:build ld: warning: The i386 architecture is deprecated for macOS (remove from the Xcode build setting: ARCHS) Is this some insidious attempt by Cupertino to force me to buy an M series? Compressed main.log attached. -- Dave main.log.gz Description: main.log.gz
Re: Global variants
On Mon, 6 Mar 2023, chrischa...@gmx.us wrote: > https://guide.macports.org/chunked/internals.configuration-files.html#internals.configuration-files.variants-conf Many thanks! Dunno how I missed that :-( -- Dave
Global variants
Is there a way to get a variant to apply globally? I'm thinking of "+nonfree" as I find the GPL to be too restrictive (personally I use a modified FreeBSD licence for my own stuff). Thanks. -- Dave
Re: MacPorts 2.8.1 has been released
On Tue, 31 Jan 2023, Joshua Root wrote: > The MacPorts Project is pleased to announce the release of version > 2.8.1. This is a bugfix release with small changes only. See the > ChangeLog [1] for the list of changes. Smooth as a baby's bottom on High Sierra; many thanks. -- Dave
Re: PortIndex file corrupt?
On Mon, 23 Jan 2023, Joshua Root wrote: > That's the thing - the bug only affects reclaim when it runs > automatically as part of the same command as sync or selfupdate. Your > PortIndex was never actually corrupt on disk, it just isn't reloaded > correctly in that specific situation. That's why I always answer "no" to the question about reclaiming, then run it by hand afterwards; isn't it time that this bug was fixed? It's been raised here several times now. -- Dave
Re: Is there a "telnetd" in MacPorts?
On Mon, 2 Jan 2023, Eric Borisch wrote: > Looks like 'inetutils +server' should do it? Bingo! I really must get the hang of variants... Many thanks. -- Dave
Is there a "telnetd" in MacPorts?
Yes, I know the risks, but I don't want to use "brew" (which short of compiling from sources appears to be the only other option). Thanks. -- Dave
"enscript" no longer working (fwd)
Anyone? I'm guessing that an update to a library broke something... -- Dave -- Forwarded message -- Date: Mon, 19 Dec 2022 12:44:47 +1100 (EST) From: Dave Horsfall To: macports-users Subject: "enscript" no longer working MacPorts 2.8.0 on High Sierra. Has anyone else found that "enscript" has stopped working after some software update or other? The symptom is that nothing is being printed, although I can redirect the output to a file and print that instead so it's obviously generating the correct PS output. The installed version of "enscript" is 1.6.6, and reinstalling it makes no difference; when I specify a dummy script in place of "lpr" it gets invoked as it should, so the spawning mechanism seems to be OK. Because it's a bit inconvenient to disable SIP right now I cannot trace the thing to see exactly what's broken, so has anyone else noticed this and can track it to a particular MP update? Thanks. -- Dave
"enscript" no longer working
MacPorts 2.8.0 on High Sierra. Has anyone else found that "enscript" has stopped working after some software update or other? The symptom is that nothing is being printed, although I can redirect the output to a file and print that instead so it's obviously generating the correct PS output. The installed version of "enscript" is 1.6.6, and reinstalling it makes no difference; when I specify a dummy script in place of "lpr" it gets invoked as it should, so the spawning mechanism seems to be OK. Because it's a bit inconvenient to disable SIP right now I cannot trace the thing to see exactly what's broken, so has anyone else noticed this and can track it to a particular MP update? Thanks. -- Dave
Re: High Sierra
On Sat, 17 Dec 2022, James wrote: > 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 I used https://developer.apple.com/download/more/ to get Xcode and the tools for High Sierra on my old MacBook Pro. -- Dave
Why would Kreversi want a spell checker?
MacBook Pro 13", mid 2010; High Sierra 10.13.6. Kreversi is an implementation of the board game "reversi", but it fails with: # port install kreversi ---> Computing dependencies for kreversi Error: Can't install aspell because conflicting ports are active: ispell Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port kreversi failed No error log that I can see, but why on earth would a spell checker be required for a simple board game? Is it because of KDE (ugh!) itself? -- Dave
MacPorts upgrade OK
High Sierra on an ancient MacBook Pro. No problems whatsoever, not even the one mentioned recently; I hope I haven't overlooked something... -- Dave
Re: ports.tar corrupt?
On Mon, 17 Oct 2022, raf via macports-users wrote: [...] > I get the same messages on macos-10.6.8 when doing "port selfupdate && > port upgrade outdated and not MacVim" and I say yes to reclaiming. But > if I say no, and reclaim separately, it's fine. Aha... I've always answered "Y", so I'll give that way a go. > It doesn't happen for me on macos-10.14.6. Unfortunately I'm stuck on 10.13.6... -- Dave
ports.tar corrupt?
I don't know what it is with MacPorts and me, but here's the latest problem; when doing my weekly "port upgrade outdated" I get: Warning: Port cairo not found: Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt. Etc. How do I fix that? Thanks. -- Dave
Cannot build graphene (fwd)
Anyone?
-- Dave
-- Forwarded message --
Date: Mon, 10 Oct 2022 08:48:28 +1100 (EST)
From: Dave Horsfall
To: macports-users
Subject: Cannot build graphene
Early MacBook Pro, High Sierra.
When building graphene, it bails out with:
Error: Failed to destroot graphene: graphene-gobject-1.0.pc differs in
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-i386//opt/local/lib/pkgconfig
and
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-x86_64//opt/local/lib/pkgconfig
and cannot be merged
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/main.log
for details.
The diffs are:
diff -r
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-i386//opt/local/lib/pkgconfig/graphene-1.0.pc
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-x86_64//opt/local/lib/pkgconfig/graphene-1.0.pc
5c5
< graphene_has_sse2=0
---
> graphene_has_sse2=1
17c17
< Cflags: -I${includedir}/graphene-1.0 -I${libdir}/graphene-1.0/include
---
> Cflags: -I${includedir}/graphene-1.0 -I${libdir}/graphene-1.0/include
-mfpmath=sse -msse -msse2
diff -r
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-i386//opt/local/lib/pkgconfig/graphene-gobject-1.0.pc
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-x86_64//opt/local/lib/pkgconfig/graphene-gobject-1.0.pc
4c4
< graphene_has_sse2=0
---
> graphene_has_sse2=1
I have no idea how to fix this, if it's my fault; I am not compiling with
+universal and no amount of "port clean" etc will work, so it would appear
to be a fundamental error (and I don't like filing dud bug reports).
The main.log is attached.
-- Dave
main.log.gz
Description: main.log.gz
Cannot build graphene
Early MacBook Pro, High Sierra.
When building graphene, it bails out with:
Error: Failed to destroot graphene: graphene-gobject-1.0.pc differs in
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-i386//opt/local/lib/pkgconfig
and
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-x86_64//opt/local/lib/pkgconfig
and cannot be merged
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/main.log
for details.
The diffs are:
diff -r
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-i386//opt/local/lib/pkgconfig/graphene-1.0.pc
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-x86_64//opt/local/lib/pkgconfig/graphene-1.0.pc
5c5
< graphene_has_sse2=0
---
> graphene_has_sse2=1
17c17
< Cflags: -I${includedir}/graphene-1.0 -I${libdir}/graphene-1.0/include
---
> Cflags: -I${includedir}/graphene-1.0 -I${libdir}/graphene-1.0/include
-mfpmath=sse -msse -msse2
diff -r
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-i386//opt/local/lib/pkgconfig/graphene-gobject-1.0.pc
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphene/graphene/work/destroot-x86_64//opt/local/lib/pkgconfig/graphene-gobject-1.0.pc
4c4
< graphene_has_sse2=0
---
> graphene_has_sse2=1
I have no idea how to fix this, if it's my fault; I am not compiling with
+universal and no amount of "port clean" etc will work, so it would appear
to be a fundamental error (and I don't like filing dud bug reports).
The main.log is attached.
-- Dave
main.log.gz
Description: main.log.gz
Re: Port upgrade outdated
On Wed, 5 Oct 2022, Lenore Horner wrote: > Maybe I misunderstood Raoul's post. > What I see at the end of > port install blah > is a list of ports that will also have to be installed and the line > Continue? [Y/n]: > This suggests to me that the response is case sensitive. Nope; it's saying that "Y" is the default. -- Dave
Re: Does the migration procedure keep ports versions?
On Thu, 29 Sep 2022, chilli.names...@gmail.com wrote: [...] > When HS was first released, I swear it wasn't supported on 2010, and > there was the typical expected uproar from customers, and a High Sierra > patcher tool was quickly released by an independent developer > (possibly http://dosdude1.com/software.html ) allowing models back to > 2008 to install it, But according to MacTracker, High Sierra is > supported on 2010 MBP. Maybe I had it wrong, maybe Apple had a change > of heart. Interesting; I didn't have to use that tool, as it "just worked" and my local Mac shop (from whom I bought my 2nd-hand MBP) recommended Sierra only. But I wanted to use Garage Band etc. Apple is trying to force me (a pensioner) to buy the very latest, but I don't see them contributing towards the cost... -- Dave
Re: Does the migration procedure keep ports versions?
On Thu, 29 Sep 2022, chilli.names...@gmail.com wrote: > The initial reported spec, "a High Sierra MBP," is ambiguous. That could > mean a 2010 MBP, that can be updated up to High Sierra with a third > party enabler, or more likely Ces VLC meant that the machine's original > and default OS from Apple was High Sierra, indicating a 2018 model, > which is still supported by Apple up to current, or Ventura. Odd; mine is a mid-2010, and I just installed it without an "enabler" (whatever that is). I do have the occasional problem though, since Sierra is recommended for this model; I needed HS to run some applications that I wanted i.e. all the old ones that I installed under Sierra and have disappeared from the store. > https://en.wikipedia.org/wiki/MacOS_version_history#Releases Yes, I think that's the one. > Anyway, while the names of all the macOS versions are so very cute, they > inevitably waste my time because I always have to double check the name > against the actual OS version number, which is the detail that matters. > Up to Lion, I had them memorized. Since then I have resisted learning > them all because Apple aggravatingly increased its OS release cycle and > feature creep to yearly. I honestly wish there were two releases, one > that included new features, and one that didn't require disabling all > the unwanted and unnecessary new features. That is indeed annoying; they must be catering to a certain demographic, like Penguin/OS. At least FreeBSD sticks to version numbers which I have no trouble remembering and are easily compared. -- Dave
Re: Does the migration procedure keep ports versions?
On Thu, 29 Sep 2022, Ces VLC wrote: > I'm planning an update of a High Sierra MBP up to Monterey [...] The MPP won't go beyond High Sierra (I've tried); there is a chart somewhere showing the supported releases. -- Dave
Re: Can I disable progress bars?
On Thu, 22 Sep 2022, Clemens Lang wrote: > port upgrade outdated | cat > > This makes stdout a pipe rather than a tty and thus invalidates the > first condition. One of the few valid uses for "| cat" :-) -- Dave
Cannot build DOSBOX
Sigh; it never rains but it pours... Trying to build DOSBOX I get: ---> Computing dependencies for dosbox Error: Cannot install dosbox for the arch 'i386' because Error: its dependency libsdl does not build for the required arch by default Error: and the configured universal_archs '' are not sufficient. macports.conf: # Space-delimited list of CPU architectures to target when building # universal. Defaults to "i386 ppc" on Mac OS X 10.5 and earlier, # "x86_64 i386" on Mac OS X 10.6 through macOS 10.13, "x86_64" on # macOS 10.14 and 10.15 (these SDKs are not universal), and # "arm64 x86_64" on macOS 11 and later. Set an empty value to disable # universal building. #universal_archsx86_64 i386 universal_archs Should I hardwire it to those? I ain't likely to use PPC etc. I vaguely remember seeing the same thing with WINE and was going to report it. -- Dave
Re: Unable to build XV
On Sun, 18 Sep 2022, Bill Cole wrote: > > And because XV is broken I can't continue with upgrading following > > ports > > You can get around that by explicitly excluding xv, e.g.: > > port -v upgrade active and not xv Thanks; I must get used to those logical conditions (FreeBSD ports has no such feature). Now have a problem with dosbox (seems that "universal_archs" isn't) which I'll post next; it's likely my fault, and I don't want to contaminate the bugs database with spurious reports. -- Dave
Re: Unable to build XV
On Sun, 18 Sep 2022, Richard L. Hamilton wrote: > I worked around the existing broken xv binary using a symlink for the > library (which if it all gets fixed, I’ll remove by hand as I created it > by hand). [...] Your workaround works fine; thanks! I made a Calendar entry to remind me. I'm not sure whether to file a bug report for that doubly-defined function or just keep using the existing one; it works, after all (once I'd installed the symlink). Damned chimpanzees who think they're programmers... And because XV is broken I can't continue with upgrading following ports (even with "-f", which used to work). -- Dave
Re: Unable to build XV
On Sun, 18 Sep 2022, Richard L. Hamilton wrote: > I’ve not only seen that across various macOS versions, but something > else broke the existing xv because one of the ports the older version > depended on changed where it keeps some libraries. Specifically, the > older version of xv expects [..] Grumble... So I see :-( I like XV (been using it since SunOS) so I'll try your fix. -- Dave
Unable to build XV
Mid-2010 MacBook Pro w/ High Sierra 10.13.6 (as far as it will go)
I'll understand if XV is no longer supported (it's quite long in the
tooth), but I find it better than GIMP for my requirements.
Anyway...
---> Building xv
Error: Failed to build xv: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_xv/xv/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe
there is a bug.
Extract from main.log (compressed log attached):
:info:build /usr/bin/clang -Os -arch x86_64 -DDOPNG -I/opt/local/include
-I/opt/local/include -DDOJPEG -I/opt/local/include -DDOTIFF
-DUSE_TILED_TIFF_BOTLEFT_FIX -I/opt/local/include -DDOPDS -DDOJP2K
-I/opt/local/libexec/jasper2/include -DMGCSFXDIR=\"/opt/local/lib/xv\"
-D__DARWIN__ -DUSLEEP -DDOCDIR=\"/opt/local/share/doc/xv\"
-DSYSCONFDIR=\"/etc\" -DXVEXECPATH=\"/opt/local/lib/xv\" -o bggen bggen.c
-L/opt/local/lib -ltiff -L/opt/local/lib -ljpeg -L/opt/local/lib -lpng
-L/opt/local/lib -lz -L/opt/local/libexec/jasper2/lib -ljasper -L/usr/X11R6/lib
-lX11 -lm
:info:build xvjp2k.c:77:5: error: redefinition of 'jas_getdbglevel'
:info:build int jas_getdbglevel(void) {return 0;}
:info:build ^
:info:build /opt/local/include/jasper/jas_debug.h:123:5: note: previous
definition is here
:info:build int jas_getdbglevel(void)
:info:build ^
:info:build 1 error generated.
:info:build make: *** [xvjp2k.o] Error 1
Anyone else seeing this before I lodge a bug report? I guess a dependency
must've changed to cause the rebuild...
-- Dave
main.log.bz2
Description: main.log.bz2
Re: openal-soft fails to build (fwd)
On Tue, 28 Jun 2022, Joshua Root wrote: > Looks like openal-soft is linking with libsndfile despite not depending > on it (and fails because the lack of a declared dependency also means > the architectures haven't been made to match.) File a ticket. Will do, as soon as I get my ducks in a row. Now I just have to remember how to file a bug report again... I rarely do it cuz MacPorts is so reliable :-) Thanks. -- Dave
openal-soft fails to build (fwd)
Re-sent: I forgot that the logfile was appended to for each run... -- Dave -- Forwarded message -- Date: Tue, 28 Jun 2022 06:36:02 +1000 (EST) From: Dave Horsfall To: macports-users Subject: openal-soft fails to build MacBook Pro 13" Mid 2010, High Sierra 10.13.6. My usual "port upgrade outdated"; aborted yesterday and tried again today on the off-chance that someone fixed it in the meantime (when you're my age you tend to take a lazy approach to fixing other peoples' bugs; I spent a career doing that): ---> Computing dependencies for openal-soft ---> Fetching archive for openal-soft ---> Attempting to fetch openal-soft-1.22.1_0+universal.darwin_17.i386-x86_64.tbz2 from http://packages.macports.org/openal-soft ---> Attempting to fetch openal-soft-1.22.1_0+universal.darwin_17.i386-x86_64.tbz2 from http://kmq.jp.packages.macports.org/openal-soft ---> Attempting to fetch openal-soft-1.22.1_0+universal.darwin_17.i386-x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/openal-soft ---> Building openal-soft Error: Failed to build openal-soft: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_audio_openal-soft/openal-soft/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. I don't even know what "openal-soft" is, so I assume it's a dependency of something. In the meantime I tried disabling "+universal" because I don't need it, and now I get: ---> Computing dependencies for wine Error: Cannot install wine for the arch 'i386' because Error: its dependency openal-soft does not build for the required arch by default Error: and the configured universal_archs '' are not sufficient. Error: rev-upgrade failed: Error rebuilding wine Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Now what? Thanks. -- Dave main.log Description: main.log
Re: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled:
On Sat, 7 May 2022, Michael Newman via macports-users wrote: > Can someone please explain what this warning is about and just what > "Wimplicit" means? It means that a function was not declared as returning a type, and so it's assumed to return "int"; I regard this as sloppy programming, and is to be avoided by serious programmers i.e. those concerned about security etc. -- Dave
Re: zsh problems MacOS High Sierra
On Mon, 2 May 2022, Ryan Schmidt wrote: > When the MacPorts installer detects that your shell is zsh, it places > such a line in ~/.zprofile. I don't know if there is a significant > difference between putting it in ~/.zprofile vs putting it in ~/.zshenv. I've been using ZSH on various boxen for ages, and I still don't understand it :-) -- Dave
Re: Announcement: macports.el, an Emacs porcelain for MacPorts
On Tue, 3 May 2022, Peter West wrote: > Ah, a trivia magnet. Trivia R Us :-) > Fun fact: emacs, of that which was to become emacs, was originally > written in TECO, an editor, and obviously a very powerful one. > > TECO attracted its own expansions. My favourite – Text Eraser and > COrrupter. Added to my list... Having had to learn to use TECO in the past (a contract job when still at Uni), I used to type a name into it to see what it did (every character was a command)... Now, the most that I can remember these days is: E$ - edit and take a backup Well, as least to delete a line in VI was "dd"... It was difficult to do something dangerous with it. -- Dave
Re: Announcement: macports.el, an Emacs porcelain for MacPorts
> Can you show it in action in a video please?I'm interested in Emacs, > just switched to it… > > I’ve added a screencast to the readme on > GitHub:https://github.com/amake/macports.el Seen in various .sigs over the decades: EMACS - eight megs and constantly swapping "Enough Memory? A Concept Strange!" I thought it stood for Escape-Meta-Alt-Control-Shift :) Emacs Makes A Computer Slow Eventually Munches All Computer Storage Let the editor wars begin :-) -- Dave
Re: Somewhat off topic - keeping older Macs running
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
Re: During Migration to Arm64 mac, should I null out archs='x86_64' from installed ports list?
On Thu, 14 Apr 2022, Daniel J. Luke wrote: [...] > > Which prevents further upgrades or installs in the existing tree. > > ... until you follow the instructions. > > Once you do step 2, the port command works again (and you should follow > the rest of the instructions, but if you're prepared to live with the > consequences of things maybe breaking because you didn't follow good > advice, even things like 'port install' and 'port upgrade outdated' > mostly work at that point). I've found that whenever I think I'm being clever, then things go pear-shaped; if I follow the instructions to the letter then it all works well. There might be a connection there... -- Dave, with 50+ years of IT experience
Re: Corrupted ports.tar file?
On Tue, 12 Apr 2022, Ryan Schmidt wrote: > > I did run that first; apologies for not mentioning it (there were no > > issues). > > I think you did mention it. I was suggesting you run it again, in case > somehow the server files were in a weird state the last time you > selfupdated. There was some intermittent network problem affecting the > server that generates the ports.tar file a few days ago, and again > today; although I thought our rsync updates happened pretty much > atomically, maybe it was possible for a set of files to be published > briefly that was not correct. Sorry; my mistake. I ran it again, and no problems; boy, do I hate these heisenbugs :-( Many thanks. -- Dave
Re: Corrupted ports.tar file?
On Mon, 11 Apr 2022, Ryan Schmidt wrote: > Run "sudo port selfupdate" to get the most recent ports.tar. Do you > still see the problem then? I did run that first; apologies for not mentioning it (there were no issues). In fact, my schedule is: Sunday: "port -u uninstall" to clean out ports that were squirrelled away. Monday: "port selfupdate; port upgrade outdated" (under "script"). Note that "port selfupdate" offers to run "port reclaim" every fortnight, where this problem was observed. > This message could occur if you run "sudo port selfupdate" (or "sudo > port sync") in one terminal window while another MacPorts process is > still running in another terminal window. So it's best not to do that. > If you weren't doing that, I can't explain it. Not a chance that I'd do anything as silly as that (I've been a sysadmin for nearly 50 years)... All my updates are run in the one window (with scrollback). I'll see if this heisenbug happens again next week (I can't spend any time on debugging it right now). -- Dave
Corrupted ports.tar file?
Early MacBook Pro, High Sierra 10.13.6, MacPorts 2.7.2. When doing my weekly MacPorts maintenance (doesn't everyone?), I saw this during a "port reclaim" (automatically requested): Found no inactive ports. ---> Building list of distfiles still in use Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt. Warning: Port bzip2 not found: Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt. Warning: Port db48 not found: Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt. Etc; I do have "bzip2" and so on. Haven't seen that before; what's going on? A following "port upgrade outdated" saw no problems... -- Dave
Re: Problem with gdb port
On Wed, 6 Apr 2022, Christoph Kukulies wrote: > I’m gettig the following: > $ sudo port install gdb [...] Worked first time on High Sierra (yet another utility that I'd lost when migrating from Sierra; sigh), except for this little bit: gdb has the following notes: You will need to codesign /opt/local/bin/ggdb See https://sourceware.org/gdb/wiki/BuildingOnDarwin#Giving_gdb_permission_to_control_other_processes for more information. Hadn't seen that before, but shouldn't be a problem to fix. -- Dace
Re: port diagnose and xcode
On Wed, 23 Mar 2022, Michele Venturi wrote: > If MacPorts is not a package manager we need one,I'd say HomeBrew could > be the right tool for the job. I find that MacPorts is a most excellent package manager; what exactly is your problem? -- Dave
2.7.1 -> 2.7.2 OK
Smooth as the proverbial baby's bottom on an oldish MacBook Pro, High Sierra 10.13.6; well done, all. I'm quite taken by the progress bar on "cmake"; it keeps changing its mind, just like a MacOS upgrade does :-) -- Dave
Re: port diagnose and xcode
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
On Wed, 9 Mar 2022, Sriranga Veeraraghavan wrote: > I have been using MacPorts for years and never knew about this. I just > ran this on my system and it reclaimed nearly 2GB of space, which was > awesome. Thank you so much for mentioning this! "port reclaim" is part of the "port -u uninstall / port selfupdate / port upgrade outdated" sequence that you should be running on a regular basis to keep your MacPorts clean and shiny; I do them weekly. -- Dave
Re: Drive-by downloads of Install macOS Monterey
On Tue, 8 Mar 2022, Christopher Chavez wrote: > If the installer is deleted, it may eventually be downloaded again. To > prevent this, one workaround suggested by > https://www.reddit.com/r/MacOS/comments/sj3aia/comment/hvcm3e4/ is to > create an empty folder 'Install macOS Monterey.app' and lock it (either > from "Get Info", or from the command line using `chflags uchg > '/Applications/Install macOS Monterey.app/'`). Personally I think the idea of deleting the installer sucks, as it might be needed for e.g. a USB stick. I know, that's what Apple does, not MP... -- Dave
Re: Fwd: rsync build failure on mojave
On Mon, 7 Mar 2022, Ryan Schmidt wrote: > https://trac.macports.org/wiki/BadContent A fine collection of perps :-) I haven't seen any of them though, as I make extensive use of DNSBLs[*], but that's not to everyone's taste. [*] http://www.horsfall.org/spam.html (I don't run HTTPS yet) https://en.wikipedia.org/wiki/Domain_Name_System-based_blackhole_list -- Dave
Re: MacPorts XCode Installation
On Sat, 26 Feb 2022, Peter Hancock wrote: > Quite. I have full Xcode, regretfully, plus the CLI tools. I'm never > confiident that some that Macports installation needs the full thing. I've never wanted to find out the hard way, so I always install the full Xcode (after a lot of digging around to find an old version -- 10.0 -- for my ancient MacBook Pro and High Sierra). > Being alerted is one thing, undergoing the grief of installing The Full > Thing is another, and uninstalling TFT afterwards yet another. (It's not > 100% clear to me how to get rid of it, while keeping the CLT) I have a 500GB SSD, so space isn't a problem :-) > A peripheral point is the way Apple deletes "receipts" for previous > command reinstalls, and once or twice a month, one (seemingly) has to > jump through the well-worn hoop of touching a flag-file into existence, > doing an Apple update, and deleting the flag afterwards. > > That's tolerable, but it's a chore, and a worrying one. It's tempting to > think (falsely): if I install TFT, perhaps this nonsense will stop. > > The clearer this (general, TFT) topic can be made, the better. I'm not quite sure what this is all about; then again, as I said I always install the full Xcode and I've never seen this problem. -- Dave
Was MacPorts having some weird trouble last Monday?
It's difficult to phrase this, but I'll do my best... MacBook Pro (13-inch, Mid 2010), High Sierra 10.13.6. After I did my regular "port upgrade outdated" (there was nothing odd in the log) I noticed that some utilities has disappeared; as I recall, they included "htop", "xv", "gimp", "enscript", "gnuplot" (which I have running all the time until I restarted it), etc. A simple re-install of the errant applications fixed it. That's about all I can say, so did anyone else notice any oddities? Everything was peachy this morning. Thanks. -- Dave
XV/GIMP/etc: Can't open display
MacBook Pro (13-inch, Mid 2010), saddled with High Sierra 10.13.6 (as far as it will go). Back when I was running Sierra these tools worked just fine; after upgrading to HS (and rebuilding MacPorts that took almost a day) things went pear-shaped: mackie:~ dave$ xv xv: Can't open display mackie:~ dave$ gimp Cannot open display: mackie:~ dave$ echo $DISPLAY mackie:~ dave$ Is this something I forgot to do during the upgrade? I set $DISPLAY to ":0" (an old Unix trick) to no effect, so I guess it's using a named pipe instead but I cannot find it; poking around doesn't seem to uncover anything applicable to this, and I certainly won't trust any "advice" on StackOverflow. Where has my 70yo brain screwed up? Thanks. -- Dave
Re: Sms for text messages in macports
On Mon, 17 Jan 2022, Richard L. Hamilton wrote: > Every cell phone provider, or at least just about every US cell phone > provider, has an email to SMS gateway. It's free for someone sending > email to it, not necessarily for the recipient. The problem is you have > to know the provider for a given number, and AFAIK, there's no > particularly easy way to do that automatically and scriptably (so you > can generate an email address for the correct gateway). MMS gateways > also exist, although the acceptable MIME types and size/complexity > limits for attachments may be tedious to discover. I've seen a reference to his before; the receiver pays to receive mobile calls in the USA? In Australia it's the sender who pays (of course). And I believe that mobile phones (what you call cellular phones) don't have their own prefix? We reserve "04" for that; at one time you could even tell which provider it was, but now you get to keep your number when you change providers. But to bring this back on topic... > Alternatives: a service (some free for small volumes only) that can send > SMS from a computer. Or Asterisk plus extensions, to set yourself up a > full VoIP PBX...except that will need some paid service too, to connect > to. But it will do a lot more than just send (or receive) SMS, it could > forward phone calls, with proper hardware interfaces drive either old > fashioned or VoiP phones, etc. It looks like a lot of work and learning > as well as expense, though, and really ought to have a dedicated server, > too, although that's not absolutely necessary. We had that in a previous $JOB; if Nagios (a general system monitor) detected something that triggered a rule then a set of users would receive a brief SMS, sent from a GSM modem. I looked at this for my own LAN, but it ain't cheap... -- Dave
Re: Sms for text messages in macports
[ Original message lost ] There is iMessage, but it's not the same as SMS i.e. you cannot send texts to arbitrary mobile phones. -- Dave
Re: Cannot build libb2
On Fri, 10 Dec 2021, Ryan Schmidt wrote: > The "-arch x86_64 -arch i386" in the log does seem to indicate MacPorts > is doing a universal build. The ways that could happen: > > * You specified +universal on the command line Nope... > * You specified +universal in variants.conf Nope... > * You installed a port that, because it does not support your machine's > native architecture, requires its dependencies to be installed > universal. Could be; how do I tell which variants were used by what? > If libb2 does not build universal, then that is certainly something we > should fix. A bug has already been filed about it: > > https://trac.macports.org/ticket/64148 Thanks; I'll try the suggested fix, but... > If you want to explore why libb2 is building universal when you don't > intend that, show us what command you ran and the output. Specifically, > we'd want to know which port you are trying to install or upgrade when > libb2 gets build universal. It was no more than my weekly "port selfupdate; port upgrade outdated" etc. Looks like I forgot to run it under "script", but when I tried again it now mysteriously works, so I dunno... Chalk it up to a "heisenbug", I guess (I hate those). -- Dave
Re: pwait?
On Tue, 14 Dec 2021, Ryan Schmidt wrote: > > Wishing for a port...bit ugly when you can't use the supplied > > Makefile. Sadly, not volunteering myself. :-/ > > Added! Thanks for the suggestion. That was quick! Compiling the FreeBSD source was easy, though; I've found that most FreeBSD sources work with little if any changes. -- Dave
Re: Can some ports install config files inside '/usr/local/etc'?
On Sat, 11 Dec 2021, Chris Jones wrote: > Nothing in macports will be installing to /usr/local. If you have > anything in that area it has been put there by some other means. Maybe > homebrew?, but also a number of third party installers sometimes use > this directory as well (which are the reasons why MacPorts specifically > ignores this area). The "/usr/local" tree is quite a common destination on other systems such as FreeBSD; I use it on the Mac to separate my own stuff from MacPorts' stuff as well. -- Dave
Cannot build libb2
MacBook Pro (13-inch, Mid 2010), macOS High Sierra 10.13.6. I finally got around to installing Xcode 10.1 and matching CLT, then started to rebuild MacPorts, dutifully following the instructions in the Migration Guide. It karked it when building "libb2" (config.log attached); here's the interesting bit: configure:4721: checking whether byte ordering is bigendian configure:4737: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local /include conftest.c >&5 configure:4737: $? = 0 configure:4936: result: universal configure:4947: error: universal endianness not supported I don't where it got "+universal" from; *I* certainly didn't ask for it... I couldn't find any references when poking around; anyone else seen this before I report it as a bug? Thanks. -- DaveThis file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libb2 configure 0.98.1, which was generated by GNU Autoconf 2.71. Invocation command line was $ ./configure --prefix=/opt/local --disable-dependency-tracking --enable-native=no --disable-openmp ## - ## ## Platform. ## ## - ## hostname = mackie.kfu uname -m = x86_64 uname -r = 17.7.0 uname -s = Darwin uname -v = Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 PDT 2020; root:xnu-4570.71.82.8~1/RELEASE_X86_64 /usr/bin/uname -p = i386 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = Mach kernel version: Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 PDT 2020; root:xnu-4570.71.82.8~1/RELEASE_X86_64 Kernel configured for up to 2 processors. 2 processors are physically available. 2 processors are logically available. Processor type: i486 (Intel 80486) Processors active: 0 1 Primary memory available: 8.00 gigabytes Default processor set: 414 tasks, 1868 threads, 2 processors Load average: 4.07, Mach factor: 0.44 /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /opt/local/bin/ PATH: /opt/local/sbin/ PATH: /bin/ PATH: /sbin/ PATH: /usr/bin/ PATH: /usr/sbin/ ## --- ## ## Core tests. ## ## --- ## configure:2532: looking for aux files: config.guess config.sub ltmain.sh compile missing install-sh configure:2545: trying ./ configure:2574: ./config.guess found configure:2574: ./config.sub found configure:2574: ./ltmain.sh found configure:2574: ./compile found configure:2574: ./missing found configure:2556: ./install-sh found configure:2706: checking for a BSD-compatible install configure:2779: result: /usr/bin/install -c configure:2790: checking whether build environment is sane configure:2845: result: yes configure:3004: checking for a race-free mkdir -p configure:3048: result: ./install-sh -c -d configure:3055: checking for gawk configure:3090: result: no configure:3055: checking for mawk configure:3090: result: no configure:3055: checking for nawk configure:3090: result: no configure:3055: checking for awk configure:3076: found /usr/bin/awk configure:3087: result: awk configure:3098: checking whether make sets $(MAKE) configure:3121: result: yes configure:3151: checking whether make supports nested variables configure:3169: result: yes configure:3378: checking for gcc configure:3410: result: /usr/bin/clang configure:3763: checking for C compiler version configure:3772: /usr/bin/clang --version >&5 Apple LLVM version 10.0.0 (clang-1000.10.44.4) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin configure:3783: $? = 0 configure:3772: /usr/bin/clang -v >&5 Apple LLVM version 10.0.0 (clang-1000.10.44.4) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin configure:3783: $? = 0 configure:3772: /usr/bin/clang -V >&5 clang: error: argument to '-V' is missing (expected 1 value) clang: error: no input files configure:3783: $? = 1 configure:3772: /usr/bin/clang -qversion >&5 clang: error: unknown argument: '-qversion' clang: error: no input files configure:3783: $? = 1 configure:3772: /usr/bin/clang -version >&5 clang: error: unknown argument: '-version' clang: error: no input files configure:3783: $? = 1 configure:3803: checking whether the C compiler works configure:3825: /usr/bin/clang -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 ld: warning: The i386 architecture is deprecated for macOS (remove from the Xcode build setting: ARCHS) configure:3829: $? = 0 configure:3879: result: yes configure:3882: checking for C compiler default output file name configure:3884: result: a.out configure:3890: checking for suffix of executables configure:3897: /usr/bin/clang -o conftest -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib
Re: No user or group to remove on macOS Catalina
On Fri, 26 Nov 2021, Ryan Schmidt wrote: > You're right, it's best to pick one package manager and uninstall the > other, to avoid them conflicting with one another. If you have any > feedback about ways that MacPorts could improve, please let us know. I'm not sure how I came across MacPorts, but I wouldn't switch away from it for quids; it serves my purposes perfectly. Keep up the great work! -- Dave
Re: Does MacPorts depend on Spotlight?
On Wed, 17 Nov 2021, Bill Cole wrote: Where are all these obscure commands documented? /usr/share/man/man1/ and /usr/share/man/man8/ mostly... Perhaps I should've expressed it better :-) I've found all sorts of obscure commands (such as "security" and the aforementioned "mdutil") mentioned on this list; now, how am I supposed to know that they existed in the first place? I cannot find any sign of an admin guide, and this 2nd-hand MacPro did not come with media. It seems that I have to look at all the manfiles and wonder what they do... FWIW, 'apropos spotlight' will tell you that mdutil and mddiagnose exist. Sure, but my query was more of a general nature. -- Dave
Re: Does MacPorts depend on Spotlight?
On Wed, 17 Nov 2021, Peter Hancock wrote: On Catalina, for me the command "sudo mdutil -i off /opt/local/var/macports" evokes: [...] Where are all these obscure commands documented? -- Dave
Re: Specify UserID and GroupID for MacPorts users, how can I do that?
On Mon, 8 Nov 2021, Bjarne D Mathiesen wrote: you've got three (3) Terminal commands to manage users directly # dscl # dsexport # dsimport Which reminds me of a bugbear of mine: every so often on this list I see hitherto-unknown commands for the Mac (and I've been dealing with Unix and Unix-like systems for decades). Another example (from this list) is "security" which leads me to more obscure commands. Is there a summary of such commands that all geeks ought to know? -- Dave
Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)
On Sun, 7 Nov 2021, Bill Cole wrote: So I wonder how widespread this problem is? The problem in this case is not the existence of the cert in the CA bundle, but the fact that this particular expired cert was used in an alternative validation path and the logic of verification for multi-path certs isn't correct. Normally, expired root CAs should stay in there because that allows positive non-verification of certs supposedly issued by an expired (and maybe compromised) root CA. Gotcha; thanks. And I'm not happy with those that are set way in the future; I heard somewhere that 5 years is the recommended max. CAs are special. The current limit on server certs is 397 days. I don't think there's a consensus on CA lifetimes because of the conflicting risks of too-short and too-long lives. One day past a leap year :-) I don't remember where I saw the 5-year recommendation, unfortunately. -- Dave
Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)
On Sun, 7 Nov 2021, Bill Cole wrote: I have my own Mojave machines working without a problem after removing the bad certificate from /etc/ssl/cert.pem. The one that starts like this: [...] Intrigued, I checked my own: mackie:~ dave$ grep "Not After" /etc/ssl/cert.pem Not After : Aug 13 23:59:00 2018 GMT Not After : Aug 22 16:41:51 2018 GMT Not After: Aug 22 16:41:51 2018 GMT Not After : Aug 1 23:59:59 2028 GMT Not After : Jan 28 12:00:00 2028 GMT Not After : Dec 15 08:00:00 2021 GMT Not After : Mar 18 10:00:00 2029 GMT Not After : Dec 31 23:59:59 2020 GMT Not After : Dec 31 23:59:59 2020 GMT Not After : Jul 16 23:59:59 2036 GMT Not After : Jul 16 23:59:59 2036 GMT Not After : Jan 18 23:59:59 2038 GMT Not After : Dec 1 23:59:59 2037 GMT Not After : Jul 16 23:59:59 2036 GMT Not After : Sep 17 19:46:36 2036 GMT Not After : Jun 26 00:19:54 2019 GMT Not After : May 25 16:39:40 2019 GMT Not Before: May 25 16:09:40 1999 GMT, Not After: May 25 16:09:40 2019 GMT Not After : Nov 10 00:00:00 2031 GMT Not After : Nov 10 00:00:00 2031 GMT Not After : Nov 10 00:00:00 2031 GMT Not After : Jun 21 04:00:00 2020 GMT Not After : Jun 21 04:00:00 2020 GMT Not After : May 21 04:00:00 2022 GMT Not After : Mar 4 05:00:00 2019 GMT Not After : Jul 16 23:59:59 2036 GMT Not After : Dec 1 23:59:59 2037 GMT Not After : Mar 4 05:00:00 2029 GMT Not After : Mar 4 05:00:00 2029 GMT Not After : Jun 29 17:06:20 2034 GMT Not After : Dec 31 23:59:59 2037 GMT Not After : Jun 29 17:39:16 2034 GMT Not After : Dec 31 23:59:59 2037 GMT Not After : Dec 31 23:59:59 2037 GMT Not After : Dec 31 23:59:01 2039 GMT Not After : Jul 16 23:59:59 2036 GMT Not After : Jan 18 23:59:59 2038 GMT Not After : Dec 1 23:59:59 2037 GMT Not After : May 30 10:48:38 2020 GMT Not After : Dec 31 23:59:59 2028 GMT Not After : Jul 9 18:19:22 2019 GMT Not After : May 12 23:59:00 2025 GMT Not After : Jul 9 23:59:00 2019 GMT Not After : Oct 1 23:59:59 2033 GMT Not After : Oct 1 23:59:59 2033 GMT Not After : Oct 25 08:30:35 2036 GMT Not After : Oct 25 08:36:00 2036 GMT Not After : Oct 25 08:32:46 2036 GMT Not After : Sep 30 14:01:15 2021 GMT Not After : Dec 6 15:08:21 2028 GMT So I wonder how widespread this problem is? And I'm not happy with those that are set way in the future; I heard somewhere that 5 years is the recommended max. -- Dave
Re: provide latest OS root certificates via port?
On Fri, 29 Oct 2021, Bill Cole wrote: Yes: Anyone running Mojave or earlier is not exactly skydiving without a parachute, but is doing something close. Perhaps it's akin to skydiving with a homemade parachute... Well, my ancient MacBook Pro is stuck on High Sierra; then again I'm careful about the sites that I visit and have all sorts of add-ons, and the Mac itself is not accessible from the 'Net. -- Dave
Re: What version of Xcode for High Sierra?
On Sat, 25 Sep 2021, Dave Horsfall wrote: MacBook Pro, 13", mid-2010, 8GB memory (self-supplied, as the default 4GB is simply not enough), firmware 7,1. Thanks all for the many answers; now to digest them... Relevance to MacPorts: it needs Xcode... And that's my only use of Xcode; being a command line person for decades I've never really related to GUIs (heck, even my Mac is full of Terminals on the screen), although Perk/Tk sort of tickles my fancy (at least it uses tools that I understand). -- Dave
Re: What version of Xcode for High Sierra?
On Sat, 25 Sep 2021, Horst Simon wrote: I have following and no issues with my MacPorts apps. [...] Xcode: Version 10.1 (10B61) Many thanks; I'll give it a try when I get the time. -- Dave
What version of Xcode for High Sierra?
MacBook Pro, 13", mid-2010, 8GB memory (self-supplied, as the default 4GB is simply not enough), firmware 7,1. Relevance to MacPorts: it needs Xcode... There seems to be many versions of Xcode for High Sierra (I don't want to upgrade further just yet) so which one is known to work for this thing so that I can start using MacPorts again?? I don't want to waste a few hours of download (including Command Line Tools) only to see "xcode-select" spit the dummy because it's the wrong version of the OS or something. Thanks. -- Dave
Is there a binary editor for MacPorts?
I can see heaps of 3rd-party stuff out there, but is there an "official" one? I have a file with some binary stuff in it (8-bit accents, perhaps?) and "vi" just spits the dummy at that point and I want to search down further. Thanks. -- Dave
Re: MacPorts for High Sierra?
On Sun, 15 Aug 2021, Ken Cunningham wrote: No — but there is a brand spanking new version of MacPorts that runs on High Sierra. I am in fact using it right at this second, and it works just great. Now running here. MacPorts doesn’t require BigSur; it runs on everything from Tiger PPC up. My mistake; I ran: mackie:~ dave$ sudo port selfupdate Error: Current platform "darwin 17" does not match expected platform "darwin 16" 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 and somehow thought that it required Big Sur. Plainly I need to read it more carefully :-( Now to install the latest MacPorts... -- Dave
Re: macOS 11 Big Sur and MacPorts
[ Late reply ] On Thu, 12 Nov 2020, Mojca Miklavec wrote: Thanks for the heads-up; I think my MacBook Pro will be stuck forever on Sierra 10.12.6 (although admittedly I haven't tried High Sierra on this one) and MacPorts 2.6.3 is likely as far as it will go. I successfully installed High Sierra; I needed it to drive a multi-function printer that I acquired. I understand the Sierra part, but why would it be stuck with MacPorts 2.6.3? I have a problem with getting the latest Xcode to work, and made the assumption that MacPorts would require it. Trouble is, I keep getting distracted by other things :-( -- Dave
Re: MacPorts for High Sierra?
On Sun, 15 Aug 2021, Ken Cunningham wrote: No — but there is a brand spanking new version of MacPorts that runs on High Sierra. I am in fact using it right at this second, and it works just great. OK. MacPorts doesn’t require BigSur; it runs on everything from Tiger PPC up. https://everymac.com/mac-answers/macos-11-big-sur-faq/macos-big-sur-macos-11-compatbility-list-system-requirements.html System Requirements In marketing and technical documentation and elsewhere, Apple specifies that macOS Big Sur runs on these Macs: MacBook (2015 and later) MacBook Air (2013 and later) MacBook Pro (Late 2013 and later) <= iMac Pro (2017 and later) iMac (2014 and later) Mac mini (2014 and later) Mac Pro (2013 and later) Compared to the previous version of the macOS -- macOS Catalina (10.15) -- macOS Big Sur (macOS 11) drops support for the Mid-2012 MacBook Air; Mid-2012, Late 2012, and Early 2013 MacBook Pro; Late 2012, Early 2013, and Late 2013 iMac; and Late 2012 Mac mini models. Perhaps you didn’t find the right HS installer? Try this one: https://github.com/macports/macports-base/releases/download/v2.7.1/MacPorts-2.7.1-10.13-HighSierra.pkg I'll have a look; thanks. -- Dave
MacPorts for High Sierra?
I had to upgrade this old MacBook Pro (mid 2010) from Sierra to High Sierra to run some software that I needed, and now I find that MacPorts wants Big Sur which this thing won't run (and I can't afford a new one). So, is there an old version of MacPorts somewhere that runs on HS? Thanks. -- Dave
Re: High Sierra
On Tue, 29 Jun 2021, Richard L. Hamilton wrote: Have you seen https://support.apple.com/en-us/HT211683 ? Many thanks! -- Dave, happily upon High Sierra
High Sierra
macOS Sierra 10.12.6, MB Pro 13", Mid 2010. 8GB mem, 480GB SS SATA drive. I'm starting to find that this old MacBook Pro needs High Sierra for various reasons (printer drivers etc), but Cupertino seems to be keeping its location a secret. So... a) Where can I find it? and more importantly: b) I take it that MacPorts will have to be download/recompiled in its entirety? After that I'll start attacking Xcode (long story). Thanks. -- Dave
Re: MacPorts 2.7.1 has been released
On Thu, 27 May 2021, Joshua Root wrote: The MacPorts Project is pleased to announce the release of version 2.7.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. [...] No trouble at all on 10.12.6 (apart from "gq" which I am still sorting out). Took most of a day, though, what with compiling LLVM etc... I was out for most of the day and missed a prompt, so it may not have been that bad. I like the revamped progress bar :-) -- Dave
Re: Telnet not in netutils
On Fri, 28 May 2021, raf wrote: It's also a horribly insecure protocol; I've even disabled it on my LAN (SSH is your friend). telnet might still be useful for debugging other services (that have no authentication), although probably nothing that nc/nc6 can't do. but yes, port 23 should certainly be avoided like something proverbial. Yeah, my router uses it for maintenance, but that's the only Telnet server here; I've even disabled the external maintenance port (the password is hardly a secret) so my ISP will have to ask me nicely if they need it. -- Dave
Re: Telnet not in netutils
On Thu, 27 May 2021, Christopher Jones wrote: I guess you didn’t read/notice the port notes when you installed inetutils ? [...] It's also a horribly insecure protocol; I've even disabled it on my LAN (SSH is your friend). -- Dave
Error building "gq"
Sierra 10.12.6, Xcode 9.2 (fetched recently). GQ is a GUI LDAP browser (my favourite). [...] ---> Attempting to fetch gq-1.2.3_2.darwin_16.x86_64.tbz2 from https://kmq.jp.packages.macports.org/gq ---> Building gq Error: Failed to build gq: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_gq/gq/main.log for details. Error: rev-upgrade failed: Error rebuilding gq Extract from main.log: [ Usual warnings due to sloppy coding ] :info:build /usr/bin/clang -DHAVE_CONFIG_H -I. -I.. -Wall -W -Wno-unused -Wmissing-declarations -Wcast-align -Wpointer-arith -Wfloat-equal -D_REENTRANT -I/opt/local/include/gnome-keyring-1 -I/opt/local/include/libglade-2.0 -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/pango-1.0 -I/opt/local/include/gio-unix-2.0/ -I/opt/local/include/cairo -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pixman-1 -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/libpng16 -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz -I/opt/local/include/pango-1.0 -I/opt/local/include/fribidi -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include/ossp -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include/libxml2 -I/opt/local/include -I/opt/local/include -I/opt/local/include -I/opt/local/include -pipe -Os -arch x86_64 -MT dt_oc.o -MD -MP -MF .deps/dt_oc.Tpo -c -o dt_oc .o dt_oc.c :info:build dt_cert.c:193:29: error: incomplete definition of type 'struct x509_st' After which everything bails out. I vaguely seeing this before... Is GQ et al now no longer maintained? If so then that would be a great pity. Entire main.log attached, in case I missed something (it's past midnight here, and I've been awake since early morning). -- Dave main.log Description: main.log
Re: Xcode for Sierra 10.12.6
On Thu, 27 May 2021, Dave Horsfall wrote: I'm a cautious person by nature, so I think I'll battle Xcode first as I really need it, then I'll look at High Sierra when I have the time (it's like watching paint dry, as I recall) and extra memory (it's struggling with 4GB because I have dozens of tabs in Firefox). Well, that sure uncorked the sluices :-) My weekly "port upgrade outdated" kept getting stuck on "gpsd" requiring Xcode, and now my poor li'l MB Pro is going flat out like a lizard drinking... -- Dave
