Re: rust port complaint at time of selfupdate

[Kenneth Wolcott]

HI Maxim;

  I guess my ticket search wasn't very thorough :-)

  Thanks for the link to the existing ticket.

Ken W

On Tue, Oct 1, 2024 at 8:54 AM Maxim Abalenkov
 wrote:
>
> Hello Kenneth et al.,
>
> How are you? There is a ticket. Please see:
>
>   https://trac.macports.org/ticket/70573
>
> This issue is relevant for me too. But it seems no-one is working on its 
> resolution. Because of it I cannot clean my MacPorts installation for a few 
> weeks now. Thank you!
>
> —
> Best wishes,
> Maxim
>
> Maxim Abalenkov \\ maxim.abalen...@gmail.com
> +44 7 486 486 505 \\ www.maxim.abalenkov.uk
>
> On 1 Oct 2024, at 16:49, Kenneth Wolcott  wrote:
>
> Hi;
>
>  I don't see a ticket for the Rust issue, I guess I will create one.
>
> Ken Wolcott
>
> On Fri, Sep 20, 2024 at 12:04 PM Christopher Jones via macports-users
>  wrote:
>
>
>
> You should learn to check trac tickets. Or just check
>
> https://trac.macports.org/wiki/SequoiaProblems
>
> for the known problems.
>
> R will not work on macOS15 until its maintainers bumps ints gcc and clang 
> versions to those support on this OS
>
> https://trac.macports.org/ticket/70799
>
> Chris
>
> On 20 Sep 2024, at 7:55 pm, Kenneth Wolcott  wrote:
>
>
> Hi;
>
> So how do I fix the problem?
>
> I have a similar problem with R now...
>
> Failed to parse file R/R-pbdMPI/Portfile: can't read "mpi_port": no
> such variable
> Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
> (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)
>
> On Wed, Sep 18, 2024 at 4:33 PM Austin Ziegler  wrote:
>
>
> I think that the `rust-bootstrap` port is supposed to track the `rust` port 
> and only the `rust` port has been updated recently.
>
> -a
>
> On Wed, Sep 18, 2024 at 6:22 PM Kenneth Wolcott  
> wrote:
>
>
> Hi;
>
> Just did a selfupdate, there's an issue with the rust port...
> 
> Creating port index in
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
> Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
> (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)
> 
>
> Thanks,
> Ken Wolcott
>
>
>
>
> --
> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
> http://www.halostatue.ca/ • http://twitter.com/halostatue
>
>
>

Re: rust port complaint at time of selfupdate

[Kenneth Wolcott]

Hi;

  I don't see a ticket for the Rust issue, I guess I will create one.

Ken Wolcott

On Fri, Sep 20, 2024 at 12:04 PM Christopher Jones via macports-users
 wrote:
>
>
> You should learn to check trac tickets. Or just check
>
>  https://trac.macports.org/wiki/SequoiaProblems
>
> for the known problems.
>
> R will not work on macOS15 until its maintainers bumps ints gcc and clang 
> versions to those support on this OS
>
>  https://trac.macports.org/ticket/70799
>
> Chris
>
> On 20 Sep 2024, at 7:55 pm, Kenneth Wolcott  wrote:
>
>
> Hi;
>
>  So how do I fix the problem?
>
>  I have a similar problem with R now...
>
> Failed to parse file R/R-pbdMPI/Portfile: can't read "mpi_port": no
> such variable
> Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
> (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)
>
> On Wed, Sep 18, 2024 at 4:33 PM Austin Ziegler  wrote:
>
>
> I think that the `rust-bootstrap` port is supposed to track the `rust` port 
> and only the `rust` port has been updated recently.
>
> -a
>
> On Wed, Sep 18, 2024 at 6:22 PM Kenneth Wolcott  
> wrote:
>
>
> Hi;
>
>  Just did a selfupdate, there's an issue with the rust port...
> 
> Creating port index in
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
> Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
> (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)
> 
>
> Thanks,
> Ken Wolcott
>
>
>
>
> --
> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
> http://www.halostatue.ca/ • http://twitter.com/halostatue
>
>

Re: The expect port has a problem

[Kenneth Wolcott]

Any update?  This is still happening...

On Wed, Sep 25, 2024 at 1:45 AM Chris Jones  wrote:
>
>
> >I uninstalled the expect port and then installed the expect port
> > again and the broken link still happens...
>
> that was entirely my point. to see the issue you needed to ensure you
> *didn't* have the old one installed 

Re: The expect port has a problem

[Kenneth Wolcott]

Hi;

  I uninstalled the expect port and then installed the expect port
again and the broken link still happens...

Ken Wolcott

On Wed, Sep 25, 2024 at 1:20 AM Chris Jones via macports-users
 wrote:
>
>
>
> On 25/09/2024 9:16 am, Saagar Jha wrote:
> > Reproduced it on a fresh install of MacPorts (I apparently had
> > libexpect.a hanging around in /opt/local for some reason).
>
> That is completely normal when you build an update. The previous version
> is only removed when the update is successfully built and destrooted.
> Only then is the old one deactivatd and the new one activated.
>
>

Re: The expect port has a problem

[Kenneth Wolcott]

It occurs at the end of every install attempt as it seems to be a
broken link check.

On Tue, Sep 24, 2024 at 8:15 PM Saagar Jha  wrote:
>
> I bumped this earlier today to use dynamic libraries instead of static ones, 
> so I assume that’s related. That said, I don’t see this on my machine (I 
> tried running expect). How can I reproduce this?
>
> Saagar Jha
>
> On Sep 24, 2024, at 20:05, Kenneth Wolcott  wrote:
>
> Could not open libexpect5.45.4.dylib: Error opening or reading file
> (referenced from /opt/local/bin/expect)
> libexpect5.45.4.dylib seems to be referenced using a relative path.
> This may be a problem with its canonical library name and require the
> use of install_name_tool(1) to fix.
>
>

The expect port has a problem

[Kenneth Wolcott]

Could not open libexpect5.45.4.dylib: Error opening or reading file
(referenced from /opt/local/bin/expect)
libexpect5.45.4.dylib seems to be referenced using a relative path.
This may be a problem with its canonical library name and require the
use of install_name_tool(1) to fix.

FYI: R depends on g95 which fails to install being too old

[Kenneth Wolcott]

FYI: R depends on g95 which fails to install being too old

I've downloaded R directly, not using MacPorts...

I'm surprised that there haven't been a flurry of email messages
regarding this g95 dependency issue

Ken Wolcott

Re: several ports cannot be installed due to a Perl circular dependency hell...

[Kenneth Wolcott]

Here's the tail-end of an attempt to install gnuplot from source
(similar results from trying to install octave, maxima and others):

Error: The following dependencies were not installed because all of
them have unmet dependencies (likely due to a dependency cycle): gd2
libheif aom git p5.34-authen-sasl p5.34-net-smtp-ssl p5.34-cgi
p5.34-pod-coverage-trustpod p5.34-test-simple p5.34-pod-eventual
p5.34-mixin-linewise p5.34-sub-exporter p5.34-data-optlist
p5.34-params-util p5.34-config-autoconf p5.34-file-slurper
p5.34-test-warnings p5.34-cpan-meta-check p5.34-module-pluggable
p5.34-module-runtime p5.34-module-build p5.34-software-license
p5.34-data-section p5.34-text-template p5.34-io-socket-ssl
p5.34-io-socket-ip p5.34-uri p5.34-html-parser p5.34-html-tagset
p5.34-http-message p5.34-clone p5.34-b-cow
DEBUG: gd2 requires: libheif
DEBUG: libheif requires: aom
DEBUG: aom requires: git
DEBUG: git requires: p5.34-authen-sasl p5.34-net-smtp-ssl p5.34-cgi
DEBUG: p5.34-authen-sasl requires: p5.34-pod-coverage-trustpod p5.34-test-simple
DEBUG: p5.34-net-smtp-ssl requires: p5.34-io-socket-ssl
DEBUG: p5.34-cgi requires: p5.34-test-simple p5.34-html-parser p5.34-uri
DEBUG: p5.34-pod-coverage-trustpod requires: p5.34-test-simple
p5.34-pod-eventual
DEBUG: p5.34-test-simple requires: p5.34-module-pluggable
DEBUG: p5.34-pod-eventual requires: p5.34-test-simple p5.34-mixin-linewise
DEBUG: p5.34-mixin-linewise requires: p5.34-sub-exporter
DEBUG: p5.34-sub-exporter requires: p5.34-data-optlist p5.34-params-util
DEBUG: p5.34-data-optlist requires: p5.34-params-util
DEBUG: p5.34-params-util requires: p5.34-config-autoconf p5.34-test-simple
DEBUG: p5.34-config-autoconf requires: p5.34-file-slurper
DEBUG: p5.34-file-slurper requires: p5.34-test-warnings
DEBUG: p5.34-test-warnings requires: p5.34-cpan-meta-check
DEBUG: p5.34-cpan-meta-check requires: p5.34-test-simple
DEBUG: p5.34-module-pluggable requires: p5.34-module-runtime
DEBUG: p5.34-module-runtime requires: p5.34-module-build
DEBUG: p5.34-module-build requires: p5.34-software-license
DEBUG: p5.34-software-license requires: p5.34-data-section p5.34-text-template
DEBUG: p5.34-data-section requires: p5.34-sub-exporter
DEBUG: p5.34-text-template requires: p5.34-test-warnings
DEBUG: p5.34-io-socket-ssl requires: p5.34-io-socket-ip p5.34-uri
DEBUG: p5.34-io-socket-ip requires: p5.34-module-build
DEBUG: p5.34-uri requires: p5.34-test-simple p5.34-test-warnings
DEBUG: p5.34-html-parser requires: p5.34-html-tagset
p5.34-http-message p5.34-uri
DEBUG: p5.34-html-tagset requires: p5.34-test-simple
DEBUG: p5.34-http-message requires: p5.34-test-simple p5.34-clone p5.34-uri
DEBUG: p5.34-clone requires: p5.34-b-cow p5.34-test-simple
DEBUG: p5.34-b-cow requires: p5.34-test-simple
Error: Follow https://guide.macports.org/#project.tickets if you
believe there is a bug.
Error: Processing of port gnuplot failed

On Fri, Sep 20, 2024 at 2:39 PM Daniel J. Luke  wrote:
>
> On Sep 20, 2024, at 4:45 PM, Kenneth Wolcott  wrote:
> >  I don't think that I, as a MacPorts consumer (not developer) ,
> > should not have to do anything other than port commands to get around
> > this issue...even if I indirectly caused the problem by trying
> > deparately to install my way out of the issue...
>
> As far as I'm aware, dependencies are intended to be an acyclic graph.
>
> If there's a cycle, I'd say that's a bug and it would be reasonable to create 
> a ticket so the maintainer(s) can fix it.
>
> > If there is a port that I should uninstall that would break this
> > circular dependency hell, then please show me which one (or ones) will
> > solve the problem.  I suppose that I could try to list all my desired
> > ports as requested then uninstall everything and re-install?
>
> That's older migration method (and would be a reasonable thing to try).
>
> --
> Daniel J. Luke
>

the typescript port depends on an unsupported (upstream) version of nodejs

[Kenneth Wolcott]

Hi;

The typescript port depends on an unsupported (upstream) version of nodejs.

Is this something that upstream controls?

If not, is it possible to bump the version of nodejs typescript depends on?

I'm looking at using some features of nodejs22 can that conflicts...

so I have deactivated nodejs16...

Thanks,
Ken Wolcott

Re: more info regarding port setrequested; how to list what ports are already requested?

[Kenneth Wolcott]

Thank you!

On Sun, Sep 22, 2024 at 11:53 AM Chris Jones  wrote:
>
>
>
> > On 22 Sep 2024, at 7:30 pm, Kenneth Wolcott  
> > wrote:
> >
> > Hi;
> >
> >  man port
> >
> >  or
> >
> >  port help
> >
> >  does not clue me in; I need more info regarding port setrequested;
> > how to list what ports are already requested?
>
> > port echo requested
>
> >
> > Thanks,
> > Ken Wolcott

more info regarding port setrequested; how to list what ports are already requested?

[Kenneth Wolcott]

Hi;

  man port

  or

  port help

  does not clue me in; I need more info regarding port setrequested;
how to list what ports are already requested?

Thanks,
Ken Wolcott

sudo port diagnose Error: process_cmd failed: could not read "/opt/local/var/macports/incoming": no such file or directory

[Kenneth Wolcott]

Hi;

  This is a new error message in my experience:

sudo port diagnose Error: process_cmd failed: could not read
"/opt/local/var/macports/incoming": no such file or directory

MacOS 15.0 (Sequoia) arm64

Thanks,
Ken Wolcott

Re: During the octave port install from source I noticed that a fortran compiler was requested and not found

[Kenneth Wolcott]

Thank you, that helps a lot in my understanding of MacPorts, fortran
and ports requiring (or should be requiring) fortran.  I'll uninstall
the ports that were successfully installed prior to encountering the
perl circular depedency hell and log those unsuccessful searches for a
fortran compiler.  Then I'll create a bug report.

On Fri, Sep 20, 2024 at 3:31 PM Christopher Jones
 wrote:
>
> Hi
>
> The LLVM fortran compilers (flang) are very much ‘work in progress’ and far 
> from being ready for any production work. For that reason no port build will 
> currently consider them as a viable fortran compiler. They are provided ‘as 
> is’ to allow testing etc.
>
> Any port build that does require a fortran compiler should configure itself 
> to use one of the macports gfortran compilers, from one of the GCC ports. If 
> a build is failing to do this, that is an error in the port configuration.
>
> As always, emails to this list are not the correct way to report port bugs. 
> Please file as trac ticket with the usual information (full build logs) if 
> you want any progress on these issues.
>
> Chris
>
> n 20 Sep 2024, at 11:13 pm, Kenneth Wolcott  wrote:
> >
> > Hi;
> >
> > During the octave port install from source I noticed that a fortran
> > compiler was requested and not found
> >
> >  Since the octave port itself and its many dependencies heavily use
> > Fortran, it is puzzling to me that a working (suitable) Fortran
> > compiler is not required.
> >
> >  Many times (100s's??) an install step paused, looking for fortran
> > compiler, fails, continues...
> >
> >  I think I already had a Fortran compiler successfully installed (flang-19).
> >
> >  Is it possible, due to MacPorts naming schemes, that these packages
> > were unable to find the fortran compiler?
> >
> >  I am just learning how to use the numerical packages; I know that
> > Fortran is required for most of them to work properly; I'm curious
> > that the install casually going forwards without the Fortran compiler
> > is a good thing, but hey I'm the newbie here, what do I know...
> >
> > Thanks,
> > Ken Wolcott
>

During the octave port install from source I noticed that a fortran compiler was requested and not found

[Kenneth Wolcott]

Hi;

During the octave port install from source I noticed that a fortran
compiler was requested and not found

  Since the octave port itself and its many dependencies heavily use
Fortran, it is puzzling to me that a working (suitable) Fortran
compiler is not required.

  Many times (100s's??) an install step paused, looking for fortran
compiler, fails, continues...

  I think I already had a Fortran compiler successfully installed (flang-19).

  Is it possible, due to MacPorts naming schemes, that these packages
were unable to find the fortran compiler?

  I am just learning how to use the numerical packages; I know that
Fortran is required for most of them to work properly; I'm curious
that the install casually going forwards without the Fortran compiler
is a good thing, but hey I'm the newbie here, what do I know...

Thanks,
Ken Wolcott

Re: several ports cannot be installed due to a Perl circular dependency hell...

[Kenneth Wolcott]

Hi Gilles;

  This specific Perl circular dependency hell occurred only after the
update of the MacOS to Sequoia and the difficulties encountered when
trying to update MacPorts.

  I don't think that I, as a MacPorts consumer (not developer) ,
should not have to do anything other than port commands to get around
this issue...even if I indirectly caused the problem by trying
deparately to install my way out of the issue...

If there is a port that I should uninstall that would break this
circular dependency hell, then please show me which one (or ones) will
solve the problem.  I suppose that I could try to list all my desired
ports as requested then uninstall everything and re-install?

Thanks,
Ken Wolcott

On Fri, Sep 20, 2024 at 10:37 AM Gilles Caulier
 wrote:
>
> Hi,
>
> I faced the same problem while installing the huge list of
> dependencies for the digiKam project under Intel and arm64 targets.
>
> The main problem arrives when Perl is used to compile Qt in my case
> but not only. Look these rules in my install script :
>
> https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/01-build-macports.sh?ref_type=heads#L287
>
> https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/01-build-macports.sh?ref_type=heads#L296
>
> ... and all these patches for Perl :
>
> https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/macports/patches/perl?ref_type=heads
>
> ... and now everything works fine...
>
> Best
>
> Gilles Caulier
>
> Le ven. 20 sept. 2024 à 18:42, Kenneth Wolcott
>  a écrit :
> >
> > several ports cannot be installed due to a Perl circular dependency hell...
> >
> > eg:
> >
> > sudo port -v -s install maxima
> >
> > Error: The following dependencies were not installed because all of
> > them have unmet dependencies (likely due to a dependency cycle):
> > p5.34-authen-sasl p5.34-net-smtp-ssl p5.34-cgi
> > p5.34-pod-coverage-trustpod p5.34-test-simple p5.34-pod-eventual
> > p5.34-mixin-linewise p5.34-sub-exporter p5.34-data-optlist
> > p5.34-params-util p5.34-config-autoconf p5.34-file-slurper
> > p5.34-test-warnings p5.34-cpan-meta-check p5.34-module-pluggable
> > p5.34-module-runtime p5.34-module-build p5.34-software-license
> > p5.34-data-section p5.34-text-template p5.34-io-socket-ssl
> > p5.34-io-socket-ip p5.34-uri p5.34-html-parser p5.34-html-tagset
> > p5.34-http-message p5.34-clone p5.34-b-cow
> >
> > Thanks,
> > Ken Wolcott

Re: rust port complaint at time of selfupdate

[Kenneth Wolcott]

Hi;

  So how do I fix the problem?

  I have a similar problem with R now...

Failed to parse file R/R-pbdMPI/Portfile: can't read "mpi_port": no
such variable
Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
(1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)

On Wed, Sep 18, 2024 at 4:33 PM Austin Ziegler  wrote:
>
> I think that the `rust-bootstrap` port is supposed to track the `rust` port 
> and only the `rust` port has been updated recently.
>
> -a
>
> On Wed, Sep 18, 2024 at 6:22 PM Kenneth Wolcott  
> wrote:
>>
>> Hi;
>>
>>   Just did a selfupdate, there's an issue with the rust port...
>> 
>> Creating port index in
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
>> Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
>> (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)
>> 
>>
>> Thanks,
>> Ken Wolcott
>
>
>
> --
> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
> http://www.halostatue.ca/ • http://twitter.com/halostatue

several ports cannot be installed due to a Perl circular dependency hell...

[Kenneth Wolcott]

several ports cannot be installed due to a Perl circular dependency hell...

eg:

sudo port -v -s install maxima

Error: The following dependencies were not installed because all of
them have unmet dependencies (likely due to a dependency cycle):
p5.34-authen-sasl p5.34-net-smtp-ssl p5.34-cgi
p5.34-pod-coverage-trustpod p5.34-test-simple p5.34-pod-eventual
p5.34-mixin-linewise p5.34-sub-exporter p5.34-data-optlist
p5.34-params-util p5.34-config-autoconf p5.34-file-slurper
p5.34-test-warnings p5.34-cpan-meta-check p5.34-module-pluggable
p5.34-module-runtime p5.34-module-build p5.34-software-license
p5.34-data-section p5.34-text-template p5.34-io-socket-ssl
p5.34-io-socket-ip p5.34-uri p5.34-html-parser p5.34-html-tagset
p5.34-http-message p5.34-clone p5.34-b-cow

Thanks,
Ken Wolcott

cmake port looks for a fortran compiler, why? and doesn't find one, is this ok?

[Kenneth Wolcott]

Hi;

  While installing the rust port (compiling from source), cmake is a
dependency...

Why does the cmake port look for a fortran compiler?

It fails, seems ok, it goes on...

But  I've already installed gcc14 and I think that the fortran
compiler was installed, shouldn't cmake be shown that a fortran
instance exists?

What's the fallout from cmake not having a fortran compiler?

Thanks,
Ken Wolcott

Re: what setting to use to force only arm64 (Apple Silicon) binaries/libraries, no universal ports?

[Kenneth Wolcott]

Hi Joshua;

  That helps greatly; I'll make that change in macports.conf.

  But, is there a way to prevent x86_64 and amd64 ports from being
installed? If it is a port that I want but it does not support arm64,
I think I'd rather skip it if at all possible.

Thanks,
Ken Wolcott

On Wed, Sep 18, 2024 at 5:45 PM Joshua Root  wrote:
>
> Clearing universal_archs in macports.conf will disable universal entirely.
>
> Some ports that don't support arm64 may still install as x86_64 if they
> don't require any universal dependencies.
>
> - Josh
>

what setting to use to force only arm64 (Apple Silicon) binaries/libraries, no universal ports?

[Kenneth Wolcott]

Hi;

what setting to use to force only arm64 (Apple Silicon)
binaries/libraries, no universal ports?

I already use 'port -s install' and 'port -s upgrade', etc...

I understand that this won't work for dart and java (and others that
are similar) as they are SDK...

I also understand that a port that I might want might not exist for
arm64 (eg: dlang).

Thanks,
Ken Wolcott

rust port complaint at time of selfupdate

[Kenneth Wolcott]

Hi;

  Just did a selfupdate, there's an issue with the rust port...

Creating port index in
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version
(1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)


Thanks,
Ken Wolcott

my ports are screwed up after OS upgrade and port migrate; some things are fine, many are not

[Kenneth Wolcott]

Hi;

  I can't remember all steps that I took, but all I know now is that I
have a really confused MacPorts status.

First of all, I updated to the new MacOS, 15.0 (Sequoia).

Secondly, I think I selected the update to the Command line tools,
which showed up after the OS update completed.

Then I tried to download and install xCode v16.  Everything
***seemed*** fine at this point.

  I then ran sudo port migrate, and things went belly up.

current state:

following :

pkgutil 
--pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
2>/dev/null | sed -n 's/^version: //p'
16.0.0.0.1.1724870825

but

sudo port diagnose
Password:
Warning: No Xcode version info was found for your OS version.
Warning: The Xcode Command Line Tools package appears to be installed,
but its receipt appears to be missing.
Warning: The Command Line Tools may be outdated, which can cause problems.
Warning: Please see:


I tried many times to install, uninstall, install, upgrade various
ports.  Many fail, (especially low-level dependencies that most ports
require), looks like the tools are not visible...

  I'm stuck in a loop.

  Do I completely do a de-install of MacPorts?  But even then, that
won't solve the problem(s) with the SDK and Command Line tools...

  I was wondering if I should wait until longer update the OS, but I
thought I would go ahead...

  I had issues that I wanted to resolve with arm symbols not found
when running some of the ports (maybe my PATH is really screwed up
when building from source?)...

  So I tried to install some ports as binaries, but some could not be
found for arm64, so that failed.

  I know that clang and clang++ have been updated successfully and all
the things that I have built outside of MacPorts appear to work, but
only some (very few) of the ports work or even exist now.

So, what's my next step?  Re-install the OS? Yikes.

Thanks,
Ken Wolcott

Sigh...

Re: asymptote port install is hanging, nothing seems amiss, puzzling

[Kenneth Wolcott]

Hmmm...

1. sudo port -v -s install asymptote

2. it hangs...

3. killed the hanging command

4. sudo port clean asymptote

5. sudo port -v -s install asymptote

Works fine...

Interesting...

Thanks,
Ken Wolcott

On Thu, Sep 12, 2024 at 12:06 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   The asymptote port install is hanging, nothing seems amiss, puzzling...
>
>   last output:
>
> ...
> Transcript written on latexusage.log.
>
> Is this a known issue?
>
> Thanks,
> Ken Wolcott

asymptote port install is hanging, nothing seems amiss, puzzling

[Kenneth Wolcott]

Hi;

  The asymptote port install is hanging, nothing seems amiss, puzzling...

  last output:

...
Transcript written on latexusage.log.

Is this a known issue?

Thanks,
Ken Wolcott

circular dependency between qemu and dtc

[Kenneth Wolcott]

circular dependency between qemu and dtc

self-update

qemu fails due to conflict with dtc

deactivating dtc then trying to update qemu fails because it activates dtc

~: sudo port uninstall dtc
--->  Uninstalling dtc @1.7.0_0
--->  Cleaning dtc
~: sudo port upgrade qemu
--->  Computing dependencies for dtc
--->  Installing dtc @1.7.0_0
--->  Activating dtc @1.7.0_0
Error: Failed to activate dtc: The following ports have active files
that conflict with dtc's:
qemu 
@9.0.2_0+cocoa+curses+spice+spice_protocol+target_arm+target_i386+target_x86_64+usb+vnc
  /opt/local/include/fdt.h
  /opt/local/include/libfdt.h
  /opt/local/include/libfdt_env.h
  /opt/local/lib/libfdt.a
Image error: Conflicting file(s) present. Please deactivate the
conflicting port(s) first, or use 'port -f activate dtc' to force the
activation.
while executing
"throw registry::image-error $msg"
("foreach" body line 35)
invoked from within
"foreach file $imagefiles {
incr progress_step
_progress update $progress_step $progress_total_steps
se..."
invoked from within
"registry::write {
foreach file $imagefiles {
incr progress_step
_progress update $progress_step $progress_..."
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_cross_dtc/dtc/main.log
for details.
Error: Problem while installing dtc
Error: Follow https://guide.macports.org/#project.tickets if you
believe there is a bug.
~: sudo port uninstall qemu
Note: It is not recommended to uninstall/deactivate a port that has
dependents as it breaks the dependents.
The following ports will break:
 macpine @1.0.5_0
 lima @0.22.0_0
 lima @0.22.0_1
 lima @0.23.1_0
Continue? [y/N]: y
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating qemu
@9.0.2_0+cocoa+curses+spice+spice_protocol+target_arm+target_i386+target_x86_64+usb+vnc
--->  Cleaning qemu
--->  Uninstalling qemu
@9.0.2_0+cocoa+curses+spice+spice_protocol+target_arm+target_i386+target_x86_64+usb+vnc
--->  Cleaning qemu
~: sudo port uninstall qemu
~: sudo port install qemu
--->  Computing dependencies for qemu
The following dependencies will be installed:  dtc
Continue? [Y/n]: n
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.
~: sudo port install dtc
--->  Activating dtc @1.7.0_0
--->  Cleaning dtc
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.
~: sudo port deactivate dtc
--->  Deactivating dtc @1.7.0_0
--->  Cleaning dtc
~: sudo port install qemu
--->  Computing dependencies for qemu
The following dependencies will be installed:  dtc
Continue? [Y/n]: n
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.


Looks fishy...

Thanks,
Ken Wolcott

Re: port outdated complains after self-update to version 2.10 of MacPorts

[Kenneth Wolcott]

Thank you, seems to be fixed by 'sudo port outdated'.

On Wed, Aug 7, 2024 at 2:57 PM Joshua Root  wrote:
>
> > port outdated
> > sqlite error: attempt to write a readonly database (8) while executing
> > query: CREATE INDEX registry.snapshot_file_id ON snapshot_files(id)
> >  while executing
> > "registry::open $db_path"
> >  (procedure "mportinit" line 832)
> >  invoked from within
> > "mportinit ui_options global_options global_variations"
> > Error: /opt/local/bin/port: Failed to initialize MacPorts, sqlite
> > error: attempt to write a readonly database (8) while executing query:
> > CREATE INDEX registry.snapshot_file_id ON snapshot_files(id)
>
> I'm not sure why that registry update didn't happen during installation,
> but it just needs write access to the database to succeed now, so
> running any port command with sudo should fix it.
>
> - Josh
>

port outdated complains after self-update to version 2.10 of MacPorts

[Kenneth Wolcott]

port outdated
sqlite error: attempt to write a readonly database (8) while executing
query: CREATE INDEX registry.snapshot_file_id ON snapshot_files(id)
while executing
"registry::open $db_path"
(procedure "mportinit" line 832)
invoked from within
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, sqlite
error: attempt to write a readonly database (8) while executing query:
CREATE INDEX registry.snapshot_file_id ON snapshot_files(id)

Re: is there a MacPorts port that converts ppm files to png format?

[Kenneth Wolcott]

Thank you!

On Thu, Jun 20, 2024 at 7:02 PM Richard L. Hamilton  wrote:
>
> netpbm port contains pnmtopng, a command line tool.
>
>
> > On Jun 20, 2024, at 21:44, Kenneth Wolcott  wrote:
> >
> > Hi;
> >
> > is there a MacPorts port that converts ppm files to png format?
> >
> > If not, is there an open source tool that does this?
> >
> > Is there a free MacOS tool that does this?
> >
> > I don't want to use an on-line tool and I don't want to pay for such a tool.
> >
> > Thanks,
> > Ken Wolcott
> >
>

Re: is there a MacPorts port that converts ppm files to png format?

[Kenneth Wolcott]

Hi;

 Dumb question, sorry.

Of course, convert (from ImageMagick) will do what I want.

convert ./bitmap.ppm ./bitmap.png

Thanks for letting me waste your time.

Ken Wolcott

On Thu, Jun 20, 2024 at 6:44 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
> is there a MacPorts port that converts ppm files to png format?
>
> If not, is there an open source tool that does this?
>
> Is there a free MacOS tool that does this?
>
> I don't want to use an on-line tool and I don't want to pay for such a tool.
>
> Thanks,
> Ken Wolcott

is there a MacPorts port that converts ppm files to png format?

[Kenneth Wolcott]

Hi;

is there a MacPorts port that converts ppm files to png format?

If not, is there an open source tool that does this?

Is there a free MacOS tool that does this?

I don't want to use an on-line tool and I don't want to pay for such a tool.

Thanks,
Ken Wolcott

just updated octave: warning: directory .turd_octave is not a valid package

[Kenneth Wolcott]

Hi;

recreating package description from .turd_octave
warning: directory .turd_octave is not a valid package
warning: called from
rebuild at line 71 column 7
pkg at line 707 column 25

Amusing :-)

Should I be concerned?

Thanks,
Ken Wolcott

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Hi, me again :-)

I removed my local installation of Primesieve from /usr/local since
I'm now using the Primesieve from MacPorts.

Now the Perl Primsieve module fails to work because it expects the
Primesieve library to be there.

I could never get the Raku Primesieve module to install, keeps
complaining about not being able to find the Primesieve library.

So, it would be great if the Primesieve bindings could also become a
port (Nim, Perl, Ruby, Raku, Python, ?)

Thanks,
Ken Wolcott

On Sat, May 25, 2024 at 12:31 PM Kenneth Wolcott
 wrote:
>
> Wow!  Someone did the PrimeSieve port already!  I missed that! WOW!
>
> On Sat, May 25, 2024 at 12:28 PM Kenneth Wolcott
>  wrote:
> >
> > Hi All;
> >
> >   Revisiting an old thread.
> >
> >   I'm able to compile Primesieve.
> >
> >   However, it automatically installs to /usr/local (good place by default).
> >
> >  Later, MacPorts complains about includes and libraries located in 
> > /usr/local...
> >
> > So I was looking at the distribution to see how to convince the
> > Primesieve build process to install to, say, "/opt/primesieve".
> >
> > Looking at the CMakeLists.txt makes me very leery of making changes;
> > it's not like using "--configure" :-)
> >
> > I see that Primesieve is supported by Brew; it would be nice if
> > someone just a bit more experienced than I am would make a port...
> >
> > Thanks,
> > Ken Wolcott
> >
> > On Wed, Dec 20, 2023 at 8:13 PM Kenneth Wolcott
> >  wrote:
> > >
> > > Hi Ken C;
> > >
> > >   Thank you for the hint.  I have gcc13 for Ada installed and I think
> > > that the gcc got picked up (it has C as well, not pure Ada, so that
> > > Ada can link up with C).
> > >
> > >   Sometimes I think it would be great to have three (or more!)
> > > different Macs so that I can customize things without conflicts.  I
> > > guess Docker is the only way to meaningfully do that (I don't have
> > > enough money or space to have that many Mac machines!)
> > >
> > > Thanks,
> > > Ken W

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Wow!  Someone did the PrimeSieve port already!  I missed that! WOW!

On Sat, May 25, 2024 at 12:28 PM Kenneth Wolcott
 wrote:
>
> Hi All;
>
>   Revisiting an old thread.
>
>   I'm able to compile Primesieve.
>
>   However, it automatically installs to /usr/local (good place by default).
>
>  Later, MacPorts complains about includes and libraries located in 
> /usr/local...
>
> So I was looking at the distribution to see how to convince the
> Primesieve build process to install to, say, "/opt/primesieve".
>
> Looking at the CMakeLists.txt makes me very leery of making changes;
> it's not like using "--configure" :-)
>
> I see that Primesieve is supported by Brew; it would be nice if
> someone just a bit more experienced than I am would make a port...
>
> Thanks,
> Ken Wolcott
>
> On Wed, Dec 20, 2023 at 8:13 PM Kenneth Wolcott
>  wrote:
> >
> > Hi Ken C;
> >
> >   Thank you for the hint.  I have gcc13 for Ada installed and I think
> > that the gcc got picked up (it has C as well, not pure Ada, so that
> > Ada can link up with C).
> >
> >   Sometimes I think it would be great to have three (or more!)
> > different Macs so that I can customize things without conflicts.  I
> > guess Docker is the only way to meaningfully do that (I don't have
> > enough money or space to have that many Mac machines!)
> >
> > Thanks,
> > Ken W

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Hi All;

  Revisiting an old thread.

  I'm able to compile Primesieve.

  However, it automatically installs to /usr/local (good place by default).

 Later, MacPorts complains about includes and libraries located in /usr/local...

So I was looking at the distribution to see how to convince the
Primesieve build process to install to, say, "/opt/primesieve".

Looking at the CMakeLists.txt makes me very leery of making changes;
it's not like using "--configure" :-)

I see that Primesieve is supported by Brew; it would be nice if
someone just a bit more experienced than I am would make a port...

Thanks,
Ken Wolcott

On Wed, Dec 20, 2023 at 8:13 PM Kenneth Wolcott
 wrote:
>
> Hi Ken C;
>
>   Thank you for the hint.  I have gcc13 for Ada installed and I think
> that the gcc got picked up (it has C as well, not pure Ada, so that
> Ada can link up with C).
>
>   Sometimes I think it would be great to have three (or more!)
> different Macs so that I can customize things without conflicts.  I
> guess Docker is the only way to meaningfully do that (I don't have
> enough money or space to have that many Mac machines!)
>
> Thanks,
> Ken W

reexported library with install name '@rpath/libunwind.1.dylib' ...couldn't be matched with any parent library

[Kenneth Wolcott]

Hi;

I just installed flang-18 from Macports, installed from source.

I created the following symlink manually for my convenience.

ls -ld /opt/local/bin/flang
lrwxr-xr-x  1 root  wheel  26 May  5 22:16 /opt/local/bin/flang ->
/opt/local/bin/flang-mp-18

Here's a simple Fortran source file:

cat ./hello.f90
program hello
  ! This is a comment line; it is ignored by the compiler
  print *, 'Hello, World!'
end program hello

flang -x none -o ./hello ./hello.f90
ld: warning: reexported library with install name
'@rpath/libunwind.1.dylib' found at
'/opt/local/libexec/llvm-18/lib/libunwind.1.0.dylib' couldn't be
matched with any parent library and will be linked directly

flang -o ./hello ./hello.f90
ld: warning: reexported library with install name
'@rpath/libunwind.1.dylib' found at
'/opt/local/libexec/llvm-18/lib/libunwind.1.0.dylib' couldn't be
matched with any parent library and will be linked directly

file ./hello
./hello: Mach-O 64-bit arm64 executable,
flags:

  Is this a known issue?

Thanks,
Ken Wolcott

Re: where is the MacPorts gcc?

[Kenneth Wolcott]

HI Ryan;

  I'll try to create a MNWE (Minimal Non-Working Example) but it will
take some time as I suspect that involves the gsl library.

Thanks,
Ken W

On Sat, May 4, 2024 at 12:22 AM Ryan Schmidt  wrote:
>
> On May 3, 2024, at 23:12, Kenneth Wolcott wrote:
> >
> > I want to compile some C code using gcc to compare against clang.
> >
> > This code I want to compile needs gsl/gsl_vector.h so I used -lgsl to
> > compile with clang and it complained at runtime: "dyld[16321]: missing
> > symbol called".
>
> Since using gcc on macOS is unusual and possibly fraught with its own unique 
> problems, and you encounter the issue with clang as well, let's focus on 
> clang first.
>
> Can you provide a minimal reproduction recipe? A .c file and the command you 
> used to compile and link it that demonstrates the problem and that we can try 
> on our systems?
>
>

Re: where is the MacPorts gcc?

[Kenneth Wolcott]

I get the same runtime error when using gcc:

/opt/local/bin/arm64-apple-darwin23-gcc-mp-12 -lgsl -o
./polynomial_long_division ./polynomial_long_division.c
-macosx_version_min has been renamed to -macos_version_min

./polynomial_long_division
dyld[16552]: missing symbol called
zsh: abort  ./polynomial_long_division

On Fri, May 3, 2024 at 9:12 PM Kenneth Wolcott  wrote:
>
> I want to compile some C code using gcc to compare against clang.
>
> This code I want to compile needs gsl/gsl_vector.h so I used -lgsl to
> compile with clang and it complained at runtime: "dyld[16321]: missing
> symbol called".
>
> what are "ar" and "nm" in the following?
>
> I think "mp" means multiple precision...
>
> find /opt/local/bin -type f -print | grep gcc | grep -v ranlib
> /opt/local/bin/arm64-apple-darwin23-gcc-ar-mp-13
> /opt/local/bin/gcc-mp-12
> /opt/local/bin/arm64-apple-darwin23-gcc-ar-mp-12
> /opt/local/bin/gcc-mp-13
> /opt/local/bin/arm64-apple-darwin23-gcc-13.2.0
> /opt/local/bin/gcc-nm-mp-13
> /opt/local/bin/gcc-nm-mp-12
> /opt/local/bin/arm64-apple-darwin23-gcc-mp-12
> /opt/local/bin/arm64-apple-darwin23-gcc-mp-13
> /opt/local/bin/arm64-apple-darwin23-gcc-nm-mp-12
> /opt/local/bin/arm64-apple-darwin23-gcc-nm-mp-13
> /opt/local/bin/gcc-ar-mp-12
> /opt/local/bin/gcc-ar-mp-13
> /opt/local/bin/arm64-apple-darwin23-gcc-12.3.0
>
> Thanks,
> Ken Wolcott

where is the MacPorts gcc?

[Kenneth Wolcott]

I want to compile some C code using gcc to compare against clang.

This code I want to compile needs gsl/gsl_vector.h so I used -lgsl to
compile with clang and it complained at runtime: "dyld[16321]: missing
symbol called".

what are "ar" and "nm" in the following?

I think "mp" means multiple precision...

find /opt/local/bin -type f -print | grep gcc | grep -v ranlib
/opt/local/bin/arm64-apple-darwin23-gcc-ar-mp-13
/opt/local/bin/gcc-mp-12
/opt/local/bin/arm64-apple-darwin23-gcc-ar-mp-12
/opt/local/bin/gcc-mp-13
/opt/local/bin/arm64-apple-darwin23-gcc-13.2.0
/opt/local/bin/gcc-nm-mp-13
/opt/local/bin/gcc-nm-mp-12
/opt/local/bin/arm64-apple-darwin23-gcc-mp-12
/opt/local/bin/arm64-apple-darwin23-gcc-mp-13
/opt/local/bin/arm64-apple-darwin23-gcc-nm-mp-12
/opt/local/bin/arm64-apple-darwin23-gcc-nm-mp-13
/opt/local/bin/gcc-ar-mp-12
/opt/local/bin/gcc-ar-mp-13
/opt/local/bin/arm64-apple-darwin23-gcc-12.3.0

Thanks,
Ken Wolcott

Re: Lilypond documentation (info+man) installation?

[Kenneth Wolcott]

Hi;

  Thanks for your responses, Richard and Werner.

  I went ahead and downloaded the Documentation package from the
Lilypond website for vesion 2.24.3, unpacked it and updated my MANPAGE
and INFOPAGE environment variables and now I have access tothe
Lilypond man pages and info pages.

Thanks,
Ken Wolcott

On Fri, Apr 19, 2024 at 9:27 PM Werner LEMBERG  wrote:
>
>
> > I'd say build it with +docs, but that failed for me:
> >
> > :info:build Making Documentation/out/lilypond-contributor.info < texi
> > :info:build bibtex: Not writing to 
> > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_lilypond/lilypond/work/.tmp/tmpy0vuau0_/bib2texi-tmp.blg
> >  (openout_any = p; no  extended check).
> > :info:build bibtex exited with return code 1.
> >
> > [...]
>
> This is new.  Most certainly `+docs` worked some time ago (at least on
> my old Lion box, to which I won't have access in the near future
> unfortunately).  What might be the reason of this failure?  I've never
> seen this message before.
>
> >> 2. Actually generate the documentation?
>
> Only non-image info pages and man pages are generated and installed by
> `+docs`; support for creating the remaining documentation files on a
> Mac is yet to be done.  Any volunteers?
>
>
> Werner

Lilypond documentation (info+man) installation?

[Kenneth Wolcott]

Hi;

  I've been using Lilypond via MacPorts for some while now.

  I've been using Lilypond documentation from the Lilypond website in
html form (sometimes from pdf).

  What I don't have is the documentation from MacPorts Lilypond in the
info and/or man format.

man lilypond
No manual entry for lilypond

info lilypond
info: No menu item 'lilypond' in node '(dir)Top'

echo $MANPATH
/opt/local/share/man:/opt/local/share/man:

echo $INFOPATH
/opt/local/share/info

  Is this something that I have to do manually to get access to:
1. modify settings in my profile?
and/or
2. Actually generate the documentation?

3. Perhaps the Lilypond documentation is just not available via MacPorts...?

Thanks,
Ken Wolcott

Re: what app on a Mac reads/views ppm files?

[Kenneth Wolcott]

Thanks to you all for your responses.

Looks like Preview wins out (built-in :-) ), didn't want to purchase
an app, but the quality of the image matters, if the image has one
pixel, it doesn't seem to appear :-)

Thanks,
Ken Wolcott

On Wed, Apr 17, 2024 at 8:38 AM Bill Cole
 wrote:
>
> On 2024-04-16 at 22:44:22 UTC-0400 (Tue, 16 Apr 2024 19:44:22 -0700)
> Kenneth Wolcott 
> is rumored to have said:
>
> > Hi;
> >
> >   what app on a Mac reads/views ppm files?
> >
> >   I've been looking at some code located on Rosetta Code that involves
> > ppm files... https://rosettacode.org/wiki/Bitmap/Read_a_PPM_file
>
> For a very long time, I've relied on GraphicConverter, which opens and saves 
> a huge variety of formats including PPM, according to this page: 
> https://www.lemkesoft.de/en/products/graphicconverter/key-features/import-and-export-formats
>
> I have not personally used it with PPMs, but it has given me usable 
> conversions of many other formats. It's a decent general-use graphics editor 
> as well.
>
>
> --
> Bill Cole

what app on a Mac reads/views ppm files?

[Kenneth Wolcott]

Hi;

  what app on a Mac reads/views ppm files?

  I've been looking at some code located on Rosetta Code that involves
ppm files... https://rosettacode.org/wiki/Bitmap/Read_a_PPM_file

Thanks,
Ken Wolcott

Re: what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?)

[Kenneth Wolcott]

Hi Joshua;

Thanks for the tip...

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...

Thanks,
Ken W.

On Thu, Apr 11, 2024 at 11:00 PM Joshua Root  wrote:
>
> > what MacPorts port would create a TAGS file (looks like a history
> > helper, rlwrap?)
>
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Tags-Tables.html
>
>

what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?)

[Kenneth Wolcott]

Hi;

what MacPorts port would create a TAGS file (looks like a history
helper, rlwrap?)

Is there a command (or method) to determine which app creates this file?

It was written at the top of my local git repo.  That's NOT a good
place for this file and I didn't create it directly.  It looks like a
command history with embedded page breaks (file output says it is
data, but I was able to look at it with less, after the warning that
it might be a binary file).

Perhaps an environment variable needs to be set to a specific path for this app?

Thanks,
Ken Wolcott

Re: always have broken files at the end of a self-update

[Kenneth Wolcott]

Thank you for the explanation.

Thanks,
Ken Wolcott

On Tue, Apr 9, 2024 at 11:19 AM Ryan Schmidt  wrote:
>
> On Apr 9, 2024, at 13:02, Kenneth Wolcott wrote:
>
>
> At the end of each self-update I get the following error message, in
> spite of whether I respond with yes or no:
>
> 
> --->  Updating database of binaries
>
> --->  Scanning binaries for linking errors
>
> Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or
> reading file (referenced from
> /opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib)
>
> --->  Found 6 broken files, matching files to ports
>
> --->  Found 1 broken port, determining rebuild order
>
> You can always run 'port rev-upgrade' again to fix errors.
>
> The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11
>
>
> This problem will continue until this ticket is resolved:
>
> https://trac.macports.org/ticket/69640
>

always have broken files at the end of a self-update

[Kenneth Wolcott]

At the end of each self-update I get the following error message, in
spite of whether I respond with yes or no:


--->  Updating database of binaries

--->  Scanning binaries for linking errors

Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or
reading file (referenced from
/opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib)

--->  Found 6 broken files, matching files to ports

--->  Found 1 broken port, determining rebuild order

You can always run 'port rev-upgrade' again to fix errors.

The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11



I get the following warning:
sudo port diagnose
Password:
Warning: found dylibs in your /usr/local/lib directory. These are
known to cause problems. We'd recommend you remove them.
Warning: found header files in your /usr/local/include directory.
These are known to cause problems. We'd recommend you remove them.

ls /usr/local/lib
cmake docker libgmp.a libgmp.la libprimesieve.a perl5 pkgconfig

sudo /bin/rm /usr/local/lib/libgmp.a
sudo /bin/rm /usr/local/lib/libgmp.la
sudo /bin/rm /usr/local/lib/libprimesieve.a

ls /usr/local/include
pari primesieve primesieve.hpp

sudo /bin/rm /usr/local/include/primesieve.hpp

sudo port diagnose [no output!]

Now when doing self-update when there's nothing new in ports I get this:

port outdated
The following installed ports are outdated:
borgbackup 1.2.7_1 < 1.2.8_1
mpv0.37.0_2 < 0.37.0_3
octave 8.4.0_2 < 9.1.0_0

This is a different issue which I will discuss in a different email.

Now when I have an upgrade or install will I still have a broken link
error message at the end of the port upgrade or install process?

I have a build log (attached, since it is very small).

Thanks,
Ken Wolcott


build_failed_webkit2-gtk.log
Description: Binary data

Re: DMD port

[Kenneth Wolcott]

Sounds good!

On Mon, Mar 11, 2024 at 7:20 PM P Padil  wrote:
>
> Dmd apparently doesn’t support Apple Silicon compilation, at least that is 
> what is stated in their compiler docs. I still tried to compile the source 
> but got an error message that it doesn’t recognize the system.  Noted that 
> gcc and ldc compilers do support Apple arm processor.  I’m planning to update 
> the gcc13 port to add D, and add a new port for ldc compiler (llvm based).
>
> > On Mar 11, 2024, at 3:10 PM, Kenneth Wolcott  
> > wrote:
> >
> > Awesome!  Good luck! Looking forward to this...
> >
> > On Mon, Mar 11, 2024 at 2:38 PM P Padil  wrote:
> >>
> >> The port doesn’t have a maintainer, I’m going to update the port file and 
> >> submit it to macports via github pull as per the instructions.  Since I’m 
> >> new to portfiles it may take some time...
> >>
> >>> On Mar 11, 2024, at 12:25 PM, Kenneth Wolcott  
> >>> wrote:
> >>>
> >>> Hi All;
> >>>
> >>> Not only that, but could there be a version for Apple Silicon? I've
> >>> been using a Docker container for DMD; not really convenient...
> >>>
> >>> Thanks,
> >>> Ken
> >>>
> >>> On Mon, Mar 11, 2024 at 11:50 AM P Padil  wrote:
> >>>>
> >>>> The dmd port is still at version 2.088 while upstream is at 2.107.1.  
> >>>> Any reason it is still stuck at this ancient version?  Can it be updated?
> >>>>
> >>>> Regards
> >>>>
> >>
>

Re: DMD port

[Kenneth Wolcott]

Awesome!  Good luck! Looking forward to this...

On Mon, Mar 11, 2024 at 2:38 PM P Padil  wrote:
>
> The port doesn’t have a maintainer, I’m going to update the port file and 
> submit it to macports via github pull as per the instructions.  Since I’m new 
> to portfiles it may take some time...
>
> > On Mar 11, 2024, at 12:25 PM, Kenneth Wolcott  
> > wrote:
> >
> > Hi All;
> >
> >  Not only that, but could there be a version for Apple Silicon? I've
> > been using a Docker container for DMD; not really convenient...
> >
> > Thanks,
> > Ken
> >
> > On Mon, Mar 11, 2024 at 11:50 AM P Padil  wrote:
> >>
> >> The dmd port is still at version 2.088 while upstream is at 2.107.1.  Any 
> >> reason it is still stuck at this ancient version?  Can it be updated?
> >>
> >> Regards
> >>
>

Re: DMD port

[Kenneth Wolcott]

Hi All;

  Not only that, but could there be a version for Apple Silicon? I've
been using a Docker container for DMD; not really convenient...

Thanks,
Ken

On Mon, Mar 11, 2024 at 11:50 AM P Padil  wrote:
>
> The dmd port is still at version 2.088 while upstream is at 2.107.1.  Any 
> reason it is still stuck at this ancient version?  Can it be updated?
>
> Regards
>

Re: Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

Whoever fixed borgbackup, I appreciate it.  It is a great relief to
have backups working again.

Thanks,
Ken Wolcott

On Sun, Mar 3, 2024 at 5:58 PM Kenneth Wolcott  wrote:
>
> It loos like this problem has re-appeared :-(
>
> You do not have a supported version of the msgpack python package
> installed. Terminating.
> This should never happen as specific, supported versions are required
> by our setup.py.
> Do not contact borgbackup support about this.
> terminating with error status, rc 2
>
> port installed | grep msgpack
>   msgpack @4_0 (active)
>   msgpack-c @4.0.0_0
>   msgpack-c @6.0.0_0 (active)
>   msgpack-cpp @4.1.1_0
>   msgpack-cpp @6.0.0_0
>   msgpack-cpp @6.1.0_0 (active)
>   py312-msgpack @1.0.7_1
>   py312-msgpack @1.0.8_0 (active)
>
> port installed | grep borgbackup
>   borgbackup @1.2.7_0 (active)
>
>   Do I need to re-activate the prior version of py312-msgpack?
>
>   Is there a way to prevent this going forwards?
>
> Thanks,
> Ken Wolcott
>
> On Fri, Jan 5, 2024 at 6:11 AM Joshua Root  wrote:
> >
> > On 6/1/2024 00:07, Clemens Lang wrote:
> > > Actually, the relevant commit is
> > > https://github.com/borgbackup/borg/commit/39761ebadc9325a7cc7e931144e2709effe8f0f0,
> > > and that has been backported to the 1.2 branch of borgbackup and is in
> > > 1.2.7, so just make sure you have the latest borgbackup installed and it
> > > should start working again.
> >
> > Yes, updating to 1.2.7 was the resolution to the ticket that was opened
> > about this. <https://trac.macports.org/ticket/68998>
> >
> > - Josh

Re: Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

It loos like this problem has re-appeared :-(

You do not have a supported version of the msgpack python package
installed. Terminating.
This should never happen as specific, supported versions are required
by our setup.py.
Do not contact borgbackup support about this.
terminating with error status, rc 2

port installed | grep msgpack
  msgpack @4_0 (active)
  msgpack-c @4.0.0_0
  msgpack-c @6.0.0_0 (active)
  msgpack-cpp @4.1.1_0
  msgpack-cpp @6.0.0_0
  msgpack-cpp @6.1.0_0 (active)
  py312-msgpack @1.0.7_1
  py312-msgpack @1.0.8_0 (active)

port installed | grep borgbackup
  borgbackup @1.2.7_0 (active)

  Do I need to re-activate the prior version of py312-msgpack?

  Is there a way to prevent this going forwards?

Thanks,
Ken Wolcott

On Fri, Jan 5, 2024 at 6:11 AM Joshua Root  wrote:
>
> On 6/1/2024 00:07, Clemens Lang wrote:
> > Actually, the relevant commit is
> > https://github.com/borgbackup/borg/commit/39761ebadc9325a7cc7e931144e2709effe8f0f0,
> > and that has been backported to the 1.2 branch of borgbackup and is in
> > 1.2.7, so just make sure you have the latest borgbackup installed and it
> > should start working again.
>
> Yes, updating to 1.2.7 was the resolution to the ticket that was opened
> about this. 
>
> - Josh

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

[Kenneth Wolcott]

Ah!!! Thank you.

On Fri, Mar 1, 2024 at 8:43 PM Dave Allured - NOAA Affiliate
 wrote:
>
> Yes, that is it.  Macports implementation decided to decorate the name of the 
> executable.  There is no naked "gfortran".  It is gfortran-mp-12, 
> gfortran-mp-13, etc.  This way you can have multiple versions installed side 
> by side, if you wish.  For convenience, I usually sym link "gfortran" to the 
> latest MP version.
>
>
> On Fri, Mar 1, 2024 at 9:35 PM Kenneth Wolcott  
> wrote:
>>
>> Should I be using gfortran-mp-13?
>>
>> ls /opt/local/bin | grep fortran
>> arm64-apple-darwin23-gfortran-mp-12
>> arm64-apple-darwin23-gfortran-mp-13
>> gfortran-mp-12
>> gfortran-mp-13
>> lfortran
>>
>> On Fri, Mar 1, 2024 at 8:28 PM Kenneth Wolcott  
>> wrote:
>> >
>> > I do have a GNAT Ada compiler located at:
>> >
>> > /opt/gcc-13.2.0-aarch64
>> >
>> > Does the existence of this confuse or mislead MacPorts?
>> >
>> > Thanks,
>> > Ken W.
>> >
>> > On Fri, Mar 1, 2024 at 8:24 PM Kenneth Wolcott  
>> > wrote:
>> > >
>> > > Hi Joshua;
>> > >
>> > > port contents gcc13 | grep gfortran
>> > >   /opt/local/bin/arm64-apple-darwin23-gfortran-mp-13
>> > >   /opt/local/bin/gfortran-mp-13
>> > >   /opt/local/lib/gcc13/libgfortran.5.dylib
>> > >   /opt/local/lib/gcc13/libgfortran.a
>> > >   /opt/local/lib/gcc13/libgfortran.dylib
>> > >   /opt/local/lib/gcc13/libgfortran.spec
>> > >   /opt/local/share/info/gfortran-mp-13.info
>> > >   /opt/local/share/man/man1/gfortran-mp-13.1.gz
>> > > ~:
>> > >
>> > > But "ls /usr/local/bin | grep -i fortran"
>> > >
>> > > Has no output. ??!!
>> > >
>> > > Thanks,
>> > > Ken W.
>> > >
>> > > On Fri, Mar 1, 2024 at 7:19 PM Joshua Root  wrote:
>> > > >
>> > > > Are you sure of that? Check e.g. 'port contents gcc13 | grep gfortran'.
>> > > >
>> > > > - Josh
>> > > >
>> > > > Kenneth Wolcott wrote:
>> > > >
>> > > > > Hi Noam;
>> > > > >
>> > > > >I do not have gfortran, therefore I must not have gcc?
>> > > > >
>> > > > > Here is a filtered list of the ports that I have installed that 
>> > > > > pertain to gcc:
>> > > > >gcc12 @12.3.0_4+stdlib_flag (active)
>> > > > >gcc12-libcxx @12.3.0_4+clang14 (active)
>> > > > >gcc13 @13.2.0_4+stdlib_flag (active)
>> > > > >gcc13-libcxx @13.2.0_4+clang16 (active)
>> > > > >gcc_select @0.1_10 (active)
>> > > > >libgcc @7.0_0 (active)
>> > > > >libgcc12 @12.3.0_4+stdlib_flag (active)
>> > > > >libgcc13 @13.2.0_4+stdlib_flag (active)
>> > > > >mpich-default @4.1.2_2+gcc13 (active)
>> > > > >
>> > > > > Still confused...
>> > > > >
>> > > > > Thanks,
>> > > > > Ken W.
>> > > > >
>> > > > > On Fri, Mar 1, 2024 at 6:03 PM Bernstein, Noam CIV USN NRL WASHINGTON
>> > > > > DC (USA) > > > > > <https://lists.macports.org/mailman/listinfo/macports-users>> wrote:
>> > > > > >//>/Pretty sure that macports gcc installs gfortran by default, 
>> > > > > >which is
>> > > > > a f90 (and 95, and maybe f2003) compiler./
>> > > >

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

[Kenneth Wolcott]

Should I be using gfortran-mp-13?

ls /opt/local/bin | grep fortran
arm64-apple-darwin23-gfortran-mp-12
arm64-apple-darwin23-gfortran-mp-13
gfortran-mp-12
gfortran-mp-13
lfortran

On Fri, Mar 1, 2024 at 8:28 PM Kenneth Wolcott  wrote:
>
> I do have a GNAT Ada compiler located at:
>
> /opt/gcc-13.2.0-aarch64
>
> Does the existence of this confuse or mislead MacPorts?
>
> Thanks,
> Ken W.
>
> On Fri, Mar 1, 2024 at 8:24 PM Kenneth Wolcott  
> wrote:
> >
> > Hi Joshua;
> >
> > port contents gcc13 | grep gfortran
> >   /opt/local/bin/arm64-apple-darwin23-gfortran-mp-13
> >   /opt/local/bin/gfortran-mp-13
> >   /opt/local/lib/gcc13/libgfortran.5.dylib
> >   /opt/local/lib/gcc13/libgfortran.a
> >   /opt/local/lib/gcc13/libgfortran.dylib
> >   /opt/local/lib/gcc13/libgfortran.spec
> >   /opt/local/share/info/gfortran-mp-13.info
> >   /opt/local/share/man/man1/gfortran-mp-13.1.gz
> > ~:
> >
> > But "ls /usr/local/bin | grep -i fortran"
> >
> > Has no output. ??!!
> >
> > Thanks,
> > Ken W.
> >
> > On Fri, Mar 1, 2024 at 7:19 PM Joshua Root  wrote:
> > >
> > > Are you sure of that? Check e.g. 'port contents gcc13 | grep gfortran'.
> > >
> > > - Josh
> > >
> > > Kenneth Wolcott wrote:
> > >
> > > > Hi Noam;
> > > >
> > > >I do not have gfortran, therefore I must not have gcc?
> > > >
> > > > Here is a filtered list of the ports that I have installed that pertain 
> > > > to gcc:
> > > >gcc12 @12.3.0_4+stdlib_flag (active)
> > > >gcc12-libcxx @12.3.0_4+clang14 (active)
> > > >gcc13 @13.2.0_4+stdlib_flag (active)
> > > >gcc13-libcxx @13.2.0_4+clang16 (active)
> > > >gcc_select @0.1_10 (active)
> > > >libgcc @7.0_0 (active)
> > > >libgcc12 @12.3.0_4+stdlib_flag (active)
> > > >libgcc13 @13.2.0_4+stdlib_flag (active)
> > > >mpich-default @4.1.2_2+gcc13 (active)
> > > >
> > > > Still confused...
> > > >
> > > > Thanks,
> > > > Ken W.
> > > >
> > > > On Fri, Mar 1, 2024 at 6:03 PM Bernstein, Noam CIV USN NRL WASHINGTON
> > > > DC (USA)  > > > <https://lists.macports.org/mailman/listinfo/macports-users>> wrote:
> > > > >//>/Pretty sure that macports gcc installs gfortran by default, which 
> > > > >is
> > > > a f90 (and 95, and maybe f2003) compiler./
> > >

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

[Kenneth Wolcott]

I do have a GNAT Ada compiler located at:

/opt/gcc-13.2.0-aarch64

Does the existence of this confuse or mislead MacPorts?

Thanks,
Ken W.

On Fri, Mar 1, 2024 at 8:24 PM Kenneth Wolcott  wrote:
>
> Hi Joshua;
>
> port contents gcc13 | grep gfortran
>   /opt/local/bin/arm64-apple-darwin23-gfortran-mp-13
>   /opt/local/bin/gfortran-mp-13
>   /opt/local/lib/gcc13/libgfortran.5.dylib
>   /opt/local/lib/gcc13/libgfortran.a
>   /opt/local/lib/gcc13/libgfortran.dylib
>   /opt/local/lib/gcc13/libgfortran.spec
>   /opt/local/share/info/gfortran-mp-13.info
>   /opt/local/share/man/man1/gfortran-mp-13.1.gz
> ~:
>
> But "ls /usr/local/bin | grep -i fortran"
>
> Has no output. ??!!
>
> Thanks,
> Ken W.
>
> On Fri, Mar 1, 2024 at 7:19 PM Joshua Root  wrote:
> >
> > Are you sure of that? Check e.g. 'port contents gcc13 | grep gfortran'.
> >
> > - Josh
> >
> > Kenneth Wolcott wrote:
> >
> > > Hi Noam;
> > >
> > >I do not have gfortran, therefore I must not have gcc?
> > >
> > > Here is a filtered list of the ports that I have installed that pertain 
> > > to gcc:
> > >gcc12 @12.3.0_4+stdlib_flag (active)
> > >gcc12-libcxx @12.3.0_4+clang14 (active)
> > >gcc13 @13.2.0_4+stdlib_flag (active)
> > >gcc13-libcxx @13.2.0_4+clang16 (active)
> > >gcc_select @0.1_10 (active)
> > >libgcc @7.0_0 (active)
> > >libgcc12 @12.3.0_4+stdlib_flag (active)
> > >libgcc13 @13.2.0_4+stdlib_flag (active)
> > >mpich-default @4.1.2_2+gcc13 (active)
> > >
> > > Still confused...
> > >
> > > Thanks,
> > > Ken W.
> > >
> > > On Fri, Mar 1, 2024 at 6:03 PM Bernstein, Noam CIV USN NRL WASHINGTON
> > > DC (USA)  > > <https://lists.macports.org/mailman/listinfo/macports-users>> wrote:
> > > >//>/Pretty sure that macports gcc installs gfortran by default, which is
> > > a f90 (and 95, and maybe f2003) compiler./
> >

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

[Kenneth Wolcott]

Hi Joshua;

port contents gcc13 | grep gfortran
  /opt/local/bin/arm64-apple-darwin23-gfortran-mp-13
  /opt/local/bin/gfortran-mp-13
  /opt/local/lib/gcc13/libgfortran.5.dylib
  /opt/local/lib/gcc13/libgfortran.a
  /opt/local/lib/gcc13/libgfortran.dylib
  /opt/local/lib/gcc13/libgfortran.spec
  /opt/local/share/info/gfortran-mp-13.info
  /opt/local/share/man/man1/gfortran-mp-13.1.gz
~:

But "ls /usr/local/bin | grep -i fortran"

Has no output. ??!!

Thanks,
Ken W.

On Fri, Mar 1, 2024 at 7:19 PM Joshua Root  wrote:
>
> Are you sure of that? Check e.g. 'port contents gcc13 | grep gfortran'.
>
> - Josh
>
> Kenneth Wolcott wrote:
>
> > Hi Noam;
> >
> >I do not have gfortran, therefore I must not have gcc?
> >
> > Here is a filtered list of the ports that I have installed that pertain to 
> > gcc:
> >gcc12 @12.3.0_4+stdlib_flag (active)
> >gcc12-libcxx @12.3.0_4+clang14 (active)
> >gcc13 @13.2.0_4+stdlib_flag (active)
> >gcc13-libcxx @13.2.0_4+clang16 (active)
> >gcc_select @0.1_10 (active)
> >libgcc @7.0_0 (active)
> >libgcc12 @12.3.0_4+stdlib_flag (active)
> >libgcc13 @13.2.0_4+stdlib_flag (active)
> >mpich-default @4.1.2_2+gcc13 (active)
> >
> > Still confused...
> >
> > Thanks,
> > Ken W.
> >
> > On Fri, Mar 1, 2024 at 6:03 PM Bernstein, Noam CIV USN NRL WASHINGTON
> > DC (USA)  > <https://lists.macports.org/mailman/listinfo/macports-users>> wrote:
> > >//>/Pretty sure that macports gcc installs gfortran by default, which is
> > a f90 (and 95, and maybe f2003) compiler./
>

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

[Kenneth Wolcott]

Hi Noam;

  I do not have gfortran, therefore I must not have gcc?

Here is a filtered list of the ports that I have installed that pertain to gcc:
  gcc12 @12.3.0_4+stdlib_flag (active)
  gcc12-libcxx @12.3.0_4+clang14 (active)
  gcc13 @13.2.0_4+stdlib_flag (active)
  gcc13-libcxx @13.2.0_4+clang16 (active)
  gcc_select @0.1_10 (active)
  libgcc @7.0_0 (active)
  libgcc12 @12.3.0_4+stdlib_flag (active)
  libgcc13 @13.2.0_4+stdlib_flag (active)
  mpich-default @4.1.2_2+gcc13 (active)

Still confused...

Thanks,
Ken W.

On Fri, Mar 1, 2024 at 6:03 PM Bernstein, Noam CIV USN NRL WASHINGTON
DC (USA)  wrote:
>
> Pretty sure that macports gcc installs gfortran by default, which is a f90 
> (and 95, and maybe f2003) compiler.
>
>
>
>
>
>

is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

[Kenneth Wolcott]

Hi;

  I have lfortran and fort77 ports installed, but neither of those can
handle Fortran-90.

  I thought that having gcc installed would automatically give me a
gfortran, but apparently not.  Is this somehow available under clang?

  Is there a FOSS Fortran-90 compiler that I can install?

  The last time I tried to install gfortran directly from FSF, it
failed, I don't remember why.

  I'm looking at some Rosetta Code tasks for fun (!)
(https://rosettacode.org/wiki/Rosetta_Code)

Thanks,
Ken Wolcott

Re: MacPorts 2.9.1 has been released

[Kenneth Wolcott]

Nice job to all who contributed!

On Wed, Jan 31, 2024 at 7:17 PM Joshua Root  wrote:
>
> The MacPorts Project is pleased to announce the release of version
> 2.9.1. This is a bugfix release with small changes only. See the
> ChangeLog [1] for the list of changes.
>
> If you already have MacPorts installed, the preferred method for
> updating is to run:
>
>  sudo port selfupdate
>
> For new installs, there are also package installers available for macOS
> versions ranging from macOS 14 Sonoma all the way back to 10.4 at [2].
> The source is also available as tarballs compressed with gzip or bzip2,
> or from the git tag [3].
>
> Detached PGP signatures for the disk images, packages and source
> tarballs have been made with my key, which is available on the
> keyservers and my MacPorts wiki page [4], the fingerprint being:
>
> 0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58  0C02 01FF 673F B4AA E6CD
>
> Josh
> (on behalf of the MacPorts Port Managers)
>
> [1] 
> [2] 
> [3] 
> [4] 
>

How to wean myself away from Python 3.9? and then Python3.10?

[Kenneth Wolcott]

Hi;

How to wean myself away from Python 3.9? and then Python3.10?

There's so much that I don't understand about MacPorts.

Should I uninstall everything that depends on Python 3.9 and then
Python 3.9 and then re-install those apps that I uninstalled from the
first sequence?  How will that not put me back to where O started?

The same question applies to Perl.

Thanks,
Ken Wolcott

Re: Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

port installed | grep msgpack
  msgpack @4_0 (active)
  msgpack-c @4.0.0_0
  msgpack-c @6.0.0_0 (active)
  msgpack-cpp @4.1.1_0
  msgpack-cpp @6.0.0_0
  msgpack-cpp @6.1.0_0 (active)
  py310-msgpack @1.0.4_2
  py310-msgpack @1.0.5_0
  py310-msgpack @1.0.7_0 (active)
~: port installed | grep borgbackup
  borgbackup @1.2.3_0
  borgbackup @1.2.3_1
  borgbackup @1.2.4_0
  borgbackup @1.2.6_0 (active)

On Thu, Dec 28, 2023 at 10:42 PM Kenneth Wolcott
 wrote:
>
> You do not have a supported version of the msgpack python package
> installed. Terminating.
> This should never happen as specific, supported versions are required
> by our setup.py.
> Do not contact borgbackup support about this.
> terminating with error status, rc 2
>
> Thanks,
> Ken Wolcott

Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

You do not have a supported version of the msgpack python package
installed. Terminating.
This should never happen as specific, supported versions are required
by our setup.py.
Do not contact borgbackup support about this.
terminating with error status, rc 2

Thanks,
Ken Wolcott

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Hi Ken C;

  Thank you for the hint.  I have gcc13 for Ada installed and I think
that the gcc got picked up (it has C as well, not pure Ada, so that
Ada can link up with C).

  Sometimes I think it would be great to have three (or more!)
different Macs so that I can customize things without conflicts.  I
guess Docker is the only way to meaningfully do that (I don't have
enough money or space to have that many Mac machines!)

Thanks,
Ken W

Re: Idiomatic process for handling needed external language modules for which there is no port

[Kenneth Wolcott]

Thanks to all of your responses.  I'm just not sure what the facts
really are :-(

I'll just try to precisely follow all the instructions I see regarding
Perl and CPAN; perhaps these problems will iron themselves out over
time when I see the errors of my ways.

Ken W.

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Hi Ken C;

  I was able to install the Perl Primesieve module finally.  Now
working on the Raku Primesieve module install process.

Thanks,
Ken W.

On Sat, Dec 16, 2023 at 8:03 PM Kenneth Wolcott
 wrote:
>
> Hi Ken C;
>
>   I thought I had precisely followed the build instructions
> previously.  I must have built from the wrong directory and as a
> result the linkage error(s) occurred.. Seems to work fine with your
> instructions.
>
>   I feel really stupid :-(
>
>   Thanks...
>
> Ken W.
>
> port installed | grep cmake
>   cmake @3.23.5_0
>   cmake @3.24.3_0
>   cmake @3.24.4_0 (active)
>   cmake-bootstrap @3.9.6_0 (active)
>   tree-sitter-cmake @0.1.0_0 (active)
>
> git clone --depth=1 https://github.com/kimwalisch/primesieve
> Cloning into 'primesieve'...
> remote: Enumerating objects: 148, done.
> remote: Counting objects: 100% (148/148), done.
> remote: Compressing objects: 100% (139/139), done.
> remote: Total 148 (delta 16), reused 96 (delta 7), pack-reused 0
> Receiving objects: 100% (148/148), 165.77 KiB | 998.00 KiB/s, done.
> Resolving deltas: 100% (16/16), done.
> BS: cd primesieve
> primesieve: mkdir build
> primesieve: cd !$
> cd build
> build: cmake ..
> -- The CXX compiler identification is GNU 13.1.0
> -- Checking whether CXX compiler has -isysroot
> -- Checking whether CXX compiler has -isysroot - yes
> -- Checking whether CXX compiler supports OSX deployment target flag
> -- Checking whether CXX compiler supports OSX deployment target flag - yes
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /opt/gcc-13.1.0-aarch64/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Performing Test atomic64
> -- Performing Test atomic64 - Success
> -- Performing Test ftree_vectorize
> -- Performing Test ftree_vectorize - Success
> -- Performing Test fvect_cost_model
> -- Performing Test fvect_cost_model - Success
> -- Performing Test multiarch_popcnt_bmi
> -- Performing Test multiarch_popcnt_bmi - Failed
> -- Performing Test multiarch_avx512
> -- Performing Test multiarch_avx512 - Failed
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /Users/kwolcott/Downloads/BS/primesieve/build
> build: make
> [  2%] Building CXX object CMakeFiles/libprimesieve.dir/src/api-c.cpp.o
> [  4%] Building CXX object CMakeFiles/libprimesieve.dir/src/api.cpp.o
> [  6%] Building CXX object
> CMakeFiles/libprimesieve.dir/src/CountPrintPrimes.cpp.o
> [  8%] Building CXX object CMakeFiles/libprimesieve.dir/src/CpuInfo.cpp.o
> [ 10%] Building CXX object CMakeFiles/libprimesieve.dir/src/Erat.cpp.o
> [ 12%] Building CXX object CMakeFiles/libprimesieve.dir/src/EratSmall.cpp.o
> [ 14%] Building CXX object CMakeFiles/libprimesieve.dir/src/EratMedium.cpp.o
> [ 17%] Building CXX object CMakeFiles/libprimesieve.dir/src/EratBig.cpp.o
> [ 19%] Building CXX object CMakeFiles/libprimesieve.dir/src/iterator-c.cpp.o
> [ 21%] Building CXX object CMakeFiles/libprimesieve.dir/src/iterator.cpp.o
> [ 23%] Building CXX object 
> CMakeFiles/libprimesieve.dir/src/IteratorHelper.cpp.o
> [ 25%] Building CXX object CMakeFiles/libprimesieve.dir/src/LookupTables.cpp.o
> [ 27%] Building CXX object CMakeFiles/libprimesieve.dir/src/MemoryPool.cpp.o
> [ 29%] Building CXX object 
> CMakeFiles/libprimesieve.dir/src/PrimeGenerator.cpp.o
> [ 31%] Building CXX object CMakeFiles/libprimesieve.dir/src/nthPrime.cpp.o
> [ 34%] Building CXX object 
> CMakeFiles/libprimesieve.dir/src/ParallelSieve.cpp.o
> [ 36%] Building CXX object CMakeFiles/libprimesieve.dir/src/popcount.cpp.o
> [ 38%] Building CXX object CMakeFiles/libprimesieve.dir/src/PreSieve.cpp.o
> [ 40%] Building CXX object CMakeFiles/libprimesieve.dir/src/PrimeSieve.cpp.o
> [ 42%] Building CXX object 
> CMakeFiles/libprimesieve.dir/src/SievingPrimes.cpp.o
> [ 44%] Linking CXX shared library libprimesieve.dylib
> -macosx_version_min has been renamed to -macos_version_min
> ld: warning: ignoring duplicate libraries: '-lgcc'
> [ 44%] Built target libprimesieve
> [ 46%] Building CXX object CMakeFiles/libprimesieve-static.dir/src/api-c.cpp.o
> [ 48%] Building CXX object CMakeFiles/libprimesieve-static.dir/src/api.cpp.o
> [ 51%] Building CXX object
> CMakeFiles/libprimesieve-static.dir/src/CountPrintPrimes.cpp.o
> [ 53%] Building CXX object 
> CMakeFiles/libprimesieve-static.dir/src/CpuInfo.cpp.o
> [ 55%] Building CXX object CMakeFiles/libprimesieve-static.dir/src/Erat.cpp.o
> [ 57%] Building CXX object
> CMakeFiles/libprimesieve-static.dir/src/EratSmall.cpp.o
> [ 59%] Building CXX object
> CMakeFiles/libprimesieve-static.dir/src/EratMedium.cpp.

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

eFiles/libprimesieve-static.dir/src/ParallelSieve.cpp.o
[ 80%] Building CXX object
CMakeFiles/libprimesieve-static.dir/src/popcount.cpp.o
[ 82%] Building CXX object
CMakeFiles/libprimesieve-static.dir/src/PreSieve.cpp.o
[ 85%] Building CXX object
CMakeFiles/libprimesieve-static.dir/src/PrimeSieve.cpp.o
[ 87%] Building CXX object
CMakeFiles/libprimesieve-static.dir/src/SievingPrimes.cpp.o
[ 89%] Linking CXX static library libprimesieve.a
[ 89%] Built target libprimesieve-static
[ 91%] Building CXX object CMakeFiles/primesieve.dir/src/app/cmdoptions.cpp.o
[ 93%] Building CXX object CMakeFiles/primesieve.dir/src/app/help.cpp.o
[ 95%] Building CXX object CMakeFiles/primesieve.dir/src/app/main.cpp.o
[ 97%] Building CXX object CMakeFiles/primesieve.dir/src/app/test.cpp.o
[100%] Linking CXX executable primesieve
-macosx_version_min has been renamed to -macos_version_min
ld: warning: ignoring duplicate libraries: '-lgcc'
[100%] Built target primesieve

On Sat, Dec 16, 2023 at 7:55 PM Kenneth Wolcott
 wrote:
>
> Hi Ken C.;
>
>   Thanks, but I could not get it to compile on my machine (M1, Sonoma
> 14.2). I think I got a link error, don't recall right now.  Another
> time I got an assert failure at the link stage.
>
> Ken W.
>
> On Sat, Dec 16, 2023 at 7:37 PM Ken Cunningham
>  wrote:
> >
> > Someone can make a port for this, but here you are for a quickie, to show 
> > you how this is done:
> >
> >
> > % sudo port install cmake
> >
> >
> > % git clone --depth=1 https://github.com/kimwalisch/primesieve
> > % cd primesieve
> > % mkdir build
> > % cd build
> > % cmake ..
> > % make
> >
> > % ./primesieve 100 --count --print
> > 2
> > 3
> > 5
> > 7
> > 11
> > 13
> > 17
> > 19
> > 23
> > 29
> > 31
> > 37
> > 41
> > 43
> > 47
> > 53
> > 59
> > 61
> > 67
> > 71
> > 73
> > 79
> > 83
> > 89
> > 97
> > 25
> >

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Hi Ken C.;

  Thanks, but I could not get it to compile on my machine (M1, Sonoma
14.2). I think I got a link error, don't recall right now.  Another
time I got an assert failure at the link stage.

Ken W.

On Sat, Dec 16, 2023 at 7:37 PM Ken Cunningham
 wrote:
>
> Someone can make a port for this, but here you are for a quickie, to show you 
> how this is done:
>
>
> % sudo port install cmake
>
>
> % git clone --depth=1 https://github.com/kimwalisch/primesieve
> % cd primesieve
> % mkdir build
> % cd build
> % cmake ..
> % make
>
> % ./primesieve 100 --count --print
> 2
> 3
> 5
> 7
> 11
> 13
> 17
> 19
> 23
> 29
> 31
> 37
> 41
> 43
> 47
> 53
> 59
> 61
> 67
> 71
> 73
> 79
> 83
> 89
> 97
> 25
>

Idiomatic process for handling needed external language modules for which there is no port

[Kenneth Wolcott]

Idiomatic process for handling needed external language modules for
which there is no port

Hi;

  I'm trying to understand how to logically handle external modules
for a language under MacPorts.

TL;DR:

How do you do package management on MacPorts for languages which might
need modules which MacPorts doesn't have?

  This problem exists for many languages supported by MacPorts; ie:
Perl, Python, Raku, Julia, etc

  Scenario A:

1.  Install Perl from MacPorts.
2. Need Perl module XYZ.
3. Perl module XYZ does not exist on MaqcPorts.
4. Install (using CPAN, CPANm, or manually) the XYX module locating it
under the MacPorts port.
5. MacPorts complains about things installed under /opt/local that it
didn't put there (makes sense).

Scenario B:
1.  Install Perl from MacPorts.
2. Perl script I want to use requires a more recent version of Perl
than those found on MacPorts.
3. Install my own version of Perl (usually from source).
4. Need Perl module XYZ.
5. Install Perl module XYZ (trying to match it with my own install
location, but frequently screw this up).
6. End up with weird path issues, Perl and/or module(s) all confused.

Scenario C:
1.  Install Perl from MacPorts.
2. Install Perl from perlbrew.
3. Run into problems with #3-6 from Scenario B.

Scenario D:
1 Use a Docker container for Perl exclusively for these experiments
that I'm trying to use Perl for (various math learning, etc);
2. Install Perl from source
3. Install all needed external Perl modules myself on the Docker container.

Looks like I end up using Scenario D for Perl and Raku.  Now
considering this for Julia, Python, Rust, etc

So one of my problems is that I do not have a foolproof method
(understanding) of how to install modules  (Perl, Raku, etc) so that
the modules are not in conflict with multiple installations of the
main language.

Bottom-line question:

How do you do package management on MacPorts for languages which might
need modules which MacPorts doesn't have?

Thanks,
Ken Wolcott

New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

[Kenneth Wolcott]

Hi;

  This exists on homebrew, but doesn't on MacPorts.

  I don't use homebrew, I use MacPorts exclusively.

  I can't get this to compile (I've tried so many different ways to
hit this, I don't know what to list here for my failures).

  I can't get the Perl and Raku modules based on this package to work
without this.

  Could someone be so awesome as to create this port?

  Perhaps part of my problem is that I'm have an M1 chip and there's a
linking problem??

  I have tried using the Perl5 that comes with MacPorts for some
numeric things and it wants Perl 5.36 or newer, and some of the
MacPorts ports that I have require Perl 5.34, so I can't get the Perl
modules to install into 5.36.  So I tried to build my own Perl 5.38
and install modules there, which mostly works...

  Oh, I'm quite frustrated; hard to tell, no?

Thanks,
Ken Wolcott

New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

Re: moar (better than less) conflicts with moarVM (needed for Raku)

[Kenneth Wolcott]

Hi Bill;

  Thanks for the clarification.  I totally missed the space before the
"+". As a result, I thought that the port was called "moar+pager".
When I did a "port list | grep -v moar", I did not see that listed.
It looks like it successfully installed now.

  Again, thank you Austin!

Ken

On Tue, Dec 5, 2023 at 1:40 PM Bill Cole
 wrote:
>
> On 2023-12-05 at 15:07:56 UTC-0500 (Tue, 5 Dec 2023 12:07:56 -0800)
> Kenneth Wolcott 
> is rumored to have said:
>
> [...]
>
> > ~: sudo port -v -s install moar
> > --->  Computing dependencies for moar.
> > Error: Can't install moar because conflicting ports are active: MoarVM
> > Error: Follow https://guide.macports.org/#project.tickets if you
> > believe there is a bug.
> > Error: Processing of port moar failed
> >
> > On Tue, Dec 5, 2023 at 11:04 AM Austin Ziegler
> >  wrote:
> >>
> >> `sudo port install moar +pager` should work after an update.
>
> Those two command lines are not the same.
>
> The "+pager" invokes a variant that fixes the problem by modifying the
> name of the conflicting executable.
>
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Re: moar (better than less) conflicts with moarVM (needed for Raku)

[Kenneth Wolcott]

Hi Austin;

  That's great news to hear, but it still seems to be in conflict with
MoarVM even after a self-update.  Perhaps there is something else that
I need to do in addition to the self-update?

Thanks,
Ken

date; sudo port -v selfupdate
Tue Dec  5 12:05:04 PST 2023
Password:
--->  Updating MacPorts base sources using rsync

Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.


receiving file list ... done
./

sent 66 bytes  received 98 bytes  46.86 bytes/sec
total size is 114272768  speedup is 696785.17
MacPorts base version 2.8.1 installed,
MacPorts base version 2.8.1 downloaded.
--->  Updating the ports tree
Synchronizing local ports tree from
rsync://rsync.macports.org/macports/release/tarballs/ports.tar

Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.


receiving file list ... done
./

sent 68 bytes  received 99 bytes  66.80 bytes/sec
total size is 123787264  speedup is 741241.10
Creating port index in
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports

Total number of ports parsed: 0
Ports successfully parsed: 0
Ports failed: 0
Up-to-date ports skipped: 37585

--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
~: port list | grep -i moar
MoarVM @2023.06lang/MoarVM
moar   @1.18.5 textproc/moar
~: port installed | grep -i moar
  moar @1.16.1_0
  moar @1.18.1_0
  MoarVM @2022.07_1
  MoarVM @2022.12_0
  MoarVM @2023.02_0
  MoarVM @2023.04_0
  MoarVM @2023.06_0
  MoarVM @2023.06_1 (active)
~: sudo port -v -s install moar
--->  Computing dependencies for moar.
Error: Can't install moar because conflicting ports are active: MoarVM
Error: Follow https://guide.macports.org/#project.tickets if you
believe there is a bug.
Error: Processing of port moar failed

On Tue, Dec 5, 2023 at 11:04 AM Austin Ziegler  wrote:
>
> `sudo port install moar +pager` should work after an update.
>
> On Thu, Nov 30, 2023 at 12:23 AM Kenneth Wolcott  
> wrote:
>>
>> AWESOME!
>>
>> On Wed, Nov 29, 2023 at 9:13 PM Austin Ziegler  wrote:
>> >
>> > Hi, Kenneth.
>> >
>> > I finally got around to figuring out how to resolve this[1] and have 
>> > opened a
>> > new PR[2] which, if accepted, will allow you to install moar with the 
>> > +pager
>> > variant, bypassing the mutual conflict on both sides (so you can install
>> > moar +pager before MoarVM or vice-versa). moar will be called moar-pager
>> > with the +pager variant, so any configuration you do to $PAGER will need
>> > to be updated to use moar-pager instead of moar.
>> >
>> > riff and ugrep, if used, will be patched to recognize moar-pager in 
>> > addition
>> > to moar as a pager.
>> >
>> > -a
>> >
>> > [1] https://trac.macports.org/ticket/6849
>> > [2] https://github.com/macports/macports-ports/pull/21604
>> >
>> > On Tue, Oct 17, 2023 at 9:16 PM Kenneth Wolcott  
>> > wrote:
>> >>
>> >> Hi;
>> >>
>> >>   I noticed today that when trying to build moar port from source that
>> >> port stops immediately by stating the previously-known conflict with
>> >> MoarVM rather than building it first and then complaining when the
>> >> installation occurs and the conflict is readily apparent.  This is an
>> >> improvement; thanks to those who improved this.  It would be great to
>> >> have both co-exist peacefully, however.
>> >>
>> >> Thanks,
>> >> Ken
>> >>
>> >> On Mon, Oct 16, 2023 at 6:53 PM Austin Ziegler  
>> >> wrote:
>> >> >
>> >> > This is a known issue with no useful response from the upstream 
>> >> > maintainer: https://github.com/walles/moar/issues/143
>> >> >
>> >> > IMO, MacPorts should either make the choice to change the `moar` pager 
>> >> > binary to `moar-pager` or set up a conflicting package rule.
>> >> >
>> >> > As I was looking for examples of this, I noticed that the moreutils 
>> >> > port excludes its version of parallel, which is easier to use in simple 
>> >> > cases than GNU parallel — so that's somewhat disappointing. Maybe we 
>> >> > can bring that back as a v

Re: Quartz no longer launching when an X application is invoked

[Kenneth Wolcott]

Thank you all for your efforts.

I'm still not getting it.

Thanks,
Ken

On Fri, Dec 1, 2023 at 1:43 AM Christopher Jones
 wrote:
>
>
>
> On 1 Dec 2023, at 6:52 am, Kenneth Wolcott  wrote:
>
> Hi;
>
>  So what is the proper way for X to be started?
>
>
>
> If properly configured the X11 server will automatically start on demand. You 
> really should never need to manually start it.
>
>
>  Do I need to manually create a launch entry like I have for the
> emacs server?  If so, what is the invocation? What is being invoked?
> xorg-server?
>
>  Now that the DISPLAY is null, invoking xpdf fails even after an open
> -a /Applications/MacPorts/X11.app, complaining about the DISPLAY
> variable setting
>
>
> Having DISPLAY null is as bad as setting it to :0.0
>
> It should look something like what I posted before
>
> $ echo $DISPLAY
> /private/tmp/com.apple.launchd.TwDg8TRtvI/org.macosforge.xquartz:0
>
> This is the launchd socket, the magic if you like, that triggers it to be 
> started on demand.
>
> Please try as I posted in my first mail completeing uninstalling org-server, 
> then re-install it. Then log out and back in again (this is important) and 
> then see. If it is still null then you have something else setting that and 
> you need to figure out what.
>
> Chris
>
>
> Thanks,
> Ken
>
> On Thu, Nov 30, 2023 at 10:47 PM Kenneth Wolcott
>  wrote:
>
>
> Hi Ryan;
>
>  It was defined in ~/.zprofile and created by MacPorts in 2021 :-)  I
> commented it out. I'll source the .zprofile and see what happens.
>
> Thanks,
> Ken
>
> On Thu, Nov 30, 2023 at 10:23 PM Ryan Schmidt  wrote:
>
>
> On Nov 30, 2023, at 16:01, Kenneth Wolcott wrote:
>
>
> 3. My DISPLAY environment variable is set to ":0";
> I do not know where this variable is not being set properly or is
> being overridden.
>
>
> You need to figure out where DISPLAY=:0 is being set, and remove the code 
> that does so. It's probably in your shell startup file. Depending on which 
> shell you use, there are many possible names for startup files in your home 
> directory: .zshrc, .zprofile, .bashrc, .bash_profile, etc.
>
> Setting DISPLAY=:0 was correct in Mac OS X 10.4 and earlier but it has not 
> been correct since Mac OS X 10.5.
>
>

Re: Quartz no longer launching when an X application is invoked

[Kenneth Wolcott]

Hi;

  So what is the proper way for X to be started?

  Do I need to manually create a launch entry like I have for the
emacs server?  If so, what is the invocation? What is being invoked?
xorg-server?

  Now that the DISPLAY is null, invoking xpdf fails even after an open
-a /Applications/MacPorts/X11.app, complaining about the DISPLAY
variable setting.

Thanks,
Ken

On Thu, Nov 30, 2023 at 10:47 PM Kenneth Wolcott
 wrote:
>
> Hi Ryan;
>
>   It was defined in ~/.zprofile and created by MacPorts in 2021 :-)  I
> commented it out. I'll source the .zprofile and see what happens.
>
> Thanks,
> Ken
>
> On Thu, Nov 30, 2023 at 10:23 PM Ryan Schmidt  wrote:
> >
> > On Nov 30, 2023, at 16:01, Kenneth Wolcott wrote:
> > >
> > > 3. My DISPLAY environment variable is set to ":0";
> > > I do not know where this variable is not being set properly or is
> > > being overridden.
> >
> > You need to figure out where DISPLAY=:0 is being set, and remove the code 
> > that does so. It's probably in your shell startup file. Depending on which 
> > shell you use, there are many possible names for startup files in your home 
> > directory: .zshrc, .zprofile, .bashrc, .bash_profile, etc.
> >
> > Setting DISPLAY=:0 was correct in Mac OS X 10.4 and earlier but it has not 
> > been correct since Mac OS X 10.5.

Re: Quartz no longer launching when an X application is invoked

[Kenneth Wolcott]

Hi Ryan;

  It was defined in ~/.zprofile and created by MacPorts in 2021 :-)  I
commented it out. I'll source the .zprofile and see what happens.

Thanks,
Ken

On Thu, Nov 30, 2023 at 10:23 PM Ryan Schmidt  wrote:
>
> On Nov 30, 2023, at 16:01, Kenneth Wolcott wrote:
> >
> > 3. My DISPLAY environment variable is set to ":0";
> > I do not know where this variable is not being set properly or is
> > being overridden.
>
> You need to figure out where DISPLAY=:0 is being set, and remove the code 
> that does so. It's probably in your shell startup file. Depending on which 
> shell you use, there are many possible names for startup files in your home 
> directory: .zshrc, .zprofile, .bashrc, .bash_profile, etc.
>
> Setting DISPLAY=:0 was correct in Mac OS X 10.4 and earlier but it has not 
> been correct since Mac OS X 10.5.

Re: Quartz no longer launching when an X application is invoked

[Kenneth Wolcott]

Hi Chris;

  Thank you for your response.

  1. I manually use /Applications/MacPorts/X11.app (/usr/bin/open -a
/Applications/MacPorts/X11.app when inside a script) when invoking an
app (such as /opt/local/bin/xtern) which then fails:

~: which xterm
/opt/local/bin/xterm
~: xterm &
[1] 6134
[1]  + exit 1 xterm
~: xterm: Xt error: Can't open display: :0

~: open -a /Applications/MacPorts/X11.app
~: xterm &
[1] 6423
~: echo $DISPLAY
:0

2. I uninstalled and re-installed xorg-server per your instructions.
This did not solve the problem.

3. My DISPLAY environment variable is set to ":0";
I do not know where this variable is not being set properly or is
being overridden.

I do have an emacs server launch:
~/Library/LaunchAgents/gnu.emacs.daemon.plist

Should I create something similar for X? If so, what app needs to do
the work? org-server?

Thanks,
Ken Wolcott

On Thu, Nov 30, 2023 at 2:55 AM Chris Jones  wrote:
>
> Hi,
>
> 'Quartz' has nothing to do with X11, its the primary compositor used by
> macOS itself to render graphics.
>
> I assume you are actually taking about the X11 server, which in MacPorts
> is provided by the 'xorg-server' port and historically was provided by
> the 'XQuartz' package.
>
> Some basic questions.
>
> 1. What installation of the X11 server are you using ? the MacPorts
> provided one or something else ?
>
> 2. Regardless of your answer to 1., try (re)installing the MacPorts
> provided one
>
>   > sudo port uninstall xorg-server
>   > sudo port install xorg-server
>
> Then log out and back in again. This step is important as if you skip it
> things do not work correctly.
>
> 3. Finally, in order for the automatic starting of the X11 server on
> demand to work, you need your DISPLAY variable set correctly. It should
> look something like
>
> $ echo $DISPLAY
> /private/tmp/com.apple.launchd.TwDg8TRtvI/org.macosforge.xquartz:0
>
> i.e. it needs to refer to a launchd socket. If you see something else
> instead you like are overriding this somewhere and you need to find and
> remove this.
>
> Chris
>
> On 30/11/2023 5:30 am, Kenneth Wolcott wrote:
> > Hi;
> >
> > Quartz no longer launching when an X application is invoked
> >
> > The first time I had installed some ports that were dependent on
> > Quartz I had difficulty getting them to start because Quartz was not
> > running.
> >
> > The first solution was to manually invoke Quartz, which worked ok.
> >
> > I then was able to get Quartz to start via Launch when an X
> > application was invoked.
> >
> > Recently (?) it stopped working and I'm not sure why.
> >
> > All research I've done so far has been fruitless, I'm just not asking
> > the right questions...
> >
> > I'm back to manually starting Quartz.
> >
> > Please show me how to diagnose the problem and also to solve it.
> >
> > Thanks,
> > Ken Wolcott

Quartz no longer launching when an X application is invoked

[Kenneth Wolcott]

Hi;

Quartz no longer launching when an X application is invoked

The first time I had installed some ports that were dependent on
Quartz I had difficulty getting them to start because Quartz was not
running.

The first solution was to manually invoke Quartz, which worked ok.

I then was able to get Quartz to start via Launch when an X
application was invoked.

Recently (?) it stopped working and I'm not sure why.

All research I've done so far has been fruitless, I'm just not asking
the right questions...

I'm back to manually starting Quartz.

Please show me how to diagnose the problem and also to solve it.

Thanks,
Ken Wolcott

Re: moar (better than less) conflicts with moarVM (needed for Raku)

[Kenneth Wolcott]

AWESOME!

On Wed, Nov 29, 2023 at 9:13 PM Austin Ziegler  wrote:
>
> Hi, Kenneth.
>
> I finally got around to figuring out how to resolve this[1] and have opened a
> new PR[2] which, if accepted, will allow you to install moar with the +pager
> variant, bypassing the mutual conflict on both sides (so you can install
> moar +pager before MoarVM or vice-versa). moar will be called moar-pager
> with the +pager variant, so any configuration you do to $PAGER will need
> to be updated to use moar-pager instead of moar.
>
> riff and ugrep, if used, will be patched to recognize moar-pager in addition
> to moar as a pager.
>
> -a
>
> [1] https://trac.macports.org/ticket/6849
> [2] https://github.com/macports/macports-ports/pull/21604
>
> On Tue, Oct 17, 2023 at 9:16 PM Kenneth Wolcott  
> wrote:
>>
>> Hi;
>>
>>   I noticed today that when trying to build moar port from source that
>> port stops immediately by stating the previously-known conflict with
>> MoarVM rather than building it first and then complaining when the
>> installation occurs and the conflict is readily apparent.  This is an
>> improvement; thanks to those who improved this.  It would be great to
>> have both co-exist peacefully, however.
>>
>> Thanks,
>> Ken
>>
>> On Mon, Oct 16, 2023 at 6:53 PM Austin Ziegler  wrote:
>> >
>> > This is a known issue with no useful response from the upstream 
>> > maintainer: https://github.com/walles/moar/issues/143
>> >
>> > IMO, MacPorts should either make the choice to change the `moar` pager 
>> > binary to `moar-pager` or set up a conflicting package rule.
>> >
>> > As I was looking for examples of this, I noticed that the moreutils port 
>> > excludes its version of parallel, which is easier to use in simple cases 
>> > than GNU parallel — so that's somewhat disappointing. Maybe we can bring 
>> > that back as a variant (moreutils+parallel) or a separate port 
>> > (moreutils-parallel).
>> >
>> > -a
>> >
>> > On Mon, Oct 16, 2023 at 8:21 PM Kenneth Wolcott  
>> > wrote:
>> >>
>> >> Hi;
>> >>
>> >> Since I have already installed raku I cannot install moar because moar
>> >> conflicts with moarvm required by Raku.
>> >>
>> >> Looks like "moar" (which is better than "less") needs to be renamed
>> >> somehow or internally there is a conflict. Trimmed error output is
>> >> enclosed below.
>> >>
>> >> Thanks,
>> >> Ken Wolcott
>> >>
>> >> .
>> >> Error: Failed to activate moar: Image error: /opt/local/bin/moar is
>> >> being used by the active MoarVM port.  Please deactivate this port
>> >> first, or use 'port -f activate moar' to force the activation.
>> >> while executing
>> >> "throw registry::image-error $msg"
>> >> ("foreach" body line 47)
>> >> invoked from within
>> >> "foreach file $imagefiles {
>> >> set srcfile "${extracted_dir}${file}"
>> >>
>> >> # To be able to install links, we test if we can lst..."
>> >> invoked from within
>> >> "registry::write {
>> >> foreach file $imagefiles {
>> >> set srcfile "${extracted_dir}${file}"
>> >>
>> >> # To be able to instal..."
>> >> Error: See 
>> >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_moar/moar/main.log
>> >> for details.
>> >
>> >
>> >
>> > --
>> > Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
>> > http://www.halostatue.ca/ • http://twitter.com/halostatue
>
>
>
> --
> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
> http://www.halostatue.ca/ • http://twitter.com/halostatue

Re: zef, the package manager for Rakudo, needs to be installed as part of the port

[Kenneth Wolcott]

**AWESOME**

On Fri, Nov 24, 2023 at 1:00 PM raf via macports-users
 wrote:
>
> On Fri, Nov 24, 2023 at 09:11:52AM -0800, Kenneth Wolcott 
>  wrote:
>
> > Hi raf;
> >
> >   Thanks for your reply.  Perhaps a note could be placed in the rakudo
> > port stating that zef can be obtained separately and the instructions
> > for installing it? Then others, who are new to Rakudo via MacPorts
> > like I was (even those who are new to rakudo in general), will be able
> > to get going quickly with rakudo.
> >
> > https://github.com/ugexe/zef/blob/main/README.md
> >
> > Thanks,
> > Ken
>
> Thanks. There's been a comment on that issue exlaining how it can
> be installed to a custom location. I'll see if I can make a Portfile
> for zef. Then the rakudo Portfile could recommend it in a note.
>
> cheers,
> raf
>

Re: zef, the package manager for Rakudo, needs to be installed as part of the port

[Kenneth Wolcott]

Hi raf;

  Thanks for your reply.  Perhaps a note could be placed in the rakudo
port stating that zef can be obtained separately and the instructions
for installing it? Then others, who are new to Rakudo via MacPorts
like I was (even those who are new to rakudo in general), will be able
to get going quickly with rakudo.

https://github.com/ugexe/zef/blob/main/README.md

Thanks,
Ken

On Fri, Nov 24, 2023 at 4:55 AM raf via macports-users
 wrote:
>
> On Thu, Nov 23, 2023 at 08:20:24PM -0800, Kenneth Wolcott 
>  wrote:
>
> > Hi;
> >
> > zef, the package manager for Rakudo, needs to be installed as part of the 
> > port
> >
> > Zef, the Rakudo package manager, really needs to be part of the Rakudo
> > port.  Just like Ruby needs the Gem, Nim needs Nimble, Perl needs
> > CPAN.
> >
> > It's not hard to build Zef manually, but I think it should be
> > automatically installed as a dependency of Rakudo.
> >
> > Thanks,
> > Ken Wolcott
>
> I'd be happy if I could install zef at all via macports.
> It doesn't have to be part of raku's portfile. Debian
> has separate packages for them.
>
> This issue indicates that a Portfile *for* zef is planned:
>
>   https://github.com/ugexe/zef/issues/516
>
> But it looks like it's actually trying to use zef to create
> a package for a raku module (unless I've misunderstood the log
> output there - I probably have), but zef doesn't work like that.
> And zef uses itself to install itself, so it looks like it isn't
> suitable for packaging systems.
>
> There might not be interest in changing zef for use with
> packaging systems. The questions in that issue were asked
> six months ago with no response. It might need a patch
> to hack the raku module path so that zef is tricked into
> doing what's needed.
>
> cheers,
> raf
>

zef, the package manager for Rakudo, needs to be installed as part of the port

[Kenneth Wolcott]

Hi;

zef, the package manager for Rakudo, needs to be installed as part of the port

Zef, the Rakudo package manager, really needs to be part of the Rakudo
port.  Just like Ruby needs the Gem, Nim needs Nimble, Perl needs
CPAN.

It's not hard to build Zef manually, but I think it should be
automatically installed as a dependency of Rakudo.

Thanks,
Ken Wolcott

Request: Please add the Perl Module "theory" as a port

[Kenneth Wolcott]

Request: Please add the Perl Module "theory" as a port

Thanks,
Ken Wolcott

Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)

[Kenneth Wolcott]

Thanks!  It's better now.

On Sat, Nov 4, 2023 at 4:53 PM Ken Cunningham
 wrote:
>
>
>
> On Nov 4, 2023, at 4:51 PM, Ken Cunningham  
> wrote:
>
> So to clean that up:
>
> sudo port -f uninstall perl5 perl5.36
>
> and then:
>
> sudo port -f install perl5
>
>
> That last line should have been:
>
> sudo port -v install perl5
>
> K

perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)

[Kenneth Wolcott]

Hi Ryan;

  I am indeed confused about these Perl variants.

port installed | grep perl5
  ack @3.7.0_0+perl5_34 (active)
  docbook2X @0.8.8_11+perl5_34 (active)
  git @2.42.1_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34 (active)
  icoutils @0.32.3_1+perl5_34 (active)
  net-snmp @5.9.4_0+perl5_34+ssl (active)
  ossp-uuid @1.6.2_13+perl5_34 (active)
  perl5 @5.34.1_0+perl5_36 (active)
  perl5.34 @5.34.1_0 (active)
  perl5.36 @5.36.0_0
  perl5.36 @5.36.1_0 (active)
  xmltoman @0.4_1+perl5_34 (active)

Is there a way to simplify this?  Looks all tangled up...

Thanks,
Ken Wolcott

Re: FYI: The meld port depends on the p5.36-xml-parser port, which does not exist

[Kenneth Wolcott]

HI Joshua;

  Thank you for your reply.

  I created "#68635: meld port depends on a nonexistent p5.36-xml-parser port".

  I hope this helps.

Ken Wolcott

On Sat, Nov 4, 2023 at 11:12 AM Joshua Root  wrote:
>
> > FYI: The meld port depends on the p5.36-xml-parser port, which does not 
> > exist
> >
> > sudo port -v -s install meld
> > --->  Computing dependencies for meld
> > Error: Dependency 'p5.36-xml-parser' not found.
> > Error: Followhttps://guide.macports.org/#project.tickets  if you
> > believe there is a bug.
> > Error: Processing of port meld failed
>
> Meld itself does not have this dependency:
>
> % port deps meld
> Full Name: meld @3.21.0_2+x11
> Extract Dependencies: xz
> Build Dependencies:   intltool, itstool, libxml2, py311-distro, makeicns,
>librsvg
> Library Dependencies: desktop-file-utils, glib2, gtk3, gtksourceview4,
>py311-cairo, py311-gobject3, shared-mime-info,
> python311
> Runtime Dependencies: adwaita-icon-theme, gsettings-desktop-schemas, yelp
>
> So it must be one of its dependencies. But on my machine there is no
> such dependency:
>
> % port rdeps meld | grep -F p5.36-xml-parser
> %
>
> So it must be something that is changing dynamically, perhaps based on
> variants.
>
> % port echo depends:xml-parser and rdepof:meld
> intltool
> pulseaudio
>
> Looking at the portfiles for these two, intltool sets a fixed
> perl5.major, but pulseaudio does not. The perl5 portgroup has something
> of a misfeature where it sets the default perl to use based on the
> currently active variant of the perl5 port. So I guess you have
> perl5+perl5_36 installed.
>
> Please file a ticket. The pulseaudio port may not even need the
> p5-xml-parser dependency (many ports that use intltool once added this
> as a poor workaround for an old bug). But if it does, or if it records
> the path to perl at build time and then uses it at runtime, it needs to
> set a fixed perl5.major.
>
> - Josh
>

FYI: The meld port depends on the p5.36-xml-parser port, which does not exist

[Kenneth Wolcott]

Hi;

FYI: The meld port depends on the p5.36-xml-parser port, which does not exist

sudo port -v -s install meld
--->  Computing dependencies for meld
Error: Dependency 'p5.36-xml-parser' not found.
Error: Follow https://guide.macports.org/#project.tickets if you
believe there is a bug.
Error: Processing of port meld failed

Ken Wolcott

Re: moar (better than less) conflicts with moarVM (needed for Raku)

[Kenneth Wolcott]

Hi;

  I noticed today that when trying to build moar port from source that
port stops immediately by stating the previously-known conflict with
MoarVM rather than building it first and then complaining when the
installation occurs and the conflict is readily apparent.  This is an
improvement; thanks to those who improved this.  It would be great to
have both co-exist peacefully, however.

Thanks,
Ken

On Mon, Oct 16, 2023 at 6:53 PM Austin Ziegler  wrote:
>
> This is a known issue with no useful response from the upstream maintainer: 
> https://github.com/walles/moar/issues/143
>
> IMO, MacPorts should either make the choice to change the `moar` pager binary 
> to `moar-pager` or set up a conflicting package rule.
>
> As I was looking for examples of this, I noticed that the moreutils port 
> excludes its version of parallel, which is easier to use in simple cases than 
> GNU parallel — so that's somewhat disappointing. Maybe we can bring that back 
> as a variant (moreutils+parallel) or a separate port (moreutils-parallel).
>
> -a
>
> On Mon, Oct 16, 2023 at 8:21 PM Kenneth Wolcott  
> wrote:
>>
>> Hi;
>>
>> Since I have already installed raku I cannot install moar because moar
>> conflicts with moarvm required by Raku.
>>
>> Looks like "moar" (which is better than "less") needs to be renamed
>> somehow or internally there is a conflict. Trimmed error output is
>> enclosed below.
>>
>> Thanks,
>> Ken Wolcott
>>
>> .
>> Error: Failed to activate moar: Image error: /opt/local/bin/moar is
>> being used by the active MoarVM port.  Please deactivate this port
>> first, or use 'port -f activate moar' to force the activation.
>> while executing
>> "throw registry::image-error $msg"
>> ("foreach" body line 47)
>> invoked from within
>> "foreach file $imagefiles {
>> set srcfile "${extracted_dir}${file}"
>>
>> # To be able to install links, we test if we can lst..."
>> invoked from within
>> "registry::write {
>> foreach file $imagefiles {
>> set srcfile "${extracted_dir}${file}"
>>
>> # To be able to instal..."
>> Error: See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_moar/moar/main.log
>> for details.
>
>
>
> --
> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
> http://www.halostatue.ca/ • http://twitter.com/halostatue

moar (better than less) conflicts with moarVM (needed for Raku)

[Kenneth Wolcott]

Hi;

Since I have already installed raku I cannot install moar because moar
conflicts with moarvm required by Raku.

Looks like "moar" (which is better than "less") needs to be renamed
somehow or internally there is a conflict. Trimmed error output is
enclosed below.

Thanks,
Ken Wolcott

.
Error: Failed to activate moar: Image error: /opt/local/bin/moar is
being used by the active MoarVM port.  Please deactivate this port
first, or use 'port -f activate moar' to force the activation.
while executing
"throw registry::image-error $msg"
("foreach" body line 47)
invoked from within
"foreach file $imagefiles {
set srcfile "${extracted_dir}${file}"

# To be able to install links, we test if we can lst..."
invoked from within
"registry::write {
foreach file $imagefiles {
set srcfile "${extracted_dir}${file}"

# To be able to instal..."
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_moar/moar/main.log
for details.

mupdf-gl port warnings shown when using mupdf-gl to display a pdf file

[Kenneth Wolcott]

Hi;

  I recently installed the mupdf port.  The pdf output looks great,
but a nit: the following warnings are generated when using mupdf-gl to
display a pdf file.

warning: This version of MuPDF has been built WITHOUT clipboard or
unicode input support!
warning: Please file a complaint with your friendly local distribution manager.

Thanks,
Ken Wolcott

BaCon: new port requested: BaCon - BASIC to C converter

[Kenneth Wolcott]

Hi;

  I think that this would be nice to have.

BaCon - BASIC to C converter

http://basic-converter.org/

Can somebody add this to MacPorts as a new port?

Thanks,
Ken Wolcott

Re: how do I fix this?

[Kenneth Wolcott]

Thank you for clearing up the mystery!

On Fri, Sep 29, 2023 at 4:48 PM  wrote:
>
> On 9/28/23 at 10:49 PM, Kenneth Wolcott wrote:
>
> > sudo port diagnose
> > Warning: No Xcode version info was found for your OS version.
>
>
> The error was emitted by diagnose.tcl [1] because there was no information in 
> xcode_versions.ini regarding what Xcode versions are supported for macOS 14 
> Sonoma. This has since been fixed by [2].
>
> [1] 
> https://github.com/macports/macports-base/blob/master/src/macports1.0/diagnose.tcl#L593
> [2] https://github.com/macports/macports-ports/commit/ffdef818ba28
>

Re: how do I fix this?

[Kenneth Wolcott]

I did another port self-update.

I installed the mpg123 port, which was the only result from port outdated.

I then did another port diagnose and there is no warning now about no
xCode version info found...weird

Thanks,
Ken

On Fri, Sep 29, 2023 at 1:31 PM Kenneth Wolcott
 wrote:
>
> Hi Chris;
>
>   I removed xCode.
>
>   I installed xCode.
>
> xcode-select --install
> xcode-select: note: Command line tools are already installed. Use
> "Software Update" in System Settings or the softwareupdate command
> line interface to install updates
>
> sudo port diagnose
> Warning: No Xcode version info was found for your OS version.
>
> xcode-select -p
> /Applications/Xcode.app/Contents/Developer
>
> xcode-select -v
> xcode-select version 2399.
>
> Is there a bug in the port diagnose command? Or is there an
> installation fault with xCode?
>
> I've attached a screenshot of the "About xCode".
>
> Thanks,
> Ken
>
> On Fri, Sep 29, 2023 at 9:18 AM Kenneth Wolcott
>  wrote:
> >
> > HI Chris;
> >
> >   Thank you.
> >
> >   I did reinstall Xcode...
> >
> >   same situation.
> >
> >   I just upgraded to Sonoma.  I installed the new version of Xcode and
> > tools (at least I thought I did). I then installed the new version of
> > MacPorts.  I then tried to upgrade all my ports.  That took a long
> > time with many failures and many restarts.  Then I tried the port
> > diagnose to see how things are that this is the result.
> >
> > Ken
> >
> > On Fri, Sep 29, 2023 at 5:40 AM Chris Jones  
> > wrote:
> > >
> > >
> > >
> > > > On 29 Sep 2023, at 4:49 am, Kenneth Wolcott  
> > > > wrote:
> > > >
> > > > sudo port diagnose
> > > > Warning: No Xcode version info was found for your OS version.
> > >
> > > Try reinstalling Xcode….
> > >
> > > >
> > > > Thanks,
> > > > Ken Wolcott

Re: how do I fix this?

[Kenneth Wolcott]

Hi Chris;

  I removed xCode.

  I installed xCode.

xcode-select --install
xcode-select: note: Command line tools are already installed. Use
"Software Update" in System Settings or the softwareupdate command
line interface to install updates

sudo port diagnose
Warning: No Xcode version info was found for your OS version.

xcode-select -p
/Applications/Xcode.app/Contents/Developer

xcode-select -v
xcode-select version 2399.

Is there a bug in the port diagnose command? Or is there an
installation fault with xCode?

I've attached a screenshot of the "About xCode".

Thanks,
Ken

On Fri, Sep 29, 2023 at 9:18 AM Kenneth Wolcott
 wrote:
>
> HI Chris;
>
>   Thank you.
>
>   I did reinstall Xcode...
>
>   same situation.
>
>   I just upgraded to Sonoma.  I installed the new version of Xcode and
> tools (at least I thought I did). I then installed the new version of
> MacPorts.  I then tried to upgrade all my ports.  That took a long
> time with many failures and many restarts.  Then I tried the port
> diagnose to see how things are that this is the result.
>
> Ken
>
> On Fri, Sep 29, 2023 at 5:40 AM Chris Jones  wrote:
> >
> >
> >
> > > On 29 Sep 2023, at 4:49 am, Kenneth Wolcott  
> > > wrote:
> > >
> > > sudo port diagnose
> > > Warning: No Xcode version info was found for your OS version.
> >
> > Try reinstalling Xcode….
> >
> > >
> > > Thanks,
> > > Ken Wolcott

Re: how do I fix this?

[Kenneth Wolcott]

HI Chris;

  Thank you.

  I did reinstall Xcode...

  same situation.

  I just upgraded to Sonoma.  I installed the new version of Xcode and
tools (at least I thought I did). I then installed the new version of
MacPorts.  I then tried to upgrade all my ports.  That took a long
time with many failures and many restarts.  Then I tried the port
diagnose to see how things are that this is the result.

Ken

On Fri, Sep 29, 2023 at 5:40 AM Chris Jones  wrote:
>
>
>
> > On 29 Sep 2023, at 4:49 am, Kenneth Wolcott  
> > wrote:
> >
> > sudo port diagnose
> > Warning: No Xcode version info was found for your OS version.
>
> Try reinstalling Xcode….
>
> >
> > Thanks,
> > Ken Wolcott

how do I fix this?

[Kenneth Wolcott]

sudo port diagnose
Warning: No Xcode version info was found for your OS version.

Thanks,
Ken Wolcott

Re: perl --version is not at perl5.36 but at perl5.34 yet both are listed as active

[Kenneth Wolcott]

Hi Pieter;

> After sudo port install perl5 +perl5_36
> I get:
> ~ $ perl --version
>
> This is perl 5, version 36, subversion 1 (v5.36.1) built for 
> darwin-thread-multi-2level

This worked absolutely fine!  So, something silently failed the last
time that Perl was updated/upgraded...

Thanks,
Ken

Re: perl --version is not at perl5.36 but at perl5.34 yet both are listed as active

[Kenneth Wolcott]

HI Bill;

  Thanks for your reply.

  I'll point to /opt/local/bin/perl5.36 in my scripts.

Thanks,
Ken

perl --version is not at perl5.36 but at perl5.34 yet both are listed as active

[Kenneth Wolcott]

Hi;

  I'm confused about what Perl I have installed vi MacPorts and what
is active and what I can use.

port installed | grep perl5
  ack @3.6.0_0+perl5_34
  ack @3.7.0_0+perl5_34 (active)
  docbook2X @0.8.8_11+perl5_34 (active)
  git @2.39.1_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34
  git @2.39.2_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34
  git @2.40.0_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34
  git @2.40.1_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34
  git @2.41.0_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34 (active)
  icoutils @0.32.3_1+perl5_34 (active)
  net-snmp @5.9.1_1+perl5_34+ssl (active)
  ossp-uuid @1.6.2_13+perl5_34+universal
  ossp-uuid @1.6.2_13+perl5_34 (active)
  perl5 @5.34.1_0+perl5_34 (active)
  perl5.34 @5.34.1_0 (active)
  perl5.36 @5.36.0_0
  perl5.36 @5.36.1_0 (active)
  po4a @0.66_0+perl5_34 (active)
  xmltoman @0.4_1+perl5_34 (active)

which perl
/opt/local/bin/perl

perl --version | head -2 | tail -1
This is perl 5, version 34, subversion 1 (v5.34.1) built for
darwin-thread-multi-2level

It looks like many perl5-based utilities are not yet updated to
perl5.36, yet I'd like to use perl5.36 when I'm writing a perl
program.

I apparently don't understand enough about how to use "port select"
even after several readings.

On a slightly off-topic question, I'm still trying to replace all
"universal" ports with aarch64 ports (native) and when I install
and/or upgrade, I always specify "-s".  I've only had one problem (so
far) with this.

Thanks,
Ken Wolcott

Re: would like to download the source of a port, but not install it (I already have installed it)

[Kenneth Wolcott]

Thank you!

I was looking in the wrong place for the location where my port fetch
write to :-(

Now I got what I needed.

Thanks,
Ken

On Sat, Jul 1, 2023 at 2:15 PM Richard L. Hamilton  wrote:
>
> newapple:~ root# port fetch file
> --->  Fetching distfiles for file
> --->  Attempting to fetch file-5.44.tar.gz from 
> http://mirror.leaseweb.com/gentoo/distfiles/
> newapple:~ root# find /opt/local/var/macports/distfiles -name file-5.44.tar.gz
> /opt/local/var/macports/distfiles/file/file-5.44.tar.gz
> newapple:~ root# ls /opt/local/var/macports/distfiles/file
> file-5.41.tar.gz file-5.44.tar.gz
>
> Note that I had an older one left in there too; port clean doesn't get rid of 
> that unless you use the --dist or --all flag.
>
> To get an older version, you may have to go to github to get the older 
> version of the Portfile, look at that, and see where it fetches from. For 
> "file", the relevant Portfile (and patch files, which may exist for some 
> ports) are in
> https://github.com/macports/macports-ports/tree/master/sysutils/file
>
> (don't ask me how to get a particular historical version of a file from 
> github, I don't use it that much)
>
> On Jul 1, 2023, at 16:51, Kenneth Wolcott  wrote:
>
> Hi;
>
>  Another very basic question that I missed the answer to in my search:
>
> How to just download the source of a port?
>
> I already have installed the port in question, I'd just like to
> examine the source.
>
> All the "easy" ways to obtain the source code seem to be temporarily
> blocked by circumstances (original web site down, etc).
>
> The specific port I'm interested in is "file".
>
> Thanks,
> Ken Wolcott
>
>

would like to download the source of a port, but not install it (I already have installed it)

[Kenneth Wolcott]

Hi;

  Another very basic question that I missed the answer to in my search:

How to just download the source of a port?

I already have installed the port in question, I'd just like to
examine the source.

All the "easy" ways to obtain the source code seem to be temporarily
blocked by circumstances (original web site down, etc).

The specific port I'm interested in is "file".

Thanks,
Ken Wolcott

Re: port install hyper as a binary fails due to lack of arm64 variant (M1 chip)

[Kenneth Wolcott]

Again, thank you!

On Thu, Jun 15, 2023 at 5:14 PM Ryan Schmidt  wrote:
>
> On Apr 14, 2023, at 23:01, Kenneth Wolcott wrote:
>
> > port install hyper (build from source) fails (see bug #67241)
>
> I see the maintainer has not responded to the ticket. If you like, you could 
> file a bug report with the developers and see if they have any suggestions 
> for how to resolve this problem.
>
>
> > port install hyper as a binary fails due to lack of arm64 variant (M1 chip)
>
> Naturally; we can't provide a binary if we cannot build that binary.
>

Re: how to prepare an existing Macports instance for an xCode update or fix Macports after xCode update?

[Kenneth Wolcott]

Thank you!

On Thu, Jun 15, 2023 at 5:03 PM Ryan Schmidt  wrote:
>
> On Jun 2, 2023, at 13:53, Kenneth Wolcott wrote:
>
> > how to prepare an existing Macports instance for an xCode update or
> > fix Macports after xCode update?
>
> No preparation is needed.
>
> > I have an xCode update notification.
> >
> > I have an existing MacPorts installation.
> >
> > Do I need to do anything to the MacPorts installation prior to the xCode 
> > update?
>
> No.
>
> > Do I need to do anything to the MacPorts installation after the cxCode 
> > update?
>
> No.
>
>
> After upgrading Xcode, make sure you open it once and complete any prompts, 
> including installing "additional components" and possibly agreeing to a 
> license. You can quit Xcode after completing these steps.
>
> If you have the command line tools installed, it's probably best to install 
> the CLT version that matches the Xcode version you have. You can download 
> Xcode and the CLT from the Apple developer download page.