Re: Call for testing: port migrate

[Franco Vaccari via macports-users]

Happy to report that the migration went smoothly. Just one port installation 
finished in error (grass, and looking at the port health that was expected, so 
also qgis3 +grass wasn’t migrated) but that didn’t prevent the migration to 
complete for all other ports (944 of them).

All this on a MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 and 
its CLT’s.

So, all in all, a very positive experience.

Thanks to the MacPorts team!

Ciao

Franco

> On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users 
>  wrote:
> 
> Dear Josh,
> 
> since your mail caught me a few minutes after updating from Ventura to 
> Sonoma, and a few seconds before I started to play with MacPorts migration, I 
> felt obliged to give the migrate command a shot…
> 
> Currently computing dependency order. Will let you know the outcome…
> 
> Ciao
> 
> Franco
> 
>> On 12 Jun 2024, at 09:00, Joshua Root  wrote:
>> 
>> A 'migrate' action has been added to MacPorts base in git on the master 
>> branch. If you are comfortable with checking out the git repo, installing 
>> MacPorts from source, running potentially buggy pre-release code, and 
>> reporting any issues, we would greatly appreciate you giving it a try.
>> 
>> The new action automates all parts of the existing Migration procedure apart 
>> from updating Xcode and the CLTs. After updating your OS to a new major 
>> version or transferring to a new machine with a different CPU architecture, 
>> you should be able to simply run:
>> 
>> sudo port migrate
>> 
>> and MacPorts base will first be rebuilt, and then all ports that need to be 
>> reinstalled to be compatible with your current system will be. Build 
>> failures should be handled as gracefully as possible and reported at the end.
>> 
>> Thanks to Umesh Singla for doing the initial work on this feature, and to 
>> Clemens Lang for doing much of the work of completing and updating the code.
>> 
>> - Josh
> 

Re: Call for testing: port migrate

[Franco Vaccari via macports-users]

Dear Josh,

since your mail caught me a few minutes after updating from Ventura to Sonoma, 
and a few seconds before I started to play with MacPorts migration, I felt 
obliged to give the migrate command a shot…

Currently computing dependency order. Will let you know the outcome…

Ciao

Franco

> On 12 Jun 2024, at 09:00, Joshua Root  wrote:
> 
> A 'migrate' action has been added to MacPorts base in git on the master 
> branch. If you are comfortable with checking out the git repo, installing 
> MacPorts from source, running potentially buggy pre-release code, and 
> reporting any issues, we would greatly appreciate you giving it a try.
> 
> The new action automates all parts of the existing Migration procedure apart 
> from updating Xcode and the CLTs. After updating your OS to a new major 
> version or transferring to a new machine with a different CPU architecture, 
> you should be able to simply run:
> 
> sudo port migrate
> 
> and MacPorts base will first be rebuilt, and then all ports that need to be 
> reinstalled to be compatible with your current system will be. Build failures 
> should be handled as gracefully as possible and reported at the end.
> 
> Thanks to Umesh Singla for doing the initial work on this feature, and to 
> Clemens Lang for doing much of the work of completing and updating the code.
> 
> - Josh

gnome-online-accounts finally built/installed :)

[Alexander Newman via macports-users]

Hello Ryan and Joshua,

Thank you very much for yor help with my Macports trac ticket (70090) regarding 
the recalcitrant “missing” #include  line in goaewsclient.c, 
greatly appreciated.

Not knowing enough about the inner workings of the ‘port’ build process, I kept 
running up against a rev-upgrade ‘loop' (of a sort), wherein the file that I 
had carefully changed go overwritten when port re-downloaded the source 
archive, even using the port -s install command. I finally had the cunning idea 
that I could pause the process in the terminal and copy back the altered file, 
which I did. A quite literal hack - with a blunt sxe! Extremely inelegant, but 
it worked! The process went right through to the install stage successfully, 
and the other two log-jammed ports behind it also got buit. I had initially got 
the build though to ‘destroot’  via fetch/configure/build, but couldn’t get it 
any further on account of lack of knowledge (see above). 

But all fixed now, thank you very much, chaps!

See terminal output below for “evidence”.

Best regards,
Alex.
…

Incompatible library version: /opt/local/libexec/gvfsd-trash requires version 
2.0.0 or later, but /opt/local/lib/libgcr-base-3.1.dylib provides version 1.0.0
--->  Found 45 broken files, matching files to ports 
--->  Found 3 broken ports, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
 gnome-online-accounts @3.44.0
 libgdata @0.18.1
 gvfs @1.36.2+python36
Continue? [Y/n]: Y

% 

sudo cp -v ~/Documents/Programming/goaewsclient.c 
build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnome-online-accounts/gnome-online-accounts/work/gnome-online-accounts-3.44.0/src/goabackend/
  

% fg

…

--->  Cleaning gvfs
--->  Removing work directory for gvfs
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found. 
--->  No broken ports found.

Re: /usr/bin/mail , mailutils port

[Christoph Kukulies via macports-users]

I must add that the behaviour is infact:


$ mail
Illegal use of "message list"
No mail for kuku
$ 

> Am 09.06.2024 um 11:20 schrieb Christoph Kukulies via macports-users 
> :
> 
> It seems that the installation of the mailutils port screwed up the 
> functioning of the `mail` commandline tool for sending mails.
> I'm pretty sure that I was able to forge the From field of an email I sent 
> with the "mail" command from the command line by editing
> ~/.mailrc with the line "from m...@valid.domain.tld" (without the 
> apostrophes).
> 
> This suddenly stopped working. Uninstalling mailutils didn't bring back the 
> functionality.
> 
> --
> Christoph
> 
> 

/usr/bin/mail , mailutils port

[Christoph Kukulies via macports-users]

It seems that the installation of the mailutils port screwed up the functioning 
of the `mail` commandline tool for sending mails.
I'm pretty sure that I was able to forge the From field of an email I sent with 
the "mail" command from the command line by editing
~/.mailrc with the line "from m...@valid.domain.tld 
" (without the apostrophes).

This suddenly stopped working. Uninstalling mailutils didn't bring back the 
functionality.

--
Christoph




smime.p7s
Description: S/MIME cryptographic signature

Criminals

[Jose Alfaro via macports-users]

i just find out exactly how are you guys stealing all my financial accounts 
dont you thought that some day i was going to find it out?? 
Mateo Flores Sanchez
Cameron Karhut
Camilo Palacios
Joana Aguilar
Talina Ramirez
Marta Hernandez "aka" Angelica Xajil
have been working with your tools and taking every penny from all my accounts 
and up to today you guys have come to be rich thanks to my family future 
savings and investments what after 19 yrs i have been working thinking and  the 
future of my loved ones and you guys didnt respected it that not even one of my 
portfolios were under my name but under Kamila wines beverages and more... 
Melanies nails product and more..:. Nicoles Worlds Elizabeth Pineda "aka" 
Jose Alfaro and take everything from them well gues what . be ready for the 
authorities because this time of course i will fill it up a report and i will 
report your company as well as a provided and complice of the criminals above 
mentioned

Jose Alfaro
Sent from my iPhone

Re: new certificates using apple-pki-bundle

[Riccardo Mottola via macports-users]

Eric Gallager wrote:

I think that the `certsync` port (alternative to curl-ca-bundle) is
supposed to help with this...


I have curl-ca-bundle installed.

Should I remove it?

I read the description

Export x509 CAs from the Mac OS X Keychain.

The package implements exporting of x509 CAs from the Mac OS X keychain, 
for use by OpenSSL and gnutls.



isn't that the opposite of what I need? I don't want to get stuff from 
Mac OS X keychain but update the keychain. Or do I get it wrong?


Riccardo

Thank you!

[Riccardo Mottola via macports-users]

Hi,

I always write about issues, problems... etc etc... because that is what 
we do on the mailing list, seek support and improvement for old and 
older mac versions.


My MacBook Pro's HD broke, I had to reinstall from scratch. It went out 
99% smooth! Just one package needed a nudge on compiler version. On 
10.11 in an evening I was productive again with developer tools (git, 
subversion, ecc), emacs and gimp! great!


Then I also bought an older, MacBook Pro for a bargain (relative, how it 
discovered) which runs 10.9


Again, I was able to install the same tools up to gimp and have a good 
second system. Great! (*)


If you had a "donate" for support, it would be worth one. Thanks. 
MacPorts really helps productivity and using OpenSource stuff on Mac!!!


Now I can get back with the difficult stuff like 10.5 and 10.6 with 
those nice old systems.


Riccardo

(*) except Meld, which is buggy, on 10.11, but completely broken on 10.9 
like it is on 10.6 and 10.7

Re: xcode not found while building

[Riccardo Mottola via macports-users]

Hi Joshua, Ryan,

Joshua Root wrote:
So make sure you checked oute4b3d80 and not an earlier commit where 
the version was 8.1 155. If use_xcode is already in the Portfile 
you're using, you probably need to run xcode-select. 
thanks you hinted me to the correct statement. I did check out a version 
before "use_xcode yes" was added to the Portfile.

However, it was not enough - ibtool of XCode 8 was required...
I was eventually able to build 8.0 r 146 ... Dit try a couple of 
intermediate version, but not all, so I am not sure it is really the 
latest to be buildable on El Capitan.


Interestingly, offically 9.0 was distributed and worked probably it 
can be built on later versions of MacOS and is compatible with previous 
ones, but with MacPorts we do a native build!


I will see what I can build then on 10.9, 10.7, 10.6, 10.5 going on 
:) Maybe somebody else is interested.


I wonder if these version can be integrated in official MacPorts, like 
limiting a certain Max version given the OS or Xcode version?

Or making a specific MacVim8 package, e.g.?

Riccardo

xcode not found while building

[Riccardo Mottola via macports-users]

Hi,

MacVim is difficult to build, I want to get a version build on older 
versions of MacOS.
I am trying to get a version building on 10.11. The current versions and 
most previous versions don't build, because XCode 8 is expected. I have 
XCode 7.3.1


Going back in history I got to 8.1 155

this has build failing.

Hunk #1 succeeded at 796 (offset 27 lines).
--->  Running ibtool for Preferences.nib
xcode-select: error: tool 'ibtool' requires Xcode, but active developer 
directory '/Library/Developer/CommandLineTools' is a command line tools 
instance
Command failed: ibtool --compile 
src/MacVim/English.lproj/Preferences.nib/keyedobjects.nib 
src/MacVim/English.lproj/Preferences.nib

Exit code: 1
Error: Failed to patch MacVim: command execution failed


But, as said, I have XCode installed! what cold be wrong?

Riccardo

Re: new certificates using apple-pki-bundle

[Eric Gallager via macports-users]

On Tue, May 21, 2024 at 4:37 AM Riccardo Mottola via macports-users
 wrote:
>
> Hi,
>
> Nils Breunese wrote:
> >> what certificates do you use with apple-pki-bundle? I got those from curl 
> >> (cacert.pem from https://curl.se/docs/caextract.html)
> >> On old Macs in Safari even a simple page like wikipedia is not loadable, I 
> >> thought it is a certificate issue, but it did not help. Firefox has its 
> >> own.
> >> Perhaps it is enforcing SSL 1.3 and I am busted?
> > What version of macOS and Safari are you using? According to sslscan 
> > en.wikipedia.org supports TLS 1.2 and 1.3.
>
> MacOS 10.9 and Safari 9.1.3
>
> I suppose that installed certificates should be available to all apps,
> if I did it right, the new certificates should be available system wide,
> right? Not just macports apps.
> So curl, wget..but also Safari or similar.
>

I think that the `certsync` port (alternative to curl-ca-bundle) is
supposed to help with this...

>
> Riccardo

Re: new certificates using apple-pki-bundle

[Riccardo Mottola via macports-users]

Hi,

Nils Breunese wrote:
>> what certificates do you use with apple-pki-bundle? I got those from curl 
>> (cacert.pem from https://curl.se/docs/caextract.html)
>> On old Macs in Safari even a simple page like wikipedia is not loadable, I 
>> thought it is a certificate issue, but it did not help. Firefox has its own.
>> Perhaps it is enforcing SSL 1.3 and I am busted?
> What version of macOS and Safari are you using? According to sslscan 
> en.wikipedia.org supports TLS 1.2 and 1.3.

MacOS 10.9 and Safari 9.1.3

I suppose that installed certificates should be available to all apps,
if I did it right, the new certificates should be available system wide,
right? Not just macports apps.
So curl, wget..but also Safari or similar.


Riccardo

Re: Dovecot install Error

[Horst Simon via macports-users]

After executing "port -d -y rev-upgrade” it showed the problem is the 
mysql8 variant which produced following error


Could not open /opt/local/lib/mysql8/mysql/libmysqlclient.24.dylib: 
Error opening or reading file (referenced from 
/opt/local/lib/dovecot/libdovecot-sql.0.dylib)

DEBUG: Marking /opt/local/lib/dovecot/libdovecot-sql.0.dylib as broken
DEBUG: Marking /opt/local/libexec/dovecot/auth as broken
DEBUG: Marking /opt/local/libexec/dovecot/dict as broken
--->  Found 3 broken files, matching files to ports
--->  Found 1 broken port, determining rebuild order
DEBUG: Broken: dovecot
DEBUG: Processing port dovecot @20060722:2.3.21_0+mysql8

The build worked after removing the mysql8 variant.


-- Original Message --
From "Horst Simon via macports-users" 


To "macports-users@lists.macports.org" 


Date 17/5/2024, 19:46:52
Subject Dovecot install Error


Hi,

Tried to install dovecot but it gives following errors and gets into a 
loop trying to install the port.


Error: Port dovecot is still broken after rebuilding it more than 3 
times.


Error: Please run port -d -y rev-upgrade and use the output to report a 
bug.


Error: rev-upgrade failed: Port dovecot still broken after rebuilding 3 
times


Error: Follow https://guide.macports.org/#project.tickets if you 
believe there is a bug.




Have attached the screen output.



Thanks and Regards,
Horst Simon

new certificates using apple-pki-bundle

[Riccardo Mottola via macports-users]

Hi,

what certificates do you use with apple-pki-bundle? I got those from 
curl (cacert.pem from https://curl.se/docs/caextract.html)
On old Macs in Safari even a simple page like wikipedia is not loadable, 
I thought it is a certificate issue, but it did not help. Firefox has 
its own.

Perhaps it is enforcing SSL 1.3 and I am busted?

Riccardo

Re: [OT] bad disk & MacOS reinstall

[Riccardo Mottola via macports-users]

Hi,

Horst Simon wrote:
I had todo a re-install on my 2010 MacBook Pro with High Sierra from 
scratch, my copy of High sierra I had was corrupted and caused my all 
kind of grief. I finally downloaded a new copy on my iMac using the 
command line

Got a new disk.

Using recovery partition I tried to dump/restore the partiton... but 
half during the process I got a disk error and the process aborted. 
Proof that it is gone.


at the end, I changed hard disk and had to reinstall. Now salvaging data.
I will reinstall MacPorts from scratch. Safer... and also a "test" like 
being a new user.


I still am a bit disappointed by SMART.

Does Macports have a tool to get SMART details? On linux  there is one  
quite comprehensive!


Riccardo

Dovecot install Error

[Horst Simon via macports-users]

Hi,

Tried to install dovecot but it gives following errors and gets into a 
loop trying to install the port.


Error: Port dovecot is still broken after rebuilding it more than 3 
times.


Error: Please run port -d -y rev-upgrade and use the output to report a 
bug.


Error: rev-upgrade failed: Port dovecot still broken after rebuilding 3 
times


Error: Follow https://guide.macports.org/#project.tickets if you believe 
there is a bug.




Have attached the screen output.



Thanks and Regards,
Horst Simon


Dovecot-Install-Error.txt.gz
Description: GNU Zip compressed data

Re: Preventing other software from linking against MacPorts libraries

[Bill Hill via macports-users]

On 09/05/2024 21:13, Dave Horsfall wrote:


The question has since been answered, but what was wrong with merely
renaming /opt/local temporarily?  That's what I would've done...


$ cat ~/Builds/bare_build.sh

unset C_INCLUDE_PATH
unset CPLUS_INCLUDE_PATH
unset LIBRARY_PATH ; export LIBRARY_PATH=/usr/lib
export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/Applications/CMake.app/Contents/bin:.
sudo mv /opt/local /opt/local.real
 

Re: Preventing other software from linking against MacPorts libraries

[Smith via macports-users]

> On May 10, 2024, at 12:14 PM, Ryan Schmidt  wrote:
> 
> On May 10, 2024, at 09:57, Smith wrote:
>> 
>> Thanks all for the replies. The software depends on openssl, libpng and 
>> libjpeg.
> 
> And the name and version of the software that depends on those?

https://github.com/istopwg/ippsample

> 
>> In the past with other projects I left MacPorts in place but used Homebrew 
>> to install these dependencies, or just built those dependencies from 
>> scratch. It's not a "bad" thing for them to link to MacPorts libraries per 
>> se.  
> 
> Having Homebrew and MacPorts installed at the same time is likely to cause 
> you problems. If you're building software manually, you could end up linking 
> against one library from MacPorts and another library from Homebrew which is 
> not only messy but might actually be incompatible if the two libraries are 
> related. 
> 
> It's even possible, if you install a MacPorts port that has to build from 
> source, that it is hard coded to look for Homebrew first and fall back to 
> MacPorts, in which case your MacPorts port is now linked with a Homebrew 
> library.
> 
> For these reasons we don't support having Homebrew installed at the same time 
> as MacPorts and recommend you pick one package manager and uninstall the 
> other(s). 
> 
> May I ask why you do not want to link your program with MacPorts libraries if 
> linking with Homebrew libraries is acceptable? Why are they ok and we aren't? 
> What can we change to become ok?

I'll work on enumerating the problems I'm having in more detail in a future 
reply to this thread.

> 
> 
>> Some of this might be due to my installing binary pre-built ports, which 
>> seem to not be code signed or not signed by me. I don't know if I were to 
>> install all ports in source form and build them locally would resolve some 
>> of my issues. I'm not sure how to cause port to reinstall everything 
>> installed from source and to use source ports rather than binary ports going 
>> forward. I'm sure it is documented somewhere...
> 
> On Apple Silicon, everything is at least ad-hoc signed because that's what 
> the toolchain does by default. On earlier systems most things are not signed 
> because that's what the toolchain does by default.
> 
> As far as I know there would be no difference if you built from source, 
> except that it would take a lot longer, use a lot more energy, and you might 
> encounter build failures. So I don't know why you would want to avoid the 
> binaries we spend so much effort providing. But if you do:
> 
> https://trac.macports.org/wiki/BinaryArchives#disable

Purely to explore that as a way of resolving the issue that I'm having.

Re: Preventing other software from linking against MacPorts libraries

[Smith via macports-users]

Thanks all for the replies. The software depends on openssl, libpng and 
libjpeg. In the past with other projects I left MacPorts in place but used 
Homebrew to install these dependencies, or just built those dependencies from 
scratch. It's not a "bad" thing for them to link to MacPorts libraries per se.  

Some of this might be due to my installing binary pre-built ports, which seem 
to not be code signed or not signed by me. I don't know if I were to install 
all ports in source form and build them locally would resolve some of my 
issues. I'm not sure how to cause port to reinstall everything installed from 
source and to use source ports rather than binary ports going forward. I'm sure 
it is documented somewhere...

Smith



> On May 9, 2024, at 6:39 AM, Bill Cole 
>  wrote:
> 
> On 2024-05-09 at 02:03:15 UTC-0400 (Thu, 9 May 2024 00:03:15 -0600)
> Smith via macports-users 
> is rumored to have said:
> 
>> Hello,
>> 
>> I occasionally run into a problem where I'm building software from a tarball 
>> or a git clone outside of MacPorts, and the build process somehow ends up 
>> linking or trying to link against libraries in the MacPorts space 
>> (/opt/local). How can I prevent this from happening? Sometimes I just end up 
>> deleting /opt/local to get it to build and then re-install MacPorts, which 
>> can be painful or at least tiresome. I have to assume there is a better way 
>> or that I'm doing something wrong?
>> 
>> Thanks in advance for any thoughts,
> 
> When building software outside of MacPorts, you should cleanse your 
> environment of any clues that /opt/local/ is a place to look for software. 
> Remove /opt/local/bin and /opt/local/sbin from your PATH when running any 
> 'configure' script (or other GNU auto* tools) that looks for tools and 
> libraries.
> 
> Any software that is meant to be multiplatform should have some mechanism for 
> explicitly setting where to find libraries, such as options to an 
> autoconf-based configure script. You can use those or (less ideal) just 
> manually obliterate any hints of /opt/local in the Makefiles created by the 
> configure script.
> 
> -- 
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Preventing other software from linking against MacPorts libraries

[Smith via macports-users]

Hello,

I occasionally run into a problem where I'm building software from a tarball or 
a git clone outside of MacPorts, and the build process somehow ends up linking 
or trying to link against libraries in the MacPorts space (/opt/local). How can 
I prevent this from happening? Sometimes I just end up deleting /opt/local to 
get it to build and then re-install MacPorts, which can be painful or at least 
tiresome. I have to assume there is a better way or that I'm doing something 
wrong?

Thanks in advance for any thoughts,

Smith

Xcode creating caches for the macports user (take 2)

[Eric Gallager via macports-users]

(trying this again since apparently the attachment was too big the first time)

I recently attempted installation/upgrading of some Xcode-related
port(s), and now I have 10GB of Xcode-related caches in the macports
user's home directory; see the attached (compressed) `du` output. Is
it expected that Xcode will do this? Is it ok to delete these caches,
and, if so, could that be something that `port reclaim` does
automatically? Or perhaps `port clean --all` when used on whichever
port it was that caused this? (I'm still not quite sure which port it
was specifically)


du_output.txt.gz
Description: GNU Zip compressed data

Re: intel videocard performance degraded severely after 9.4 update

[Riccardo Mottola via macports-users]

sorry, wrong list :)

intel videocard performance degraded severely after 9.4 update

[Riccardo Mottola via macports-users]

Hi,

I updated my trusty R52 ThinkPad to 9.4 - i915.
All went quite well.

wifi is unreliable - but that is most probably the same isue I have on
the T30 and I am already investigating that with Martin.

X11 performance however is close to unusable, even a simple xterm has
issues scrolling and there are artifacts in redrawing, sometimes
garbage, something wrong colors in the title bar!
With 9.3 it wasn't a a gaming platform, but quite usable for terminal
and programming.
I think that console switch sometimes had it loose acceleration, but it
was never so bad and never had artifacts.

wscons look and perform fine, the issue is X11.

[ 5.106546] kern.module.path=/stand/i386/9.4/modules
[ 5.106546] kern info: [drm] Memory usable by graphics device = 128M
[ 5.106546] kern info: [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[ 5.106546] kern info: [drm] Driver supports precise vblank
timestamp query.
[ 5.106546] i915drmkms0: interrupting at irq 11 (i915drmkms0)
[ 5.106546] WARNING: clock gained 4 days
[ 5.126546] kern error:
[drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler]
*ERROR* CPU pipe A FIFO underrun
[ 5.126546] kern error:
[drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler]
*ERROR* CPU pipe B FIFO underrun
[ 5.136547] kern error:
[drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem_stolen.c:555)i915_pages_create_for_stolen]
*ERROR* failed to load DMA map for stolen object: -22
[ 5.136547] kern info: [drm] initialized overlay support
[ 5.176547] kern error:
[drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem_stolen.c:555)i915_pages_create_for_stolen]
*ERROR* failed to load DMA map for stolen object: -22
[ 5.186566] intelfb0 at i915drmkms0
[ 5.186566] intelfb0: framebuffer at 0xdc295000, size 1024x768,
depth 32, stride 4096
[ 5.816557] wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100
emulation), using wskbd0

these errors look a bit scary, but I am pretty sure  the fifo underrun
was there before.
However *ERROR* failed to load DMA map for stolen object: -22 is new.


In Xorg.0.log I see:
[  1561.785] (EE) intel(0): Failed to submit rendering commands (Invalid
argument), disabling acceleration.

that doesn't look promising!

Riccardo

Keeping ansible-galaxy collections up to date?

[Ralph Seichter via macports-users]

I have been trying to figure out how the Ansible ports bundle plugins,
in particular the community.general collection [1]. Not having made much
progress so far, I thought I'd ask here. The currently bundled version
of community.general included seems quite outdated, but a manual update
attempt leads to this:

  $ ansible-galaxy collection install community.general
  Starting galaxy collection install process
  Nothing to do. All requested collections are already installed. If you
  want to reinstall them, consider using `--force`.

Replacing "install" with "verify" in the command above shows that there
are hundreds of files on my machine which don't match community.general,
so what gives?

Before I potentially screw up files managed by MacPorts by using
--force, what is the official way to get plugins/roles/collections
updated? I would be happy to create Trac tickets, but for which ports?
There are multiple Python versions to consider; 3.12 is just the one I
currently use.

-Ralph

[1] https://galaxy.ansible.com/ui/repo/published/community/general/

Re: [OT] bad disk & MacOS reinstall

[Horst Simon via macports-users]

I had todo a re-install on my 2010 MacBook Pro with High Sierra from scratch, 
my copy of High sierra I had was corrupted and caused my all kind of grief. I 
finally downloaded a new copy on my iMac using the command line

softwareupdate --list-full-installers
softwareupdate --fetch-full-installer --full-installer-version 10.13.6

After the download I created a bootable image on a USB stick.

I did a new install of mac ports and my applications. 
Regards,
Horst

> On 5 May 2024, at 17:46, Riccardo Mottola via macports-users 
>  wrote:
> 
> Hi all,
> 
> I have a slightly off-topic question.
> 
> I think the Hard Disk of my older MacBook Pro is failing. The computer has 
> long delays sometimes, in random moments. Maybe at login, maybe at 
> application startup. I never see error and when activity resumes, everything 
> goes fine, including GIT usage, browsing, compilation. No "pattern". Disk 
> Utility reports a verified SMART status and Disk First Aid says all is OK.
> 
> However Console reports:
> kernel[0]: disk0s2: I/O error.
> 
> about the same time when he delay started. I suppose some kind of issues (eg. 
> going out of calibration, head reset...), maybe nothing is corrupted yet, 
> but... I suppose the only fix is a disk replacement. I wonder why SMART 
> doesn't alert anything, but maybe the detailed status should be inspected. Is 
> there a command line utility that can give more detail?
> 
> My question is your experience in reinstall.
> 
> First way would be to able to format, partition and copy all files to an 
> external hard disk, swap and reboot. I have done this once 10 years ago in 
> PowerPC times and it was not trivial and they sell software to do that, which 
> I don't want to buy.
> 
> Second way would be to reinstall MacOS 10.11 (no DVD available...) from 
> scratch and then copy or reinstall things  (including MacPorts, of course).
> 
> With a "new" hard disk, what is the best way to reinstall OS like Apple 
> supplied? In the past I had some bad experiences with Internet install not 
> working/completing with weird errors.
> Also, I'd like to have disk utility and recovery working. I wonder if it will 
> work or some magic partition needs to recreated?
> Hardware Diagnostic Tools need to be installed extra, I have read.
> 
> Riccardo

[OT] bad disk & MacOS reinstall

[Riccardo Mottola via macports-users]

Hi all,

I have a slightly off-topic question.

I think the Hard Disk of my older MacBook Pro is failing. The computer 
has long delays sometimes, in random moments. Maybe at login, maybe at 
application startup. I never see error and when activity resumes, 
everything goes fine, including GIT usage, browsing, compilation. No 
"pattern". Disk Utility reports a verified SMART status and Disk First 
Aid says all is OK.


However Console reports:
kernel[0]: disk0s2: I/O error.

about the same time when he delay started. I suppose some kind of issues 
(eg. going out of calibration, head reset...), maybe nothing is 
corrupted yet, but... I suppose the only fix is a disk replacement. I 
wonder why SMART doesn't alert anything, but maybe the detailed status 
should be inspected. Is there a command line utility that can give more 
detail?


My question is your experience in reinstall.

First way would be to able to format, partition and copy all files to an 
external hard disk, swap and reboot. I have done this once 10 years ago 
in PowerPC times and it was not trivial and they sell software to do 
that, which I don't want to buy.


Second way would be to reinstall MacOS 10.11 (no DVD available...) from 
scratch and then copy or reinstall things  (including MacPorts, of course).


With a "new" hard disk, what is the best way to reinstall OS like Apple 
supplied? In the past I had some bad experiences with Internet install 
not working/completing with weird errors.
Also, I'd like to have disk utility and recovery working. I wonder if it 
will work or some magic partition needs to recreated?

Hardware Diagnostic Tools need to be installed extra, I have read.

Riccardo

Re: where is the MacPorts gcc?

[Eric Gallager via macports-users]

`ar` and `nm` are wrappers around the corresponding tools from
binutils/cctools; GCC wraps them for use in its LTO system, I'm pretty
sure. You probably want to do `port select gcc` and then choose one of
the options available to symlink gcc into place without its suffix. If
it's dyld giving you your error, though, switching compilers probably
won't help, but I guess you can always try anyways...

On Sat, May 4, 2024 at 12:12 AM 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

Re: bash prints errors for every non-existing command

[Baerenblau via macports-users]

Indeed, $LANG is the root cause (any of $LC_* is not set). Unset of $LANG or 
LANG=en_US.UTF-8 helps in my environment, setting it to e.g. "C" does not help.

At least a workaround :-)

Issue #41248 was created 10 years ago but it didn't happen for me until I 
upgraded to the current or previous Macos version.

Thanks!

Am 24.04.24 um 23:42 schrieb Rainer Müller:

On 24.04.24 18:33, Baerenblau via macports-users wrote:

I'm on macOS 14.4.1 (23E224) and continue to experience a long standing problem 
with bash from Macports

% which bash
/opt/local/bin/bash

% bash --version
GNU bash, Version 5.2.26(1)-release (x86_64-apple-darwin23.2.0)

For every command which is not found a error similar error like this is printed:

$ asdf
objc[1321]: +[__SwiftNativeNSStringBase initialize] may have been in progress 
in another thread when fork() was called.
objc[1321]: +[__SwiftNativeNSStringBase initialize] may have been in progress 
in another thread when fork() was called. We cannot safely call it or ignore it 
in the fork() child process. Crashing instead. Set a breakpoint on 
objc_initializeAfterForkError to debug.
Abort trap: 6

Xcode has been installed today. Then MacPorts has been updated to the latest 
version, machine is rebooted, issue continues to exist.


This is indeed a very long standing issue:
https://trac.macports.org/ticket/41248
https://trac.macports.org/ticket/68638

It appears that this crash is actually caused by gettext, when localizing the 
error message in the child process forked by bash.

Rainer

Re[2]: Latest Apache Segmentation Fault

[Horst Simon via macports-users]

Could be that there was an update in php which is not compatible with 
horde, this is the only thing I can think of. It was working with the 
Apache and php before the upgrade.

Will do more checking with.

Thanks for the reply
Horst Simon


-- Original Message --

From "Bill Cole" 

To "Horst Simon via macports-users" 
Date 24/4/2024, 23:10:54
Subject Re: Latest Apache Segmentation Fault


On 2024-04-24 at 01:34:11 UTC-0400 (Wed, 24 Apr 2024 05:34:11 +0000)
Horst Simon via macports-users 
is rumored to have said:


Hi,

I upgraded from MacPorts-2.8.1-13 to MacPorts-2.9.3-10.13 and did port update 
installed, this updated Apache 2.4.58 to Apache 2.4.59.
After the upgrade one URL which connects to the Horde Web server fails with 
following error in the apache error log:
[mpm_prefork:info] [pid 298] AH00162: server seems busy, (you may need to 
increase StartServers, or Min/MaxSpareServers), spawning 8 children, there are 
2 idle, and 4 total children

[core:notice] [pid 298] AH00052: child pid 715 exit signal Segmentation fault 
(11)

[core:notice] [pid 298] AH00052: child pid 714 exit signal Segmentation fault 
(11)



Other URL’s cacti and phpkyadmin are working fine.


I am not specifically familiar with Horde, but this looks like a failure of 
whatever Horde uses to run, e.g. php-fpm or mod_php. A common reason for this 
specific sort of failure is if you have different versions of PHP present and 
the loader manages to select conflicting versions of libraries



I still have MacPorts-2.8.1 on another machine and no updates and this one does 
not show any errors.



Are there changes in the updated apache which could cause this issues or 
additional parameters need to be changed?


Nothing in the Apache httpd 2.4.58->59 update itself is likely to cause trouble 
per se, but because it is a highly modular program with optional modules linking 
at run time, you can have mismatches between the core software and modules like 
mod_php.


-- Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

bash prints errors for every non-existing command

[Baerenblau via macports-users]

Hi,

I'm on macOS 14.4.1 (23E224) and continue to experience a long standing problem 
with bash from Macports

% which bash
/opt/local/bin/bash

% bash --version
GNU bash, Version 5.2.26(1)-release (x86_64-apple-darwin23.2.0)

For every command which is not found a error similar error like this is printed:

$ asdf
objc[1321]: +[__SwiftNativeNSStringBase initialize] may have been in progress 
in another thread when fork() was called.
objc[1321]: +[__SwiftNativeNSStringBase initialize] may have been in progress 
in another thread when fork() was called. We cannot safely call it or ignore it 
in the fork() child process. Crashing instead. Set a breakpoint on 
objc_initializeAfterForkError to debug.
Abort trap: 6

Xcode has been installed today. Then MacPorts has been updated to the latest 
version, machine is rebooted, issue continues to exist.

Any ideas?

Thanks!

Latest Apache Segmentation Fault

[Horst Simon via macports-users]

Hi,

I upgraded from MacPorts-2.8.1-13 to MacPorts-2.9.3-10.13 and did port 
update installed, this updated Apache 2.4.58 to Apache 2.4.59.
After the upgrade one URL which connects to the Horde Web server fails 
with following error in the apache error log:
[mpm_prefork:info] [pid 298] AH00162: server seems busy, (you may need 
to increase StartServers, or Min/MaxSpareServers), spawning 8 children, 
there are 2 idle, and 4 total children


[core:notice] [pid 298] AH00052: child pid 715 exit signal Segmentation 
fault (11)


[core:notice] [pid 298] AH00052: child pid 714 exit signal Segmentation 
fault (11)




Other URL’s cacti and phpkyadmin are working fine.



I still have MacPorts-2.8.1 on another machine and no updates and this 
one does not show any errors.




Are there changes in the updated apache which could cause this issues or 
additional parameters need to be changed?




Regards,

Horst Simon

Re: Fetching port getmail fails

[Horst Simon via macports-users]

Thanks for the explanations
Sent from my iPhone

> On 21 Apr 2024, at 07:08, Ryan Schmidt  wrote:
> 
> On Apr 19, 2024, at 18:24, Horst Simon wrote:
>> 
>> What I tried to explain is that the curl I used in previous installs was 
>> from MacPorts, but when it failed I had only the macOS High Sierra native 
>> curl.
> 
> That's what I thought you meant, but I don't think you've achieved that.
> 
> You wrote:
> 
>> after adding changing
>> the root profile using /usr/local/bin and /usr/local/sbin it worked ok
> 
> I assume you mean that you edited the shell startup file of the root user so 
> that /usr/local/bin and /usr/local/sbin are included in its PATH environment 
> variable.
> 
> I further assume that you either meant /opt/local instead of /usr/local or 
> that you have built MacPorts from source and specified the configure 
> arguments --prefix=/usr/local --with-unsupported-prefix when doing so, since 
> using /usr/local as your MacPorts prefix is not recommended.
> 

Yes /opt/local and not /usr/local

> If that's what you did, then that will affect what commands are available 
> when you use a root shell but it will not affect which curl MacPorts uses.
> 
> MacPorts doesn't use the curl executable. It uses the libcurl library. Which 
> one it uses is determined at configure time. If you use MacPorts installed 
> from our installer, it uses /usr/lib/libcurl.dylib. If you build MacPorts 
> from source, you can have it use whatever curl you like by using the 
> --with-curlprefix configure argument, except that using the libcurl installed 
> by MacPorts is not recommended because if you ever deactivate the curl port, 
> then you would not be able to run MacPorts anymore because it would not be 
> able to find the libcurl library anymore.
> 
> To overcome this, some users who want to have MacPorts use a newer libcurl 
> than their OS provides build curl from source in some other prefix and 
> configure MacPorts to use that, or they install curl in a second copy of 
> MacPorts that they build from source in some other prefix and then build 
> their primary copy of MacPorts from source, using the libcurl from the second 
> copy of MacPorts.
> 
> We try to keep things working so that this is not necessary, e.g. by having a 
> network of mirror servers, making mirror servers available over http for old 
> OS versions whose libcurls can't access https anymore, etc. When you find 
> situations like this one with getmail where it's not working, just report it 
> to us and we'll figure out what needs to be fixed.
> 
> 

Re[2]: Fetching port getmail fails

[Horst Simon via macports-users]

I am sorry misunderstood your last email, but anyway it is working now.

What I tried to explain is that the curl I used in previous installs was 
from MacPorts, but when it failed I had only the macOS High Sierra 
native curl.


Regards,
Horst


-- Original Message --

From "Ryan Schmidt" 

To "Horst Simon" 
Cc macports-users@lists.macports.org
Date 20/4/2024, 09:16:45
Subject Re: Fetching port getmail fails


On Apr 19, 2024, at 17:17, Horst Simon wrote:

 Yes, this was the problem, it used the macOS High Sierra curl, after adding 
changing
 the root profile using /usr/local/bin and /usr/local/sbin it worked ok.


I'm not sure what you're referring to with the root profile. But after writing 
my message to the list I manually put the missing file onto the MacPorts 
distfiles server so that you could fetch it from one of our mirrors, and I 
updated the getmail port to include a second download location.

Re: Fetching port getmail fails

[Horst Simon via macports-users]

Yes, this was the problem, it used the macOS High Sierra curl, after adding 
changing 
the root profile using /usr/local/bin and /usr/local/sbin it worked ok.

Thanks
Horst Simon


> On 20 Apr 2024, at 01:36, Ryan Schmidt  wrote:
> 
> On Apr 19, 2024, at 00:15, contextnerror wrote:
>> The issue is that you’re getting too many redirects for the pyropus.ca url. 
>> I'm not sure why this is happening to you and not me.
> 
> You probably use different versions of macOS and therefore different versions 
> of curl. This is a bug in curl versions released between 2014 and 2022. 
> 
> https://trac.macports.org/ticket/67186

Re[2]: Fetching port getmail fails

[Horst Simon via macports-users]

I have the main.log file attached, it shows 404 errors.

-- Original Message --
From: "contextnerror" 
To: "Horst Simon" 
Cc: macports-users@lists.macports.org
Sent: 19/04/2024 1:38:02 PM
Subject: Re: Fetching port getmail fails


It’s currently working for me right now. Do you have a log?


 On Apr 18, 2024, at 7:32 PM, Horst Simon via macports-users 
 wrote:

 Tried to install get mail and get following errors, it worked a few days ago, 
any answers why?

 --->  Computing dependencies for getmail
 --->  Fetching archive for getmail
 --->  Attempting to fetch getmail-5.16_0.darwin_any.noarch.tbz2 from 
http://packages.macports.org/getmail
 --->  Attempting to fetch getmail-5.16_0.darwin_any.noarch.tbz2 from 
http://jog.id.packages.macports.org/macports/packages/getmail
 --->  Attempting to fetch getmail-5.16_0.darwin_any.noarch.tbz2 from 
http://mirror.fcix.net/macports/packages/getmail
 --->  Fetching distfiles for getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://aarnet.au.distfiles.macports.org/pub/macports/distfiles/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://mirror.fcix.net/macports/distfiles/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
https://pyropus.ca/software/getmail/old-versions/
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://ywg.ca.distfiles.macports.org/mirror/macports/distfiles/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://kmq.jp.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://cjj.kr.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://mse.uk.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://fra.de.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://pek.cn.distfiles.macports.org/macports/distfiles/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://cph.dk.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://fco.it.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://nue.de.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://atl.us.distfiles.macports.org/getmail
 --->  Attempting to fetch getmail-5.16.tar.gz from 
http://jog.id.distfiles.macports.org/macports/distfiles/getmail
 Error: Failed to fetch getmail: The requested URL returned error: 404 Not Found
 Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_mail_getmail/getmail/main.log
 for details.
 Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
 Error: Processing of port getmail failed

 Horst


main.log.gz
Description: GNU Zip compressed data

Fetching port getmail fails

[Horst Simon via macports-users]

Tried to install get mail and get following errors, it worked a few days 
ago, any answers why?




--->  Computing dependencies for getmail

--->  Fetching archive for getmail

--->  Attempting to fetch getmail-5.16_0.darwin_any.noarch.tbz2 from 
http://packages.macports.org/getmail


--->  Attempting to fetch getmail-5.16_0.darwin_any.noarch.tbz2 from 
http://jog.id.packages.macports.org/macports/packages/getmail


--->  Attempting to fetch getmail-5.16_0.darwin_any.noarch.tbz2 from 
http://mirror.fcix.net/macports/packages/getmail


--->  Fetching distfiles for getmail

--->  Attempting to fetch getmail-5.16.tar.gz from 
http://aarnet.au.distfiles.macports.org/pub/macports/distfiles/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://mirror.fcix.net/macports/distfiles/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
https://pyropus.ca/software/getmail/old-versions/


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://ywg.ca.distfiles.macports.org/mirror/macports/distfiles/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://kmq.jp.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://cjj.kr.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://mse.uk.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://fra.de.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://pek.cn.distfiles.macports.org/macports/distfiles/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://cph.dk.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://fco.it.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://nue.de.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://atl.us.distfiles.macports.org/getmail


--->  Attempting to fetch getmail-5.16.tar.gz from 
http://jog.id.distfiles.macports.org/macports/distfiles/getmail


Error: Failed to fetch getmail: The requested URL returned error: 404 
Not Found


Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_mail_getmail/getmail/main.log 
for details.


Error: Follow https://guide.macports.org/#project.tickets if you believe 
there is a bug.


Error: Processing of port getmail failed



Horst

The whole redis/redict/valkey forking situation

[Eric Gallager via macports-users]

So one of the stories getting talked about in the FOSS world recently
has been how redis changed its license, leading to some new competing
forks:
https://vickiboykis.com/2024/04/16/redis-is-forked/
This presents a number of questions for what will happen in MacPorts?
- Will MacPorts continue to maintain a redis port?
- Will MacPorts add ports for valkey and/or redict?
- If so, will the 3 conflict, or will they all be installable separately?
- For ports that currently depend on redis, will they continue to
require redis specifically, or will it be possible to use valkey
and/or redict to satisfy their dependencies instead?
- Do any new licenses need to be added to MacPorts' list of recognized
licenses in response to this change? And does
port_binary_distributable.tcl work properly with the new license(s)?
Anyways, this isn't too big of an issue for me personally, as I don't
actually use redis myself, but I figured some other MacPorts users
might appreciate some clarity on the topic...
Eric

Re: macports-users Digest, Vol 212, Issue 11

[Joël Brogniart via macports-users]

Hi,

It seems that Preview, GraphicConverter and Pixelmator Pro are able to view and 
open ".ppm" files.

Yours,

Joël Brogniart

> Message: 1
> Date: Tue, 16 Apr 2024 19:44:22 -0700
> From: Kenneth Wolcott 
> To: macports-users@lists.macports.org
> Subject: what app on a Mac reads/views ppm files?
> Message-ID:
> 
> Content-Type: text/plain; charset="UTF-8"
> 
> 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[2]: build of rspamd and amavisd-new not working with High Sierra

[Horst Simon via macports-users]

Thanks to Ryan and Bill, I followed Bill’s instructions, applied the 
patch and the build and install completed without errors, after this I 
could install
amavisd-new without any problem and too it is working. This patch fixed 
the issue on High Sierra.


Thanks and Regards,
Horst Simon


-- Original Message --

From "Ryan Schmidt" 

To "Bill Cole" 
Cc "MacPorts Users" 
Date 12/4/2024, 09:03:35
Subject Re: build of rspamd and amavisd-new not working with High Sierra


On Apr 11, 2024, at 09:04, Bill Cole wrote:


 I got to 
https://github.com/DCIT/perl-CryptX/pull/99/commits/9568b3e7ce17d9e3ace6ddbfb7df2d2e387aa91f
 which shows the patch graphically. If you are dedicated to actually using the 
'patch' utility with a patchfile, there should be a way to get GitHub to 
provide that, but I don't see it.


Manually append .patch to the URL to get:

https://github.com/DCIT/perl-CryptX/pull/99/commits/9568b3e7ce17d9e3ace6ddbfb7df2d2e387aa91f.patch

Re: build of rspamd and amavisd-new not working with High Sierra

[Horst Simon via macports-users]

Thanks will try it this way

> On 12 Apr 2024, at 00:06, Bill Cole 
>  wrote:
> 
> On 2024-04-11 at 06:18:58 UTC-0400 (Thu, 11 Apr 2024 20:18:58 +1000)
> Horst Simon via macports-users 
> is rumored to have said:
> 
>> I understand the wiki information, but at a loss on how to get the patch.
> 
> Following the link Ryan put in the ticket and navigating the obfuscatory 
> GitHub interface, I got to 
> https://github.com/DCIT/perl-CryptX/pull/99/commits/9568b3e7ce17d9e3ace6ddbfb7df2d2e387aa91f
>  which shows the patch graphically. If you are dedicated to actually using 
> the 'patch' utility with a patchfile, there should be a way to get GitHub to 
> provide that, but I don't see it. It is small enough (3 new lines and 2 
> changed across 2 header files and crypt.c) that you could make changes to the 
> source by hand AFTER getting it downloaded, extracted, and patched by any 
> pre-existing MacPorts patches, after which MacPorts won't notice your changes:
> 
> port patch  p5.34-cryptx
> 
> You will then have a copy of the source tree under the port's work directory 
> (`port work p5.34-cryptx`) where you can edit the files and them try 'port 
> build p5.34-cryptx' again.
> 
> 
> 
>> 
>>>> On 11 Apr 2024, at 18:30, contextnerror  wrote:
>>> 
>>> 
>>> You would take the changes from the pull request and follow 
>>> https://trac.macports.org/wiki/howto/PatchLocal
>>> 
>>>>> On Apr 11, 2024, at 1:15 AM, Horst Simon via macports-users 
>>>>>  wrote:
>>>>> 
>>>>  Thanks Ryan for the response I prefer to get the p5-cryptx working. Is 
>>>> there a how to or instruction on how to build it using the patch
>>>>> Horst Simon
>>>> 
>>>> 
>>>>> On 11 Apr 2024, at 17:48, Ryan Schmidt  wrote:
>>>>> 
>>>>> 
>>>>>> On Apr 10, 2024, at 22:59, Horst Simon wrote:
>>>>>> 
>>>>>> I tried to install amavisd-new on macOS High Sierra but fails in the 
>>>>>> install of the dependency p5.34-cryptx, after this I tried to change to 
>>>>>> rspamd,
>>>>>> but rspamd  too fails to build.
>>>>>> 
>>>>>> I already created request ticket for p5.34cryptx. My question is is it 
>>>>>> possible to get at least on of these working on High Sierra and what is 
>>>>>> needed from me.
>>>>> 
>>>>> The rspamd problem is
>>>>> https://trac.macports.org/ticket/63785. It currently cannot build for 
>>>>> macOS 10.14 or earlier because it uses features from a newer version of 
>>>>> C++ than those earlier macOS versions can normally accommodate.
>>>>> 
>>>>> The p5-cryptx problem is https://trac.macports.org/ticket/68470. I added 
>>>>> a comment there about some similar upstream bug reports and a proposed 
>>>>> upstream patch. You could try that patch and see if it solves the 
>>>>> problem. If so we can add it to the port. If it doesn't solve the problem 
>>>>> then report the problem to the developers so they can develop a fix.
> 
> 
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Re: build of rspamd and amavisd-new not working with High Sierra

[Horst Simon via macports-users]

I understand the wiki information, but at a loss on how to get the patch.

> On 11 Apr 2024, at 18:30, contextnerror  wrote:
> 
> 
> You would take the changes from the pull request and follow 
> https://trac.macports.org/wiki/howto/PatchLocal 
> 
>>> On Apr 11, 2024, at 1:15 AM, Horst Simon via macports-users 
>>>  wrote:
>>> 
>>  Thanks Ryan for the response I prefer to get the p5-cryptx working. Is 
>> there a how to or instruction on how to build it using the patch
>>> Horst Simon
>> 
>> 
>>> On 11 Apr 2024, at 17:48, Ryan Schmidt  wrote:
>>> 
>>> 
>>>> On Apr 10, 2024, at 22:59, Horst Simon wrote:
>>>> 
>>>> I tried to install amavisd-new on macOS High Sierra but fails in the 
>>>> install of the dependency p5.34-cryptx, after this I tried to change to 
>>>> rspamd,
>>>> but rspamd  too fails to build.
>>>> 
>>>> I already created request ticket for p5.34cryptx. My question is is it 
>>>> possible to get at least on of these working on High Sierra and what is 
>>>> needed from me.
>>> 
>>> The rspamd problem is 
>>> https://trac.macports.org/ticket/63785. It currently cannot build for macOS 
>>> 10.14 or earlier because it uses features from a newer version of C++ than 
>>> those earlier macOS versions can normally accommodate. 
>>> 
>>> The p5-cryptx problem is https://trac.macports.org/ticket/68470. I added a 
>>> comment there about some similar upstream bug reports and a proposed 
>>> upstream patch. You could try that patch and see if it solves the problem. 
>>> If so we can add it to the port. If it doesn't solve the problem then 
>>> report the problem to the developers so they can develop a fix. 

Re: build of rspamd and amavisd-new not working with High Sierra

[Horst Simon via macports-users]

Thanks Ryan for the response I prefer to get the p5-cryptx working. Is there a 
how to or instruction on how to build it using the patch
> Horst Simon


> On 11 Apr 2024, at 17:48, Ryan Schmidt  wrote:
> 
> 
>> On Apr 10, 2024, at 22:59, Horst Simon wrote:
>> 
>> I tried to install amavisd-new on macOS High Sierra but fails in the install 
>> of the dependency p5.34-cryptx, after this I tried to change to rspamd,
>> but rspamd  too fails to build.
>> 
>> I already created request ticket for p5.34cryptx. My question is is it 
>> possible to get at least on of these working on High Sierra and what is 
>> needed from me.
> 
> The rspamd problem is 
> https://trac.macports.org/ticket/63785. It currently cannot build for macOS 
> 10.14 or earlier because it uses features from a newer version of C++ than 
> those earlier macOS versions can normally accommodate. 
> 
> The p5-cryptx problem is https://trac.macports.org/ticket/68470. I added a 
> comment there about some similar upstream bug reports and a proposed upstream 
> patch. You could try that patch and see if it solves the problem. If so we 
> can add it to the port. If it doesn't solve the problem then report the 
> problem to the developers so they can develop a fix. 

build of rspamd and amavisd-new not working with High Sierra

[Horst Simon via macports-users]

Hi,

I tried to install amavisd-new on macOS High Sierra but fails in the 
install of the dependency p5.34-cryptx, after this I tried to change to 
rspamd,

but rspamd  too fails to build.

I already created request ticket for p5.34cryptx. My question is is it 
possible to get at least on of these working on High Sierra and what is 
needed from me.


Kind Regards,
horst Simon

Re: macports2.93 p5.34-cryptx build failed

[Horst Simon via macports-users]

I created ticket #69706Sent from my iPhoneOn 10 Apr 2024, at 18:32, Ryan Schmidt  wrote:On Apr 8, 2024, at 19:10, Horst Simon wrote:fails with building p5.34-cryptx. Macports version 2.93OS High Sierra Version 10.13.6Presumably this is https://trac.macports.org/ticket/68470

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

[Alexander Newman via macports-users]

I have exactly the same problem, but with rygel as another affected build. I've 
uninstalled rygel but left webkit2-gtk in place. I now just ignore the 
rev-upgrade suggestion (n). It seems to be associated with gstreamer and cmake 
(cmake recently updated on my Ventura machine). Last time I looked (two days 
ago) the macports page was showing a healthy port (Sonoma on down).

Cheers,
Alex.

> On 10 Apr 2024, at 4:20 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
> 

macports2.93 p5.34-cryptx build failed

[Horst Simon via macports-users]

I try to install amavisd-new, but fails with building p5.34-cryptx.

Macports version 2.93
OS High Sierra Version 10.13.6

I have attached the main.log should i make a bug report? I had no 
problem with the build on Ventura.


Thanks and Regards,
Horst Simon



main.log.gz
Description: GNU Zip compressed data

Re: force rebuild a port

[Riccardo Mottola via macports-users]

Hi Ryan,


Ryan Schmidt wrote:

As others explained, because you're getting a pre-compiled binary from our 
servers. This is probably what you want if you suspect something has corrupted 
your local installation and you want to reinstall.


Thank you guys, I didn't think of binary packages, since some had some 
not. I guess it comes down to variants.



On the other hand, if you believe there is a defect in our pre-compiled binary, 
add -s to the -n flag to force a build from source. If that fixes the issue 
you're seeing, file a bug so we can increase the port's revision (and possibly 
additional changes) so that a new corrected binary is produced.


Yes, I suppose generally a reference package should help. I am hunting 
indeed down a troublesome situation on this old MacBook 10.6. All gtk 
based apps on quartz do not display text since more than a year. This 
happened also on 10.7. I about back then I hunted it down to an issue 
with harfbuzz... although pango and other packages were connected. Since 
then 10.7 works. I have some "pinned" some repositories, but all works 
on 10.7. I was able to briefly have things working on 10.5 too! 
(currently there are some major breakages) so I thought something must 
be broken on 10.6 in terms of build options, not OS support.
I have about the same setup on 10.6 and 10.7, same pinned version of 
pango. both 64bit... yet still the same issues. That is why I thought to 
selectively rebuild and reinstall things.


the tree up to Gimp is large, so the hunt is hard!

on 10.7 many packages come indeed with pre-compiled things.

Riccardo

Re: force rebuild a port

[Riccardo Mottola via macports-users]

Hi Richard,

last week I did a test and it worked, but it was not what I needed. 
Probably it was a port already in need to upgrade.

I have a system now where all ports are up-to-date (as of "port outdated").

If I issue e.g.

port -n upgrade --force --no-rev-upgrade gtk2


It takes it time to recompile gtk2... I actually see "Building gtk2" [* * *]

If I do

port -n upgrade --force --no-rev-upgrade harfbuzz


it completes in a matter of seconds... and the ol' MacBook isn't that 
fast :)


I see cleaning, uninstalling, cleaning, installing activating, 
cleaning... but never configure/building!

Why?

Regards,
Riccardo

Richard L. Hamilton wrote:

To explain:

-n prevents rebuilding ports that the ports being upgraded (works with install 
too I suppose, but there should be no need for that) depend on; it may cause 
failure if they're not already installed and up-to-date

--force forces upgrading even of a port that's current; but without the -n, 
that would apply to everything it depends on too, which is slow and might cause 
more problems (esp. if there are issues with any of the build tools used)

--no-rev-upgrade because while the check for broken ports is usually good, it 
might get in the way in this sort of situation; and because one might be 
repeating the command one port at a time for more than one port (separate 
commands so it tries them all even if one fails), and since the check is a bit 
slow, that saves time

This is rather far down the list of what one should try, because normally -n is not a 
good idea (although it can make sense to limit --force), and because ideally one would 
just do "port upgrade" and let it sort out what needs doing. But clearly it 
helps sometimes when things aren't right and you don't want to do more than necessary.

Re: MacPorts 2.9.3 has been released

[Sriranga Veeraraghavan via macports-users]

I’m on Ventura 13.6.6 and Xcode 14.3 and I also observed that ‘port selfupdate’ 
didn’t update 2.9.1 to 2.9.2 or 2.9.2 to 2.9.3.  I installed the Ventura 
packages for 2.9.2 and 2.9.3 and both seemed to perform the update properly.

Thanks,

-ranga

> On Apr 3, 2024, at 9:29 PM, Peter West via macports-users 
>  wrote:
> 
> I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the port 
> install. Is this something you’re aware of?
> 
> I’ve been installing these to try to fix the “missing m4” problem, but 
> neither seemed to fix it. Should I add a comment to one of the number of 
> issues in trac concerning this?
> 
> In any case, I’m downgrading to Xcode 15.1.
> 
> —
> Peter West
> p...@pbw.id.au
> `Mary Magdalene went and said to the disciples, “I have seen the Lord”; and 
> she told them that he had said these things to her.`
> 
>> On 4 Apr 2024, at 12:00 PM, Joshua Root  wrote:
>> 
>> The MacPorts Project is pleased to announce the release of version
>> 2.9.3. This is a bugfix release with small changes only. See the
>> ChangeLog [1] for the list of changes.
>> 
>> 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] <https://github.com/macports/macports-base/blob/release-2.9/ChangeLog>
>> [2] <https://www.macports.org/install.php>
>> [3] <https://github.com/macports/macports-base/releases/tag/v2.9.3>
>> [4] <https://trac.macports.org/wiki/jmr>
> 

Re: MacPorts 2.9.3 has been released

[Peter West via macports-users]

I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the port 
install. Is this something you’re aware of?

I’ve been installing these to try to fix the “missing m4” problem, but neither 
seemed to fix it. Should I add a comment to one of the number of issues in trac 
concerning this?

In any case, I’m downgrading to Xcode 15.1.

—
Peter West
p...@pbw.id.au
`Mary Magdalene went and said to the disciples, “I have seen the Lord”; and she 
told them that he had said these things to her.`

> On 4 Apr 2024, at 12:00 PM, Joshua Root  wrote:
> 
> The MacPorts Project is pleased to announce the release of version
> 2.9.3. This is a bugfix release with small changes only. See the
> ChangeLog [1] for the list of changes.
> 
> 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] <https://github.com/macports/macports-base/blob/release-2.9/ChangeLog>
> [2] <https://www.macports.org/install.php>
> [3] <https://github.com/macports/macports-base/releases/tag/v2.9.3>
> [4] <https://trac.macports.org/wiki/jmr>

Re: [EXTERNAL] Re: Library libtdbc used in restore_ports script is unsigned

[Fielding, Eric J (US 329A) via macports-users]

Thanks, Josh, for the workaround. Using “sudo `readlink 
/opt/local/bin/port-tclsh` ./restore_ports.tcl” worked great.

++Eric

The most straightforward workaround is to use a different path for the
interpreter. /opt/local/bin/port-tclsh is a symlink to the actual
tclsh8.6 in a subdirectory, so running the script like this should work:

sudo `readlink /opt/local/bin/port-tclsh` ./restore_ports.tcl

Hopefully we can ship automatic migration in MacPorts base soon and
retire restore_ports.tcl.

- Josh

Re: force rebuild a port

[Riccardo Mottola via macports-users]

Hi Richard,

Richard L. Hamilton wrote:
> port -n upgrade --force --no-rev-upgrade crankyport
> 
> It might not work if crankyport needs the latest of something it depends on 
> and that isn't already up-to-date. But a lot of times, it does work.

this is a good one.. appears to work for stubborn libgdk, it just rebuilt

I prefer it to build/uninstall/install because upgrade preserves the
automatic status and variants automagically.

Riccardo

Re: Library libtdbc used in restore_ports script is unsigned

[Eric Gallager via macports-users]

On Thu, Mar 21, 2024 at 12:53 AM Joshua Root  wrote:
>
> > I recently upgraded from macOS 13.x to macOS 14.3.1 Sonoma and started 
> > running the MacPorts Migration process. I got interrupted and did the minor 
> > macOS update to macOS 14.4 and tried to run the “restore_ports.tcl” script, 
> > which worked for a while but then threw an error about the libtdbc library 
> > being unsigned. I don’t know if this is something that changed recently. 
> > What is the recommended procedure for fixing this? Uninstall all the ports 
> > and reinstall them?
> >
> > This is the full error:
> > dlopen(/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib, 0x0006): tried: 
> > '/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' (code signature in 
> > <3CE89C0F-A387-3934-8B3D-5834290B7BD3> 
> > '/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' not valid for use in process: 
> > mapped file has no cdhash, completely unsigned? Code has to be at least 
> > ad-hoc signed.), 
> > '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib'
> >  (no such file), '/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' (code 
> > signature in <3CE89C0F-A387-3934-8B3D-5834290B7BD3> 
> > '/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' not valid for use in process: 
> > mapped file has no cdhash, completely unsigned? Code has to be at least 
> > ad-hoc signed.)
> >  while executing
> > "load /opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib Tdbc"
> >  ("package ifneeded tdbc 1.1.7" script)
> >  invoked from within
> > "package require tdbc"
> >  (file "/opt/local/lib/tcl8/8.6/tdbc/sqlite3-1.1.7.tm" line 13)
> >  invoked from within
>
> This is likely an unfortunate interaction with a feature of tclsh and a
> feature of macOS. Tcl will look for packages in the same prefix as the
> interpreter that is running the script, and in this case, the tclsh
> shipped with MacPorts base finds a tdbc library installed by a port. The
> former is signed and the latter is not, and macOS doesn't allow signed
> executables to load unsigned libraries.
>
> The most straightforward workaround is to use a different path for the
> interpreter. /opt/local/bin/port-tclsh is a symlink to the actual
> tclsh8.6 in a subdirectory, so running the script like this should work:
>
> sudo `readlink /opt/local/bin/port-tclsh` ./restore_ports.tcl
>

Could this info go on the wiki somewhere or something? Like the
"Migration" page, or whichever it is that documents restore_ports.tcl
again...

> Hopefully we can ship automatic migration in MacPorts base soon and
> retire restore_ports.tcl.
>

Yeah, please notify me once this happens; I've been reluctant to
update from Big Sur just due to how much of a pain the
restore_ports.tcl process can be...

> - Josh
>

Library libtdbc used in restore_ports script is unsigned

[Fielding, Eric J (US 329A) via macports-users]

I recently upgraded from macOS 13.x to macOS 14.3.1 Sonoma and started running 
the MacPorts Migration process. I got interrupted and did the minor macOS 
update to macOS 14.4 and tried to run the “restore_ports.tcl” script, which 
worked for a while but then threw an error about the libtdbc library being 
unsigned. I don’t know if this is something that changed recently. What is the 
recommended procedure for fixing this? Uninstall all the ports and reinstall 
them?

This is the full error:
dlopen(/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib, 0x0006): tried: 
'/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' (code signature in 
<3CE89C0F-A387-3934-8B3D-5834290B7BD3> 
'/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' not valid for use in process: 
mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc 
signed.), 
'/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib'
 (no such file), '/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' (code signature 
in <3CE89C0F-A387-3934-8B3D-5834290B7BD3> 
'/opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib' not valid for use in process: 
mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc 
signed.)
while executing
"load /opt/local/lib/tdbc1.1.7/libtdbc1.1.7.dylib Tdbc"
("package ifneeded tdbc 1.1.7" script)
invoked from within
"package require tdbc"
(file "/opt/local/lib/tcl8/8.6/tdbc/sqlite3-1.1.7.tm" line 13)
invoked from within
…

Thanks,
++Eric

Re: MacPorts vs. Apple compiler issues, Handle

[Riccardo Mottola via macports-users]

Hi,

Sergio Had wrote:

Could you refer me to the beginning of this discussion please?

it started on the Mac Users mailing list, you can find in the archives!




I am also involved in AF project:)


Oh, I am curious, how?
I am essentially the only active developer currently, except Roy who 
does its windows fork.


Riccardo

Re: MacPorts vs. Apple compiler issues, Handle

[Riccardo Mottola via macports-users]

Hi,

Joshua Root wrote:

(Moving to macports-dev as it is a better fit for this topic.)


indeed, it is a development issue, although well, not for a MacPorts 
package (yet?) but use of MP development tools.


Issues that only appear at higher optimisation levels also often 
involve undefined behaviour.




Right.. I reduced optimization to O1 with no change, I have strange 
issues compiling with O0!




Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   XUL       0x00010f5468e1 
nsWindowWatcher::OpenWindowInternal(mozIDOMWindowProxy*, char const*, 
char const*, char const*, bool, bool, bool, nsITabParent*, nsIArray*, 
nsIDocShellLoadInfo*, mozIDOMWindowProxy**) + 273


And this is where it happened. Since this is not a full debug build, 
there is no line number information, but you at least know which 
method is doing the bad memory access.




But it should be a debug build. Well a build with debug symbols (not a 
firefox-style debug which adds also a lot of debug code).

I add:
ac_add_options --disable-strip

and this helps on Linux usually.

Still, the nsWindowWatcher class gave me a clue and I found a couple of 
Firefox patches to import which initialized parameters, checked them, 
etc and now the error changed to>


0   XUL       0x0001035f5c44 
JS::Rooted::registerWithRootLists(js::RootLists&) + 20

1   ???       0x7ffeecb477f0 0 + 140732869670896

this is bad, since it is inside the JS engine. Also the JS engine works 
on other system when compiled with modern clang and gcc!


Also here I don't have a class name which maps directly to a file which 
I can easily inspect.


I will try clang 7 & 8, just so.

Riccardo

Re: MacPorts vs. Apple compiler issues, Handle

[Riccardo Mottola via macports-users]

Hi Joshua,

Joshua Root wrote:


Yes, any number of programs have had bugs that only became apparent 
when building with a newer compiler. But that's a very broad category, 
so without knowing the nature of the crash you're seeing, it's 
impossible to say what else might have had a similar problem.

I imagined that, but perhaps somebody experienced like a recurring issue!
On FreeBSD I compile with clang 12 and it works, so they issue could be 
Apple specific, either in the Apple code part or in dependent SDK and 
libraries.


Bugs in clang are not unknown, but far more common is programs relying 
on certain behaviour for operations that have undefined behaviour 
according to the language standard. Or sometimes the layout of memory 
just shifts slightly, causing a previously benign buffer overflow to 
do damage. Sometimes a newer compiler will also default to a newer 
version of the language, so if that's the cause of the differing 
behaviour, you can use -std to change it back.


I did try clang 10 and it compiles, but crashes. So probably it is not a 
compiler bug (although sometimes the remain undetected for years...).


I will do another compilation reducing the optimization level. GCC has 
an issue where beyond gcc6 certain optimizations need to be disabled, or 
AF crashes.


Otherwise, you have to do the hard work of debugging: Look at the 
crash report to see where and how the code is crashing, pay attention 
to compiler warnings, and systematically eliminate possibilities of 
what could be going wrong. Building with clang's sanitizers may be 
helpful, particularly -fsanitize=address and -fsanitize=undefined, 
though in a code base this size I wouldn't be surprised if they also 
detected hundreds of other potential issues.


Indeed, it is a big code base, with hundreds of warnings...

I don't get very smart on the crash report either. Where is the issue? I 
don't see a trace and don't know how to read it. Sorry to admit that!


Process:   arcticfox [93365]
Path: /Users/USER/Documents/*/ArcticFox.app/Contents/MacOS/arcticfox
Identifier:    org.mozilla.arctic fox
Version:   44.0 (4424.3.18)
Code Type: X86-64 (Native)
Parent Process:    Python [93301]
Responsible:   arcticfox [93365]
User ID:   501

Date/Time: 2024-03-18 11:52:05.968 +0100
OS Version:    Mac OS X 10.13.6 (17G14042)
Report Version:    12
Anonymous UUID:    195FD101-66EF-B75D-42D8-012488A629B7


Time Awake Since Boot: 49000 seconds

System Integrity Protection: disabled

Crashed Thread:    0  Dispatch queue: com.apple.main-thread

Exception Type:    EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x7ffe2007
Exception Note:    EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x7ffe2007:
    Stack  7531-75392000 [ 520K] 
rw-/rwx SM=COW  thread 29

-->
    MALLOC_TINY    7ffe25c0-7ffe2600 [ 4096K] 
rw-/rwx SM=PRV


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   XUL       0x00010f5468e1 
nsWindowWatcher::OpenWindowInternal(mozIDOMWindowProxy*, char const*, 
char const*, char const*, bool, bool, bool, nsITabParent*, nsIArray*, 
nsIDocShellLoadInfo*, mozIDOMWindowProxy**) + 273


Thread 1:
0   libsystem_kernel.dylib        0x7fff50c8728a 
__workq_kernreturn + 10
1   libsystem_pthread.dylib       0x7fff50e4e20e 
_pthread_wqthread + 1552

2   libsystem_pthread.dylib       0x7fff50e4dbe9 start_wqthread + 13

Thread 2:
0   libsystem_kernel.dylib        0x7fff50c8728a 
__workq_kernreturn + 10
1   libsystem_pthread.dylib       0x7fff50e4e009 
_pthread_wqthread + 1035

2   libsystem_pthread.dylib       0x7fff50e4dbe9 start_wqthread + 13

Thread 3:
0   libsystem_kernel.dylib        0x7fff50c8728a 
__workq_kernreturn + 10
1   libsystem_pthread.dylib       0x7fff50e4e20e 
_pthread_wqthread + 1552

2   libsystem_pthread.dylib       0x7fff50e4dbe9 start_wqthread + 13

Thread 4:
0   libsystem_kernel.dylib        0x7fff50c8728a 
__workq_kernreturn + 10
1   libsystem_pthread.dylib       0x7fff50e4e20e 
_pthread_wqthread + 1552

2   libsystem_pthread.dylib       0x7fff50e4dbe9 start_wqthread + 13

Thread 5:
0   libsystem_kernel.dylib        0x7fff50c8728a 
__workq_kernreturn + 10
1   libsystem_pthread.dylib       0x7fff50e4e009 
_pthread_wqthread + 1035

2   libsystem_pthread.dylib       0x7fff50e4dbe9 start_wqthread + 13

Thread 6:: Gecko_IOThread
0   libsystem_kernel.dylib        0x7fff50c87bea kevent + 10
1   XUL       0x00010da95bff kq_dispatch + 687

Thread 7:: Socket Thread
0   libsystem_kernel.dylib        0x7fff50c86cf2 __select 

Re: ld: can't write output file for architecture ppc

[raf via macports-users]

On Sun, Mar 17, 2024 at 02:50:37PM +0100, Riccardo Mottola via macports-users 
 wrote:

> Hi Andreas,
> 
> 
> Andreas Falkenhahn wrote:
> >   ld: can't write output file  for architecture ppc
> > 
> > gcc-mp-6 itself apparently is still working. I have compared the object 
> > files generated by it from before and after the attempted MacPorts update 
> > and they're identical but ld seems broken. Is there any way I can get ld 
> > back up and running?
> > 
> > No, I don't have a backup of my old MacPorts installation, another
> > mistake:(
> > 
> > It's really annoying. I really could've sensed that updating a 2017 
> > MacPorts installation on a 20 year old system nobody besides me is still 
> > using would never go through but still I tried... silly, silly me!!
> 
> It is a big jump in updates, but on the other side you are not the only one
> uses. I am using 10.5 on PPC and Intel and other MacPorts users are on PPC
> or other legacy systems, so there is still good effort updating things.
> 
> I have GCC working on my G4. I updated dozen of packages last week.
> 
> I have a couple of "leftovers" I want to report and tackle, some are generic
> to 10.5, some are specific to ppc / gcc, because on Intel the preferred
> compiler is clang.
> 
> > 
> > Any idea how I can get that fixed?
> 
> I would have a look at the linker, binutils and similar.
> Are you on G3/G4 or G5 ?
> 
> does gcc fail when used outside MacPorts or does it always fail?
> 
> Since I have a working gcc, you should be able too.
> 
> Riccardo

I've been told that macports needs to be selfupdated at least annually.
If it's been too long between selfupdates, it can fail (It did for me once
on 10.6.8). You might need to reinstall macports instead of selfupdate.

To any expoerts out there, does that sound helpful?

cheers,
raf

Re: ld: can't write output file for architecture ppc

[Riccardo Mottola via macports-users]

Hi Andreas,


Andreas Falkenhahn wrote:

  ld: can't write output file  for architecture ppc

gcc-mp-6 itself apparently is still working. I have compared the object files 
generated by it from before and after the attempted MacPorts update and they're 
identical but ld seems broken. Is there any way I can get ld back up and 
running?

No, I don't have a backup of my old MacPorts installation, another mistake:(  


It's really annoying. I really could've sensed that updating a 2017 MacPorts 
installation on a 20 year old system nobody besides me is still using would 
never go through but still I tried... silly, silly me!!


It is a big jump in updates, but on the other side you are not the only 
one uses. I am using 10.5 on PPC and Intel and other MacPorts users are 
on PPC or other legacy systems, so there is still good effort updating 
things.


I have GCC working on my G4. I updated dozen of packages last week.

I have a couple of "leftovers" I want to report and tackle, some are 
generic to 10.5, some are specific to ppc / gcc, because on Intel the 
preferred compiler is clang.




Any idea how I can get that fixed?


I would have a look at the linker, binutils and similar.
Are you on G3/G4 or G5 ?

does gcc fail when used outside MacPorts or does it always fail?

Since I have a working gcc, you should be able too.

Riccardo

Re: Missing m4 forcing CLT reinstallation loop

[Dave Allured - NOAA Affiliate via macports-users]

There are multiple tickets on M4.  There is a fix in the works.  Yours
seems like the same thing.  Please see PR
https://github.com/macports/macports-ports/pull/22984 .


On Thu, Mar 14, 2024 at 7:16 PM Larry Stone 
wrote:

> This seems like an Xcode issue more than MacPorts but since MacPorts is
> why I have Xcode and its command line tools installed, I’ll ask here.
>
> I upgraded to Sonoma about three weeks ago. All went well including
> following the MacPorts instructions for major MacOS upgrades. All was
> working fine. At the time, Xcode and CLT was version 15.1 but both have
> been upgraded to 15.3 since then.
>
> Today, for the first time since upgrading to Sonoma, I ran the MacPorts
> update sequence starting with port selfudpate. One of the packages needing
> updating was Postfix which requires local building. The upgrade script
> errored and an error box popped up saying "the m4 command requires the
> command line developer tools.” Uh, they’re installed. Thinking maybe
> something had changed, I let it rerun the CLT installation but per System
> Information, the version was the same. Tried to upgrade Postfix again and
> the same thing.
>
> Looking in the CLT directory, I saw usr/bin/gm4 but not m4. A search
> suggested that gm4 is just m4 with a different name (maybe GNU m4) and to
> link m4 to gm4. I did and Postfix upgraded OK.
>
> So what happened? Built OK three weeks ago with CLT 15.1 but failed today
> with CLT 15.3. Was m4 in 15.1 but is now missing? (Normally, I’d just go to
> the Time Machine disk to take a look but I had to reinitialize it just a
> few days ago due to an error trying to expand the Time Machine partition on
> the disk). Am I OK linking m4 to gm4?
>
> --
> Larry Stone
> lston...@stonejongleux.com
>
>
>
>
>

Re: MacPorts vs. Apple compiler issues, Handle

[Riccardo Mottola via macports-users]

Hi,

Joshua Root wrote:


The version difference is less slight than you might think. Apple 
clang version numbers are unrelated to the version number of the 
llvm.org release they are based on. Apple clang 9.1.0 is closest to 
the clang-5.0 port.


The name collision looks genuine however. I can only assume that 
MacTypes.h is not included or is preprocessed differently based on 
different defines in the other compiler. 


I found a minor patch by Firefox to solve this namespace collision. So 
for whatever reason Apple's did differently, it now compiles on all 
compilers.


However clang9 generates a crashing executable. I tried on both 10.11 
and 10.13.


- Apple clang: works fine
- MacPorts clang 7: compiles & works
- MacPorts clang 9 : compiles but fails

anybody has seen this behaviour in other software, perhaps smaller and 
easier to test than ArcticFox?


Riccardo

Re: MacPorts vs. Apple compiler issues, Handle

[Riccardo Mottola via macports-users]

Hi Joshua,

Joshua Root wrote:

MacPort installs:
$ clang-mp-9.0 --version
clang version 9.0.1

Apple:
$ clang --version
Apple LLVM version 9.1.0 (clang-902.0.39.1)

Is there some Apple "trick" or is it the slight compiler difference in
version?


The version difference is less slight than you might think. Apple 
clang version numbers are unrelated to the version number of the 
llvm.org release they are based on. Apple clang 9.1.0 is closest to 
the clang-5.0 port.

Aha, I supposed that the number in parenthesis would match, but not.
Do you think it make sense for me to try clang5 or clang6?

The name collision looks genuine however. I can only assume that 
MacTypes.h is not included or is preprocessed differently based on 
different defines in the other compiler.


Do you think an issue in MacPorts compiler or a problem with the code? 
On Linux and FreeBSD  ArcticFox compiles with gcc13 and clang10, but 
this is an issue specific to the Mac code path, so not directly comparable.


I checked XPCShellEnvironment.cpp, there is no direct inclusion of 
MacTypes.h


Riccardo

Re: mozjs102

[Dave Allured - NOAA Affiliate via macports-users]

Following Ryan's suggestion, I am working on an update which should remove
the mozjs102 dependency, and enable gjs and glade for Sonoma.  Please try
the portfile from PR https://github.com/macports/macports-ports/pull/22974 .


On Thu, Mar 7, 2024 at 5:22 PM Lukas Oberhuber  wrote:

> i was never able to get gjs to work (at least when included in GIMP. It
> did compile, at least when I last tried (which was at least a year ago).
>
> On Thu, 7 Mar 2024 at 12:23, Ryan Schmidt  wrote:
>
>> On Mar 6, 2024, at 06:13, Gregory Dodwell wrote:
>>
>>
>> 
>> Will there ever be a mozjs102 port for the Sonoma version of MacPorts
>> 2.9.1?
>>
>> I can't install Glade without it. On the MacPorts bugs re mozjs102 page
>> there's a big red 'X' near the Sonoma version.
>>
>> Any plans for an update?
>>
>>
>> Nobody maintains this port. Somebody has to volunteer to investigate and
>> fix the problem. This is the bug report:
>>
>> https://trac.macports.org/ticket/68511
>>
>> mozjs115 does build on Sonoma so perhaps a fix already exists that can be
>> backported to mozjs102.
>>
>> And/or maybe the ports that depend on mozjs102 (currently only gjs and
>> gjs-devel) can switch to mozjs115.
>>
>

Re: mozjs102

[Dave Allured - NOAA Affiliate via macports-users]

On Thu, Mar 7, 2024 at 5:22 PM Lukas Oberhuber  wrote:

> i was never able to get gjs to work (at least when included in GIMP. It
> did compile, at least when I last tried (which was at least a year ago).
>
> On Thu, 7 Mar 2024 at 12:23, Ryan Schmidt  wrote:
>
>> On Mar 6, 2024, at 06:13, Gregory Dodwell wrote:
>>
>>
>> 
>> Will there ever be a mozjs102 port for the Sonoma version of MacPorts
>> 2.9.1?
>>
>> I can't install Glade without it. On the MacPorts bugs re mozjs102 page
>> there's a big red 'X' near the Sonoma version.
>>
>> Any plans for an update?
>>
>>
>> Nobody maintains this port. Somebody has to volunteer to investigate and
>> fix the problem. This is the bug report:
>>
>> https://trac.macports.org/ticket/68511
>>
>> mozjs115 does build on Sonoma so perhaps a fix already exists that can be
>> backported to mozjs102.
>>
>> And/or maybe the ports that depend on mozjs102 (currently only gjs and
>> gjs-devel) can switch to mozjs115.
>>
>>

MacPorts vs. Apple compiler issues, Handle

[Riccardo Mottola via macports-users]

Hi!

I am wondering about differences between Apple clang and MacPorts clang.
I tried to compile ArcticFox on 10.13, but in back compiatibility (10.9 
target on 10.11 SDK got through MacPorts)


Using exactly the same configuration options, MacPort clang 9.0 fails with:

169:29.18 
/Users/multix/code/Arctic-Fox/ipc/testshell/XPCShellEnvironment.cpp:76:13: 
error: reference to 'Handle' is ambiguous

169:29.18 Environment(Handle global)
169:29.18 ^
169:29.18 
/opt/local/Developer/SDKs/MacOSX10.11.sdk/usr/include/MacTypes.h:249:41: 
note: candidate found by name lookup is 'Handle'

169:29.18 typedef Ptr *   Handle;
169:29.18 ^
169:29.18 
/Users/multix/code/Arctic-Fox/obj-x86_64-apple-darwin17.7.0/dist/include/js/RootingAPI.h:381:25: 
note: candidate found by name lookup is 'JS::Handle'

169:29.18 class MOZ_NONHEAP_CLASS Handle : public js::HandleBase
169:29.18 ^
169:29.18 1 error generated.


However using apple's clang, all works fine.

MacPort installs:
$ clang-mp-9.0 --version
clang version 9.0.1

Apple:
$ clang --version
Apple LLVM version 9.1.0 (clang-902.0.39.1)

Is there some Apple "trick" or is it the slight compiler difference in 
version?


Thanks,

Riccardo

Re: I just wanted to upgrade my older MacPorts version

[Riccardo Mottola via macports-users]

Hi,

xmar...@iqf.csic.es wrote:
The “sudo port upgrade outdated” is running, but the question know is, 
how can I run in the future the equivalent to the older “sudo port 
selfupdate”?
I suppose that since you got the repository in git, you just need to do 
a "git pull" to upgrade it and subsequently "sudo port -v sync".


Essentially Step 1 becomes a git pull, Step 2 can be skipped, Step 3 
repeated.


I too have a similar issue, at work I cannot access the web resources, a 
proxy is usually needed. At home though I can use it, so I run 
selfupdate at home or over a mobile connection.


Hope that helps, I did not test it.

Riccardo

force rebuild a port

[Riccardo Mottola via macports-users]

Hi!

suppose I want to rebuild a port, but it has no version update.
1) e.g. rev-upgrade shows it to be rebuild but "port outdated" doesn't 
show it.

2) Or I want to rebuild it with a different compiler.

How can I do? "port upgrade X" will do nothing because X is not outdated.
"port upgrade --force X" will upgrade all dependencies, which is a 
little too much...


1) in my case has issues because it wants to rebuild many packages and 
starts with one that breaks, so it never gets to the next one.
I tried using "-p" but apparently it is not respected for "port -p 
rev-upgrade" and still dies.


Riccardo

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

[Dave Allured - NOAA Affiliate via macports-users]

Thanks Chris, that is good advice.  I forgot about port select.  In my case
I had to resort to a manual workaround for gfortran, because the port
command is disabled on my corporate controlled Mac.


On Mon, Mar 4, 2024 at 4:04 AM Chris Jones  wrote:

>
> You should not sym link manually yourself. That is precisely what `sudo
> port select gcc` is there for 
>
> On 02/03/2024 4:43 am, Dave Allured - NOAA Affiliate via macports-users
> 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  > <mailto:kennethwolc...@gmail.com>> 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
> > mailto:kennethwolc...@gmail.com>> 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
> > mailto:kennethwolc...@gmail.com>> 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
> > <http://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  > <mailto:j...@macports.org>> 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)  > <http://us.navy.mil>
> > <https://lists.macports.org/mailman/listinfo/macports-users
> > <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?

[Dave Allured - NOAA Affiliate via macports-users]

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?

[Eric Gallager via macports-users]

You might need to do `port select gcc` to make one of them the default

On Fri, Mar 1, 2024 at 9:20 PM 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)  wrote:
> >
> > Pretty sure that macports gcc installs gfortran by default, which is a f90 
> > (and 95, and maybe f2003) compiler.
> >
> >
> >
> >
> >
> >

specific port collections for old systems (Leopard, Snow Leopard...)

[Riccardo Mottola via macports-users]

Hi,

I know that the MacPorts "policy" is to provide the same version of all
packages for all operating system versions and then handle differences
of option, variants, patches in the specific portfile. There are some
minor exceptions.
If an old version of a port needs to live on, two ports exist (e.g. all
compiler versions)

Two things can happen though:
1) a port in version X works on the system, but X+1 doesn't work, work
is in progress to make it work, but as-is it fails to compile or run
2) even after long work of 1) a port cannot compile in a newer version
or there is too much work involved

a case of 2) is e.g. MacVim, which is just not available for old system
and is quite convenient. a case of 1) has been Emacs, which now works!

I have a local overlay repository where I "pin" certain packages to a
specific version. For a long time Ken Cunnigham provided those, my work
is much simpler for now, mostly just a temporary "stop-gap" so that the
system can finish upgrading and remains usable.

Is there interest that I share my work?
It may help others and encourage backports, but it also has some drawbacks

1) if not continuously checked, one might stick to an old version, even
if official macports has "fixed" the port. I see no easy fix here,
except for periodically "hiding" a port manually, reindex, try to build
and see
2) it creates a system of dependencies which is different from official.
It may help get things going, but may also complicate debugging of
dependent ports
3) it may cause false bugs, if someone fails a bug and doesn't notice it
is building an "Unofficial" portfile
4) since it is an overlay, it is not a "fork" of the official repository
where one can then easily make pull-requests from


Ken, you stopped doing it: a specific burden?

What do you think about it?

Right now 10.5 has several hiccups, so I am working locally to get at
least to the point where "everything upgrades again".

It could also serve as a playground for e.g. gcc8 or so.

Riccardo

Re: X11 no longer starts - it does again but now some GTk3 apps abort with a BadAccess

[Jeremy Sequoia via macports-users]

Over TCP, you might not be getting DRI and GLX, so that might be forcing GTK 
down some alternative codepath

Sent from my iPhone...

> On Feb 17, 2024, at 03:28, René J.V. Bertin  wrote:
> 
> Well, at 3h this morning I had it mostly working again. I think the order of 
> mishaps was
> 
> 1) me setting PATH in the launchctl environment
> 2) before undoing that (and rebooting), me calling `startx` or running 
> X11.app from a terminal as root with the idea that the IPC error might go 
> away because of that
> 3) me seeing the warnings about .Xauthority and somehow thinking "I don't 
> have that file anyway" rather than checking and discovering it had been 
> "stolen" by root during 2)
> 
> So after fixing 3) and running `xauth -b` for good measure my X11 environment 
> starts again.
> 
> I haven't yet had the chance to check if remote connections work, but local 
> connections via `DISPLAY=hostname:0` do work again (they didn't with my 
> hands-on call to `xinit` without `-auth` file).
> 
> Jeremy pointed out that we need privileged_startx, the launchctl plist I had 
> moved aside for forgotten reasons. So I moved it back and loaded it before 
> launching X11.app after the fixes above.
> 
> Before all this I'd been tinkering with epiphany, the Gnome WebKit browser, 
> so that was the 1st thing I tried to launch from my restored X11 session.
> Boom, BadAccess and abort. `zenity --calendar` and `gtk3-demo-application` 
> also do the same thing.
> 
> Curiously, they do NOT when I run them with `env DISPLAY=Portia.local:0.0 
> foo` .
> 
> Tracing shows the culprit is a call to XCreatePixmap from 
> `gdk_window_set_icon_list`  (GTk 3.24.20).
> 
> Evidently I unloaded that privileged_startx plist, moved it back to its 
> -disabled folder and restarted X11.
> 
> Now, these applications will start OK, but only for a few minutes in (or 
> maybe just starting one triggers a who-knows-what that causes the BadAccess 
> error on subsequent runs).
> 
> Needless to say, this is new.
> 
> Does this ring any bells, an X11 operation that raises a BadAccess when run 
> over the local DISPLAY socket but not when it goes (IIUC!) via the TCP layer?
> 
> Thanks,
> R.

Re: X11 no longer starts

[Jeremy Sequoia via macports-users]

I suggest moving aside all of your shell init scripts (~/.bash_profile et al) 
and seeing if that helps.

Note the privileged startx job is necessary for setting up correct permissions 
on the paths in /tmp and caching fonts.

Sent from my iPhone...

> On Feb 16, 2024, at 13:50, René J.V. Bertin  wrote:
> 
> Hi,
> 
> It seems I've gotten myself into some real trouble, and the problem is I have 
> no idea how/why. Hence the cross-posting...
> 
> I can no longer launch the X11 environment in which I did almost all my work 
> and that's crucial for displaying remote applications.
> 
> The original XQuartz environment has been crashing for me for years now so 
> I've been running the MacPorts xorg-server-devel port (1.20.10) in a build of 
> my own that enables some additional features such as xephyr.
> 
> Yesterday my session started to become instable (nothing to do with X11) 
> after about 65 days of uptime so I quit everything, logged off and rebooted. 
> That's when the problems started, but I think I did something I shouldn't 
> have done before that.
> 
> The X11 application shell launches, but the actual X server doesn't, at least 
> not in my own account.
> 
> After a good while waiting I'm getting this message in the system.log:
> 
> Feb 16 21:43:36 Portia.local org.macosforge.xquartz.X11.stub[2110]: 
> launch_msg("CheckIn") IPC failure: Operation not permitted
>   
>   
> 
> Googling served up someone who got this after setting the PATH in the 
> launchctl environment (~/.MacOSX/environment.plist) and that removing that 
> and rebooting help him.
> It doesn't for me (I tried both removing the PATH specification and restoring 
> the plist from before, rebooting both times).
> 
> Starting from the commandline gives
> ```
> # /opt/local/bin/startx -- /opt/local/bin/Xquartz
> font_cache: Scanning user font directories to generate X11 font caches
>   
> privileged_startx: bootstrap_look_up(org.macports.privileged_startx): Unknown 
> service name   
> font_cache: Updating FC cache 
>
> font_cache: Done  
>
> expr: syntax error
>
> expr: syntax error
>
> expr: syntax error
>
> xauth:  file /Users/bertin/.serverauth.1969 does not exist
>
> 
> xauth:  timeout in locking authority file /Users/bertin/.Xauthority   
>
> 
> No protocol specified
> 
> 
> waiting for X server to begin accepting connections .
> No protocol specified
> 
> ..
> ```
> 
> The "No protocol specified" and ".." lines start about when the X11 
> application opens and are repeated indefinitely until I quit that 
> application. The message about org.macports.privileged_startx is normal: I 
> moved that plist to LaunchDaemons-disabled long ago for reasons I cannot 
> remember but it was clearly not crucial.
> I also moved the org.*.startx.plist files to LaunchAgents-disabled because I 
> don't need on-demand starting of the X11 server and prefer to have a "normal" 
> DISPLAY variable of the ":0" style .
> 
> My .xinitrc generates output, and that isn't being generated anymore. Moving 
> the entire file aside or removing the plist in ~/Library/Preferences don't 
> solve anything either.
> 
> Curiously, when I log in to my fallback admin account the X11 server still 
> starts as it should: without long delays or any other issue. It's of course 
> not set up properly but things seem to work normally otherwise.
> 
> Any idea how to triage this problem, or any suggestions what I could try to 
> unblock this?
> 
> FWIW, I'm still running 10.9.5 .
> 
> Thanks a LOT in advance!
> 
> René

jupyter-notebook and jupyter-lab 3.11 stopped working

[Artemio González López via macports-users]

Both of these python ports stopped working recently (I’m running Sonoma on a 
15” 2021 MacBook Pro). For jupyter-lab, the error I get when I try to run it is:

raceback (most recent call last):
  File "/opt/local/bin/jupyter-lab-3.11", line 33, in 
sys.exit(load_entry_point('jupyterlab==3.0.13', 'console_scripts', 
'jupyter-lab')())
 

  File "/opt/local/bin/jupyter-lab-3.11", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/importlib/metadata/__init__.py",
 line 202, in load
module = import_module(match.group('module'))
 
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/importlib/__init__.py",
 line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1126, in _find_and_load_unlocked
  File "", line 241, in _call_with_frames_removed
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1147, in _find_and_load_unlocked
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyterlab/__init__.py",
 line 7, in 
from .labapp import LabApp
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyterlab/labapp.py",
 line 15, in 
from jupyterlab_server import slugify, WORKSPACE_EXTENSION
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyterlab_server/__init__.py",
 line 4, in 
from .app import LabServerApp
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyterlab_server/app.py",
 line 7, in 
from jupyter_server.extension.application import ExtensionApp, 
ExtensionAppJinjaMixin
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyter_server/extension/application.py",
 line 21, in 
from jupyter_server.serverapp import ServerApp
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyter_server/serverapp.py",
 line 75, in 
from jupyter_server.services.contents.filemanager import 
AsyncFileContentsManager, FileContentsManager
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyter_server/services/contents/filemanager.py",
 line 15, in 
from anyio import run_sync_in_worker_thread
ImportError: cannot import name 'run_sync_in_worker_thread' from 'anyio' 
(/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/anyio/__init__.py)

For jupyter.notebook, the error is the following:

Traceback (most recent call last):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/notebook/traittypes.py",
 line 235, in _resolve_classes
klass = self._resolve_string(klass)
^^^
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/traitlets/traitlets.py",
 line 2015, in _resolve_string
return import_item(string)
   ^^^
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/traitlets/utils/importstring.py",
 line 33, in import_item
module = __import__(package, fromlist=[obj])
 ^^^
ModuleNotFoundError: No module named 'jupyter_server.contents'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/local/bin/jupyter-notebook", line 8, in 
sys.exit(main())
 ^^
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyter_core/application.py",
 line 277, in launch_instance
return super().launch_instance(argv=argv, **kwargs)
   
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/traitlets/config/application.py",
 line 1073, in launch_instance
app = cls.instance(**kwargs)
  ^^
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/traitlets/config/configurable.py",
 line 583, in instance
inst = cls(*args, **kwargs)
   
  File 

Re: Patch for 'skey' package submitted

[Link Dupont via macports-users]

I think you linked to the wrong Trac ticket. The one you’re referring to is 
probably https://trac.macports.org/ticket/69280.

Link

> On Feb 4, 2024, at 18:12, Bill Cole 
>  wrote:
> 
> They 'skey' package is an implementation of the S/Key algorithm derived from 
> OpenBSD code over 20 years ago. It has not been built by the buildbots for 
> any system after darwin19 because all the modern compilers (including Apple 
> Clang called as 'gcc') enforce the C99 ban on implicit declarations.
> 
> There's a patch attached to the Trac ticket at 
> https://trac.macports.org/ticket/69210 which adds the requisite #include 
> statements.
> 
> Sorry for no pull request, but history tells me that putting one together 
> properly takes me (a non-user of git, usually) a solid 10x as long as it 
> should and annoys at least one person (me) and maybe a few more (actual devs 
> seeing my messed-up PR.)
> 
> 
> -- 
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Re: Kdelibs4-4.14.3 update fails

[Eric Gallager via macports-users]

I'm guessing it's most likely 68452: https://trac.macports.org/ticket/68452

On Sun, Jan 28, 2024 at 8:56 PM Stanton Sanderson  wrote:
>
> Latest MacPorts, old MacBook Air (mid 2013, Intel) running OS 11.7.19 (Big 
> Sur)
>
> kdelibs4-4.14.3_111.darwin_20.x86_64.tbz fetches, update reaches around 50%, 
> then fails.
> Log is very large, don’t know what to look for.
>
> If a ticket has been created, I haven’t found it.
>
> Thanks for help or suggestions,
>
> Stan

MacPorts 2.9.0 & Xcode 15 on Ventura

[Sriranga Veeraraghavan via macports-users]

Hi,

My primary Mac is currently running Venture (13.6.3) but I have held off on 
upgrading to Xcode 15 because I recall reading that there were some issues with 
MacPorts and the linker on Xcode 15.  

With the release of MacPorts 2.9.0, does anyone know if these issues have been 
fixed which would make the upgrade to Xcode 15 safe?  I didn’t see anything 
specific in the release notes about this, which is why I’m asking.

TIA,

-ranga

finalize glib2 fix for 10.5 64bit intel

[Riccardo Mottola via macports-users]

Hi,

in reference to bug https://trac.macports.org/ticket/67307

The "fix" current on my system is the one mentioned in comment 33:

needs to be applied also on 10.5, a.k.a. darwin 9. Strictly speaking 
only on 64bit though. I don't know about 64bit PPC. x86 32bit and ppc 
32bit just compile fine.


Is it possible to write a conditional for darwin 9 & 64bit (intel)?



glib2 is a big dependency, getting it smoothed out helps a lot of ports.

Riccardo

clang and PPC? libsdl2 dependencies

[Riccardo Mottola via macports-users]

Hi,

how is the situation of PPC and clang? I tried upgrading 10.5 PPC since 
a long long time, almost a year... not so easy, some hiccups.


The system compiled for almost two days, I think I saw both GCC and 
CLANG compiling... clang, I thought? Then I see this in console :


--->  Cleaning libstdcxx_clang_fix
--->  Removing work directory for libstdcxx_clang_fix
Error: clang-11-bootstrap cannot be installed for the configured 
build_arch 'ppc' because it only supports the arch(s) 'arm64 i386 x86_64'.

Error: Problem while installing clang-11-bootstrap
Error: Follow https://guide.macports.org/#project.tickets if you believe 
there is a bug.



This happened after I issued:
sudo port -v upgrade py39-anytree  py39-beaker  py39-mako 
p5.30-locale-gettext   p5.28-cgi  libsdl2


I see all the ports upgraded fine, but not libsdl2, so I guess somehow 
libsdl triggered in some dependency up to clang :)


What now?

Riccardo

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

[raf via macports-users]

On Sat, Dec 30, 2023 at 06:38:15PM -0800, Kenneth Wolcott 
 wrote:

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

I don't think you need to think about it. Python-based
ports tend to just depend on whatever is macports's
current default python port which gets updated
annually. A handful (38 out of 2261) declare a specific
default python version. When there are no longer any
ports depending on an old version of python, it
probably automatically becomes a candidate for removal
unless it was explicitly requested.

> The same question applies to Perl.

Perl-based ports are slightly different. They tend to
declare a range of perl5 versions that they work with
(usually the four that are supported at any time by
macports).

I think if you regularly selfupdate and upgrade outdated and
reclaim, it'll probably look after itself. At least, that's my
mental model. Corrections are always welcome.

> Thanks,
> Ken Wolcott

cheers,
raf

Re: Questions on postfix

[Horst Simon via macports-users]

I have MacPorts postfix with amavisd new, spamassassin and dovecot successful 
working on macOS Ventura and High Sierra by sending external mail through icloud
and using getmail to fetch mail from icloud, outlook and gmail. I am using 
submission
(port 587) to send mail.
I had to disable the macOS postfix by running “sudo launchctl unload -w 
/System/Library/LaunchDaemons/com.apple.postfix.master.plist”.

Horst

> On 30 Dec 2023, at 07:28, Rainer Müller  wrote:
> On 29/12/2023 15.28, Ubence Quevedo (thatrat) wrote:
>> That’s just it, I am using mail from /opt/local/bin/:
>> uquevedo@ubence-mini-wired ~ % which mail
>> /opt/local/bin/mail
>> 
>> I shouldn’t have to use a specific executable if it’s attaching to a
>> standard port for a running service…?
>> 
>> Unless there’s something configuration wise that I’m not seeing about
>> what port the postfix from MacPorts is doing…?
> 
> mail(1) does not connect to port 25 or 587 by default, if you wanted to
> imply that. Unless you configured it differently, /opt/local/bin/mail
> might probably still use /usr/sbin/sendmail, but I am not sure about that.
> 
> Depending on your macOS version, it already ships with postfix. The
> relevant sockets are already bound by launchd to run the macOS postfix
> installation on-demand. You won't see any running daemon processes as it
> is only activated by launchd on an incoming connection as configured in
> the /System/Library/LaunchDaemons/com.apple.postfix.master.plist file.
> There is no way to get rid of this postfix setup unless you disable
> System Integrity Protection (SIP).
> 
> If your intention is just to set up a relay over an external SMTP
> server, you could just use the macOS provided postfix. I described such
> a setup on my personal blog a while ago with a specific setup that was
> required for macOS 10.12 Sierra, but the general instructions should
> still apply today:
> 
> https://raimue.blog/2018/03/22/postfix-with-relayhost-over-stunnel-on-macos-10-12-sierra/
> 
> Rainer

Re: Questions on postfix

[Horst Simon via macports-users]

You should have only the postfix.log file and don’t worry about the warning not 
owned by postfix on the .turd_postfix file.

I think you use the macOS mail command which will not use macports postfix. 
Check the /opt/local/bin directory for the mail or mailx command, which you 
should use.

instead of just using mail,  use the full path /opt/local/bin/mail or 
/opt/local/bin/mailx.

Horst

> On 29 Dec 2023, at 10:50, Ubence Quevedo (thatrat)  wrote:
> 
> Huh, I’m only getting a /opt/local/var/log/postfix/postfix.log generated:
> uquevedo@ubence-mini-wired ~ % tree /opt/local/var/log
> /opt/local/var/log
> └── postfix
> └── postfix.log
> 
> 2 directories, 1 file
> 
> With the following contents [which I fixed a few things and restarted the 
> service]:
> uquevedo@ubence-mini-wired ~ % cat /opt/local/var/log/postfix/postfix.log
> Dec 28 14:24:27 ubence-mini-wired postfix/postsuper[31269]: warning: bogus 
> file name: maildrop/.turd_postfix
> Dec 28 14:24:27 ubence-mini-wired postfix/postfix-script[31284]: warning: not 
> owned by _postfix: /opt/local/var/lib/postfix/./.turd_postfix
> Dec 28 14:24:27 ubence-mini-wired postfix/postfix-script[31290]: warning: not 
> owned by _postfix: /opt/local/var/spool/postfix/public/.turd_postfix
> Dec 28 14:24:27 ubence-mini-wired postfix/postfix-script[31295]: starting the 
> Postfix mail system
> Dec 28 14:24:27 ubence-mini-wired postfix/master[31297]: daemon started -- 
> version 3.8.3, configuration /opt/local/etc/postfix
> Dec 28 14:26:05 ubence-mini-wired postfix/postfix-script[31400]: stopping the 
> Postfix mail system
> Dec 28 14:26:07 ubence-mini-wired postfix/postsuper[31451]: warning: bogus 
> file name: maildrop/.turd_postfix
> Dec 28 14:26:07 ubence-mini-wired postfix/postfix-script[31471]: warning: not 
> owned by _postfix: /opt/local/var/spool/postfix/public/.turd_postfix
> Dec 28 14:26:07 ubence-mini-wired postfix/postfix-script[31476]: starting the 
> Postfix mail system
> Dec 28 14:26:07 ubence-mini-wired postfix/master[31478]: daemon started -- 
> version 3.8.3, configuration /opt/local/etc/postfix
> Dec 28 14:27:07 ubence-mini-wired postfix/postfix-script[31549]: stopping the 
> Postfix mail system
> Dec 28 14:27:09 ubence-mini-wired postfix/postsuper[31601]: warning: bogus 
> file name: maildrop/.turd_postfix
> Dec 28 14:27:09 ubence-mini-wired postfix/postfix-script[31625]: starting the 
> Postfix mail system
> Dec 28 14:27:09 ubence-mini-wired postfix/master[31627]: daemon started -- 
> version 3.8.3, configuration /opt/local/etc/postfix
> 
> I don’t get anything from running the following command:
> echo "Postfix setting test" | mail -s "Hello Postfix" "that...@gmail.com”
> 
> Should I be getting the send attempt in the above log file?  Or should l be 
> looking somewhere else?
> 
> -Ubence
> 
> On Dec 28, 2023, at 3:26 PM, Horst Simon  wrote:
> 
> You should with this logging you should get the information in your postfix 
> log as in mail.log, this is what I get.
> 
> Sent from my iPhone
> 
>>> On 29 Dec 2023, at 09:36, Ubence Quevedo (thatrat)  
>>> wrote:
>>> 
>> Thanks for pointing that out.  I added that and tweaked the permissions, 
>> and I’m getting some logging about the service starting/stopping, but I’m 
>> not getting the same type of logging I’m expecting from my Linux systems.
>> 
>> I can usually look in /var/log/mail.log on my Ubuntu server to see the 
>> status of the outgoing mail.
>> 
>> Looking further, it looks like it’s related to syslog on that system, which 
>> isn’t quite the same functionality that macOS has.
>> 
>> Any suggestions on how to be able to log the output of mail commands to 
>> postfix similar to how it is done in Linux?
>> 
>> -Ubence
>> 
>> On Dec 28, 2023, at 1:51 PM, Horst Simon  wrote:
>> 
>> I have postfix login to a file enabled as follow:
>> in the main.cf I added:
>> 
>> maillog_file = /opt/local/var/log/postfix/postfix.log
>> 
>> and in the master.cf:
>> 
>> postlog   unix-dgram n  -   n   -   1   postlogd
>> 
>> Make sure the directory /opt/local/var/log/postfix exists and is writeable 
>> vy postfix.
>> 
>> Horst Simon
>> 
>>>> On 29 Dec 2023, at 02:54, Ubence Quevedo (thatrat)  
>>>> wrote:
>>>> 
>>> Hi,
>>> 
>>> I’ve installed postfix and have configured it similarly to how I have it 
>>> configured on some Linux systems using this tutorial 
>>> [https://www.tutorialspoint.com/configure-postfix-with-gmail-on-ubuntu], 
>>> and when I install and configure postfix in macOS [and make some slight 
>>> changes because everything is in /opt/local/etc/postfix], mail is not sent.
>>> 
>>> What bothers me most is that I can’t find the log files for the macports 
>>> version of postfix.
>>> 
>>> Can someone point me in the right direction to where I can find them to see 
>>> why my sending mail isn’t working?
>>> 
>>> I’m sure I’ll have more questions later, but without the logs, I really am 
>>> only guessing as to why this might not be working.
>>> 
>>> -Ubence
>> 
> 

Re: Questions on postfix

[Horst Simon via macports-users]

You should with this logging you should get the information in your postfix log 
as in mail.log, this is what I get.

Sent from my iPhone

> On 29 Dec 2023, at 09:36, Ubence Quevedo (thatrat)  wrote:
> 
> Thanks for pointing that out.  I added that and tweaked the permissions, and 
> I’m getting some logging about the service starting/stopping, but I’m not 
> getting the same type of logging I’m expecting from my Linux systems.
> 
> I can usually look in /var/log/mail.log on my Ubuntu server to see the status 
> of the outgoing mail.
> 
> Looking further, it looks like it’s related to syslog on that system, which 
> isn’t quite the same functionality that macOS has.
> 
> Any suggestions on how to be able to log the output of mail commands to 
> postfix similar to how it is done in Linux?
> 
> -Ubence
> 
> On Dec 28, 2023, at 1:51 PM, Horst Simon  wrote:
> 
> I have postfix login to a file enabled as follow:
> in the main.cf I added:
> 
> maillog_file = /opt/local/var/log/postfix/postfix.log
> 
> and in the master.cf:
> 
> postlog   unix-dgram n  -   n   -   1   postlogd
> 
> Make sure the directory /opt/local/var/log/postfix exists and is writeable vy 
> postfix.
> 
> Horst Simon
> 
>>> On 29 Dec 2023, at 02:54, Ubence Quevedo (thatrat)  
>>> wrote:
>>> 
>> Hi,
>> 
>> I’ve installed postfix and have configured it similarly to how I have it 
>> configured on some Linux systems using this tutorial 
>> [https://www.tutorialspoint.com/configure-postfix-with-gmail-on-ubuntu], and 
>> when I install and configure postfix in macOS [and make some slight changes 
>> because everything is in /opt/local/etc/postfix], mail is not sent.
>> 
>> What bothers me most is that I can’t find the log files for the macports 
>> version of postfix.
>> 
>> Can someone point me in the right direction to where I can find them to see 
>> why my sending mail isn’t working?
>> 
>> I’m sure I’ll have more questions later, but without the logs, I really am 
>> only guessing as to why this might not be working.
>> 
>> -Ubence
> 

Re: Questions on postfix

[Horst Simon via macports-users]

I have postfix login to a file enabled as follow:
in the main.cf I added:

maillog_file = /opt/local/var/log/postfix/postfix.log

and in the master.cf:

postlog   unix-dgram n  -   n   -   1   postlogd

Make sure the directory /opt/local/var/log/postfix exists and is writeable vy 
postfix.

Horst Simon

> On 29 Dec 2023, at 02:54, Ubence Quevedo (thatrat)  wrote:
> 
> Hi,
> 
> I’ve installed postfix and have configured it similarly to how I have it 
> configured on some Linux systems using this tutorial 
> [https://www.tutorialspoint.com/configure-postfix-with-gmail-on-ubuntu], and 
> when I install and configure postfix in macOS [and make some slight changes 
> because everything is in /opt/local/etc/postfix], mail is not sent.
> 
> What bothers me most is that I can’t find the log files for the macports 
> version of postfix.
> 
> Can someone point me in the right direction to where I can find them to see 
> why my sending mail isn’t working?
> 
> I’m sure I’ll have more questions later, but without the logs, I really am 
> only guessing as to why this might not be working.
> 
> -Ubence

Re: How to download builds from macports?

[Dave Allured - NOAA Affiliate via macports-users]

Thanks, Joshua.  Also, Pavel, your project might do better to simply use
standard Macports in sub shells as your Macports library manager, rather
than accessing mirrors directly.  This will take care of many issues for
you, such as updates, dependencies, and mirror changes, as well as what
Joshua mentioned.


On Tue, Dec 26, 2023 at 6:00 PM Joshua Root  wrote:

> Be aware that not all ports are available as binary archives, and some
> ports rely on post-activate code in the Portfile being run in order to
> work properly.
>
> - Josh
>
> PavelTurk wrote:
>
> > Hi Dave,
> >
> > Thank you very much for your answer.
> >
> > Best regards, Pavel
> >
> > On 12/26/23 5:19 PM, Dave Allured - NOAA Affiliate wrote:
> > >/Use one of the several mirror sites for pre-built binary
> > distributions.  Look under section "Archives" here: />/
> https://trac.macports.org/wiki/Mirrors
> > <https://trac.macports.org/wiki/Mirrors> />//>/Because each home page
> is huge, I find it convenient to postfix the
> > package name for use in a browser, e.g.: />/
> http://atl.us.packages.macports.org/ffmpeg/
> > <http://atl.us.packages.macports.org/ffmpeg/> />//>//>/On Tue, Dec 26,
> 2023 at 3:47 AM PavelTurk  > <https://lists.macports.org/mailman/listinfo/macports-users>
> > <mailto:pavelturk2000 at gmail.com
> > <https://lists.macports.org/mailman/listinfo/macports-users>>> wrote:
> />//>/Hi all,
> />//>/We have a Java project that must work on linux, windows, mac. To make 
> project cross-platform
>
> >
> />/we provide jars with shared libraries - so, dll. These libraries are 
> dowloaded with .sh script while
>
> >
> />/jar is built. We have libraries for linux and windows, but mac library is 
> on macports.
>
> >
> />//>/Could anyone say how to donwload build/package, for example, for 
> project `ffmpeg` using curl or wget?
>
> > />/Or what is the link to to it - http/https?/
>

Re: How to download builds from macports?

[Dave Allured - NOAA Affiliate via macports-users]

Use one of the several mirror sites for pre-built binary distributions.
Look under section "Archives" here:
https://trac.macports.org/wiki/Mirrors

Because each home page is huge, I find it convenient to postfix the package
name for use in a browser, e.g.:
http://atl.us.packages.macports.org/ffmpeg/


On Tue, Dec 26, 2023 at 3:47 AM PavelTurk  wrote:

> Hi all,
>
>
> We have a Java project that must work on linux, windows, mac. To make project 
> cross-platform
>
> we provide jars with shared libraries - so, dll. These libraries are 
> dowloaded with .sh script while
>
> jar is built. We have libraries for linux and windows, but mac library is on 
> macports.
>
>
> Could anyone say how to donwload build/package, for example, for project 
> `ffmpeg` using curl or wget?
> Or what is the link to to it - http/https?
>
> Best regards, Pavel
>

Re: Re: pre-build packages for Lion

[Christopher A. Chavez via macports-users]

On 12/10/23 at 2:07 AM, Christopher A. Chavez via macports-users wrote:

> where one of its dependents

I meant to say “one of its dependencies”.

Re: pre-build packages for Lion

[Christopher A. Chavez via macports-users]

On 12/10/23 at 12:47 AM, Werner LEMBERG wrote:

> What are the intervals that pre-build packages for Lion are generated?
> For example, `libpaper` is already available, but `ghostscript` is not


There will not be any prebuilt archives available for ghostscript for any macOS 
version where one of its dependents, e.g. libpaper, is using legacy-support:

> "ghostscript" is not distributable because its license "agpl" conflicts with 
> license "APSL-2" of dependency "legacy-support"

https://build.macports.org/builders/ports-10.7_x86_64-builder/builds/166656/steps/gather-archives/logs/stdio

Re: Help with zef Portfile

[raf via macports-users]

On Mon, Nov 27, 2023 at 06:08:00AM +1100, Joshua Root  wrote:

> raf wrote:
> 
> > I tried just putting "system" before the command but it didn't work.
> > I couldn't find the documentation for tcl's system,
> 
> System isn't a standard Tcl thing, it's provided by MacPorts. It's closely
> analogous to system(3). It takes a single string which is passed to 'sh -c'.

Thanks. I was effectively giving it multiple strings instead of one.

> It's documented in the portfile man page at least. If it's missing
> elsewhere, that's one more thing for the list of documentation improvements
> that are needed.

I looked for it at 
https://guide.macports.org/chunked/reference.tcl-extensions.html
Thanks for the pointer to the portfile manpage.

> >:info:destroot Failed to create directory 
> > '/opt/local/share/perl6/site/short' with mode '0o777': Failed to mkdir: 
> > Operation not permitted
> That path is outside the work path, so it's not permitted to write to it
> except in the activate phase, but apparently something in the port is trying
> to create it during the destroot phase.
> 
> - Josh

Yes. I thought it was odd but assumed it must have been part of
the activation phase (even though it says destroot in the message).

Perhaps it's rakudo itself doing that. But how did I manage to get it
to work at all (before trying install with -vst)? Maybe I had installed
zef earlier manually and the directories were there? Not sure. But I
think I remember seeing that directory in the past but it's gone now.

I'll try to create any missing directories in ${destroot} as part of
post-destroot and see if that helps. Or maybe I can ask on a rakudo
mailing list about what creates these directories.

cheers,
raf

Re: Help with zef Portfile

[raf via macports-users]

On Sat, Nov 25, 2023 at 05:45:35PM +0100, Rainer Müller  
wrote:

> On 25.11.23 16:07, Joshua Root wrote:
> > The default destroot phase builds a string to pass to 'system' by
> > combining destroot.cmd, destroot.args, etc. In this case, it might be
> > easiest to use those for the rakudo command, and create the symlinks in
> > a post-destroot block?
> 
> Also note that all files have to be put into ${destroot} during the
> destroot phase. The files will afterwards be put into an archive from
> this ${destroot} and will only later be moved to the real ${prefix}
> when activating the port.
> 
> When moving these symlink commands to a post-destroot phase, these should 
> look like this:
> 
> post-destroot {
> ln -s "${prefix}/share/perl6/site/bin/zef"   
> "${destroot}${prefix}/bin/zef"
> ln -s "${prefix}/share/perl6/site/bin/zef-m" 
> "${destroot}${prefix}/bin/zef-m"
> }
> 
> Rainer

Thanks. I spotted that mistake too.

cheers,
raf

Re: Help with zef Portfile

[raf via macports-users]

On Sun, Nov 26, 2023 at 02:07:39AM +1100, Joshua Root  wrote:

> raf wrote:
> 
> > The destroot part looks like this:
> > 
> >destroot {
> >"${prefix}/bin/rakudo" -I"${worksrcpath}" bin/zef \
> >--to="inst#${destroot}${prefix}/share/perl6/site" \
> >install "${worksrcpath}"
> > 
> >ln -s "${prefix}/share/perl6/site/bin/zef"   "${prefix}/bin/zef"
> >ln -s "${prefix}/share/perl6/site/bin/zef-m" "${prefix}/bin/zef-m"
> >}
> > 
> > Which results in this error:
> > 
> >:error:destroot Failed to destroot raku-zef: invalid command name 
> > "/opt/local/bin/rakudo"
> >:debug:destroot Error code: NONE
> >:debug:destroot Backtrace: invalid command name "/opt/local/bin/rakudo"
> >:debug:destroot while executing
> >:debug:destroot "$procedure $targetname"
> > 
> > As "${prefix}/bin/rakudo" is valid in test.cmd,
> > why isn't it valid during destroot?
> > And how do I help destroot find it?
> 
> This is really a macports-dev question, so cross-posting this there.
> 
> When you override (e.g. destroot { ... }) or augment (e.g. post-build { ...
> }) a port phase, the code you provide is executed in the Tcl interpreter.
> '${prefix}/bin/rakudo' is indeed not a valid Tcl command. It happens that we
> do define an 'ln' Tcl command that takes args very much like ln(1). If you
> want to execute something in the shell, you have to use the 'system' command
> (or sometimes 'exec' if you want to capture the output.)
> 
> The default destroot phase builds a string to pass to 'system' by combining
> destroot.cmd, destroot.args, etc. In this case, it might be easiest to use
> those for the rakudo command, and create the symlinks in a post-destroot
> block?
> 
> - Josh

Thanks! That's super helpful.

I tried just putting "system" before the command but it didn't work.
I couldn't find the documentation for tcl's system, so I tried using
destroot.cmd "${prefix}/bin/rakudo" ... instead, but it added extra
arguments: install DESTROOT=... which break the command. But erasing
destroot's args, pre_args, and post_args fixed the build.

Then the problem was activating it. It said:

  Error: Failed to activate raku-zef: Image error:
  /opt/local/share/perl6/site/version is being used by the active rakudo port.
  Please deactivate this port first, or use 'port -f activate raku-zef' to
  force the activation.

So I added the removal of that file to post-destroot and now it works!
It installs and avtivates...

However, when I now test with "sudo port install -vst raku-zef", and add the
missing dependencies (curl, git, wget), I get this error:

  :info:destroot Failed to create directory '/opt/local/share/perl6/site/short' 
with mode '0o777': Failed to mkdir: Operation not permitted
  :info:destroot Command failed:  cd 
"/opt/local/var/macports/build/_Users_raf_macports_ports_lang_raku-zef/raku-zef/work/zef-0.21.1"
 && /opt/local/bin/rakudo 
-I"/opt/local/var/macports/build/_Users_raf_macports_ports_lang_raku-zef/raku-zef/work/zef-0.21.1"
 bin/zef 
--to="inst#/opt/local/var/macports/build/_Users_raf_macports_ports_lang_raku-zef/raku-zef/work/destroot/opt/local/share/perl6/site"
 install 
/opt/local/var/macports/build/_Users_raf_macports_ports_lang_raku-zef/raku-zef/work/zef-0.21.1
 
  :info:destroot Exit code: 1

And now, I get the same error without -vst. Wierd, that did work before trying 
-vst.
And port test isn't working anymore either with teh same error.

  $ ls -lasp /opt/local/share/perl6/site
  0 drwxr-xr-x  3 root  wheel   96 26 Nov 11:58 ./
  0 drwxr-xr-x  7 root  admin  224 26 Nov 11:58 ../
  0 -rw-r--r--  1 root  wheel  1 26 Nov 11:57 version

Any idea what's happening? Or what to try next?

I tried uninstalling and reinstalling rakudo just in case it might
help, but it didn't. My current attempt is
https://github.com/macportsraf/raku-zef-portfile

cheers,
raf

PostgeSQL problem

[Bill Hill via macports-users]

Hi,
I've run a MacPorts update, and now postgres is broken.
I did:
  sudo port selfupdate && sudo port upgrade outdated && sudo port -N reclaim
which upgraded about a dozen ports, the only ones of which I remember were:
  exa, py310-mypy and py311-mypy
Now some years old scripts using psql no longer work.
The command that tripped up:
  psql --host=raidbox.lan sen01 senlog -c "SELECT COUNT(*) FROM weather WHERE 
dtstamp>(TIMEZONE('utc', NOW())-'1 hour'::INTERVAL)"
The error:
  psql: error: connection to server at "raidbox.lan", port 5432 failed: FATAL:  
no PostgreSQL user name specified in startup packet
  connection to server at "raidbox.lan", port 5432 failed: FATAL:  no 
PostgreSQL user name specified in startup packet
  psql(31651,0x7ff844dff9c0) malloc: *** error for object 0xab: pointer being 
freed was not allocated
  psql(31651,0x7ff844dff9c0) malloc: *** set a breakpoint in malloc_error_break 
to debug
  Abort trap: 6
I get about the same messages from /opt/local/bin/psql13 and 
/opt/local/bin/psql15 (15 is active)
It isn't a server problem; I can run the query on the server, and on a linux 
box, and on a Debian VM under Parallels.
Also, I tried installing the brew version:
  brew install postgresql@16
And /usr/local/Cellar/postgresql@16/16.1/bin/psql works.
In addition, /opt/local/bin/pgcli gives:
  Illegal instruction: 4
And qt5-psql-plugin @5.15.11_0+postgresql13 and octave-database don't work 
either.
How can I find out what's broken, and how can I fix this?
Thanks.
Bill

Help with zef Portfile

[raf via macports-users]

Hi,

I'm writing a Portfile for raku's module manager, zef (port named raku-zef),
and I'm getting a destroot error I don't understand.

The test part looks like this:

  test.runyes
  test.cmd"${prefix}/bin/rakudo" -I"${worksrcpath}" bin/zef test 
"${worksrcpath}"
  test.target

And it works and the tests pass (Yay!).

The destroot part looks like this:

  destroot {
  "${prefix}/bin/rakudo" -I"${worksrcpath}" bin/zef \
  --to="inst#${destroot}${prefix}/share/perl6/site" \
  install "${worksrcpath}"

  ln -s "${prefix}/share/perl6/site/bin/zef"   "${prefix}/bin/zef"
  ln -s "${prefix}/share/perl6/site/bin/zef-m" "${prefix}/bin/zef-m"
  }

Which results in this error:

  :error:destroot Failed to destroot raku-zef: invalid command name 
"/opt/local/bin/rakudo"
  :debug:destroot Error code: NONE
  :debug:destroot Backtrace: invalid command name "/opt/local/bin/rakudo"
  :debug:destroot while executing
  :debug:destroot "$procedure $targetname"

As "${prefix}/bin/rakudo" is valid in test.cmd,
why isn't it valid during destroot?
And how do I help destroot find it?

If you need to see the whole Portfile, it's at:

  
https://github.com/macportsraf/raku-zef-portfile/blob/main/lang/raku-zef/Portfile

cheers,
raf

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

[raf via macports-users]

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

[raf via macports-users]

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

Apple Silicon Hardware and MacPorts

[Alexander Newman via macports-users]

Hello All,

I hope that this is the right place to ask a few questions about Apple Silicon 
Hardware and MacPorts - I won’t be offended if this post is ignored.

I’ve trawled through the FAQs but can’t find any references to Apple Silicon 
hardware, which I assume is a good thing. I do realise that a number of 
MacPorts ports appear not to be compilable for AS systems, yet.

I currently have a mid-2010 27” i7 iMac (32 MB RAM) that is running Ventura on 
top of OCLP (and doing much better than it did natively running High Sierra 
with the last security updates). I am using this solution until I can figure 
out what Apple Silicon best meets my needs with respect to compiling MacPorts 
ports (I use Inkscape, R and Octave, amongst other things). I should also say 
that an entry-level 2017 21.5” iMac (bottom spec) that one of my family members 
acquired is without doubt the worst computer that I’ve ever used, and that 
includes 8088/6 DOS machines. Nice screen, but a horror to do try and do 
anything on.

I have been waiting for several years to see what I can replace the 27” iMac 
with - the Mac Studio is probably over-powered for my requirements, the Mac 
mini M2 needs an external display (finding a decent quality 27”+ display seems 
to be difficult here were I live, in Australia, and the Apple Studio Display is 
wickedly expensive), and I wasn’t at all sure that the M1 iMac would cut it, 
especially after the experiences with the ghastly 21.5” iMac.

The M3 iMac is out now, which may or may not change things, so I am currently 
pondering whether I should plump for a specced-out M3 iMac now, wait to see 
what sort of mini (M3, M3 Pro?) comes out next year (presumably), or wait for a 
lower-end M3 Max Studio (again, next year, and least preferred option).

Are large-ish MacPorts ports going to compile all right on a 24 MB RAM iMac 
with, say, a 2TB SSD, without the hardware throttling? The same with running R. 
Do many people on this list use AS machines, and what are their experiences and 
advice regarding MacPorts on them? Am I in fact over-thinking it?

Best regards,
Alex.

Re: Quartz variant missing for tk?

[Christopher A. Chavez via macports-users]

 On 11/6/23 at 1:25 PM, Christian Calderon wrote:

> Hello,
> 
> I recently pulled my old G5 out again with a fresh install of Leopard. I 
> remember being able to install the tk port with the +quartz variant. This 
> made using Tkinter in Python a lot nicer. I see on the website that quartz is 
> listed as a variant, but when I run "port info tk" on my machine it is not 
> listed. Did ppc support get dropped?


PowerPC support was dropped a long time ago. tk +quartz (“Tk Aqua”) has 
required macOS 10.6 or later since version 8.5.13, released November 2012.

Re: 503 errors

[Christopher A. Chavez via macports-users]

On 10/27/23 at 5:05 PM, contextnerror wrote:

> Has anyone else been getting a lot of 503 errors lately when installing ports?



https://trac.macports.org/ticket/68563

Clang 17.0.3 fails to build on Sonoma.

[doa via macports-users]

Attachment available until Nov 19, 2023
This port was recently outdated, so this seems rather strange. Attached is the 
log I received.



Thank you.

Diego Vicioso.

Email… viciosodi...@icloud.com
Click to Download
 
main.log
31.6 MB

Re: problem with py311-scipy on M1 MacBook Pro

[Artemio González López via macports-users]

I just realized that my problem could exactly be the one reported in ticket 
#68329 (py311-scipy @1.10.1_0+gfortran+openblas not building on Sonoma apple 
silicon). Indeed, I just spotted the following lines in my main.log:

:info:build ld: duplicate LC_RPATH '/opt/local/lib/libgcc' in 
'/opt/local/lib/libopenblas-r1.dylib'
:info:build clang: error: linker command failed with exit code 1 (use -v to see 
invocation)

Short of waiting for Apple to release XCode 15.1, is there any quick fix for 
this?

Cheers,

Artemio
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature