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
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
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. (
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.
Bing
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 ve
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
No trouble upgrading on this ancient MBP running High Sierra.
-- Dave
che). 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:
> >
> > [...]
> &
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 brea
> > 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
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 Me
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
Smooth as usual on this ancient box... Thanks, all.
-- Dave
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
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
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_m
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
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
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_
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?
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
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
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
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.
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
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
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
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
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
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 w
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
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
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 an
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.
T
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 CL
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 h
High Sierra on an ancient MacBook Pro.
No problems whatsoever, not even the one mentioned recently; I hope I
haven't overlooked something...
-- Dave
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
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.
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
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/d
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 tha
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://dosdud
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
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
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
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_arch
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
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 no
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
[.
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
E
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.
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
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
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 fo
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.
> 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
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 malwa
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 t
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
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 port
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 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 codes
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
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
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
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
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 lo
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://
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
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
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 displa
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 g
[ 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
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...
> * Yo
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 source
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 rea
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
intere
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, b
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 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
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-
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
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 A
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 abo
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 Xcod
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
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 thi
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
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.
[ 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 Sie
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://everym
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.
-- D
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
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 importan
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
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 certa
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
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: S
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
1 - 100 of 326 matches
Mail list logo
