Re: DMD port
Sounds good! On Mon, Mar 11, 2024 at 7:20 PM P Padil wrote: > > Dmd apparently doesn’t support Apple Silicon compilation, at least that is > what is stated in their compiler docs. I still tried to compile the source > but got an error message that it doesn’t recognize the system. Noted that > gcc and ldc compilers do support Apple arm processor. I’m planning to update > the gcc13 port to add D, and add a new port for ldc compiler (llvm based). > > > On Mar 11, 2024, at 3:10 PM, Kenneth Wolcott > > wrote: > > > > Awesome! Good luck! Looking forward to this... > > > > On Mon, Mar 11, 2024 at 2:38 PM P Padil wrote: > >> > >> The port doesn’t have a maintainer, I’m going to update the port file and > >> submit it to macports via github pull as per the instructions. Since I’m > >> new to portfiles it may take some time... > >> > >>> On Mar 11, 2024, at 12:25 PM, Kenneth Wolcott > >>> wrote: > >>> > >>> Hi All; > >>> > >>> Not only that, but could there be a version for Apple Silicon? I've > >>> been using a Docker container for DMD; not really convenient... > >>> > >>> Thanks, > >>> Ken > >>> > >>> On Mon, Mar 11, 2024 at 11:50 AM P Padil wrote: > > The dmd port is still at version 2.088 while upstream is at 2.107.1. > Any reason it is still stuck at this ancient version? Can it be updated? > > Regards > > >> >
Re: DMD port
Dmd apparently doesn’t support Apple Silicon compilation, at least that is what is stated in their compiler docs. I still tried to compile the source but got an error message that it doesn’t recognize the system. Noted that gcc and ldc compilers do support Apple arm processor. I’m planning to update the gcc13 port to add D, and add a new port for ldc compiler (llvm based). > On Mar 11, 2024, at 3:10 PM, Kenneth Wolcott wrote: > > Awesome! Good luck! Looking forward to this... > > On Mon, Mar 11, 2024 at 2:38 PM P Padil wrote: >> >> The port doesn’t have a maintainer, I’m going to update the port file and >> submit it to macports via github pull as per the instructions. Since I’m >> new to portfiles it may take some time... >> >>> On Mar 11, 2024, at 12:25 PM, Kenneth Wolcott >>> wrote: >>> >>> Hi All; >>> >>> Not only that, but could there be a version for Apple Silicon? I've >>> been using a Docker container for DMD; not really convenient... >>> >>> Thanks, >>> Ken >>> >>> On Mon, Mar 11, 2024 at 11:50 AM P Padil wrote: The dmd port is still at version 2.088 while upstream is at 2.107.1. Any reason it is still stuck at this ancient version? Can it be updated? Regards >>
Re: DMD port
Awesome! Good luck! Looking forward to this... On Mon, Mar 11, 2024 at 2:38 PM P Padil wrote: > > The port doesn’t have a maintainer, I’m going to update the port file and > submit it to macports via github pull as per the instructions. Since I’m new > to portfiles it may take some time... > > > On Mar 11, 2024, at 12:25 PM, Kenneth Wolcott > > wrote: > > > > Hi All; > > > > Not only that, but could there be a version for Apple Silicon? I've > > been using a Docker container for DMD; not really convenient... > > > > Thanks, > > Ken > > > > On Mon, Mar 11, 2024 at 11:50 AM P Padil wrote: > >> > >> The dmd port is still at version 2.088 while upstream is at 2.107.1. Any > >> reason it is still stuck at this ancient version? Can it be updated? > >> > >> Regards > >> >
Re: DMD port
The port doesn’t have a maintainer, I’m going to update the port file and submit it to macports via github pull as per the instructions. Since I’m new to portfiles it may take some time... > On Mar 11, 2024, at 12:25 PM, Kenneth Wolcott > wrote: > > Hi All; > > Not only that, but could there be a version for Apple Silicon? I've > been using a Docker container for DMD; not really convenient... > > Thanks, > Ken > > On Mon, Mar 11, 2024 at 11:50 AM P Padil wrote: >> >> The dmd port is still at version 2.088 while upstream is at 2.107.1. Any >> reason it is still stuck at this ancient version? Can it be updated? >> >> Regards >>
Re: DMD port
Hi All; Not only that, but could there be a version for Apple Silicon? I've been using a Docker container for DMD; not really convenient... Thanks, Ken On Mon, Mar 11, 2024 at 11:50 AM P Padil wrote: > > The dmd port is still at version 2.088 while upstream is at 2.107.1. Any > reason it is still stuck at this ancient version? Can it be updated? > > Regards >
DMD port
The dmd port is still at version 2.088 while upstream is at 2.107.1. Any reason it is still stuck at this ancient version? Can it be updated? Regards
RE: I just wanted to upgrade my older MacPorts version
Thanks a lot for your kind help! _ Dr. Martin Martinez-Ripoll Research Professor Emeritus martin.m.rip...@csic.es xmar...@iqf.csic.es Department of Crystallography & Structural Biology www.xtal.iqf.csic.es www.xtal.iqf.csic.es/Cristalografia/ Telf.: +34 917459550 Consejo Superior de Investigaciones Científicas Spanish National Research Council -Mensaje original- De: macports-users [mailto:macports-users-boun...@lists.macports.org] En nombre de Ryan Schmidt Enviado el: lunes, 11 de marzo de 2024 12:05 Para: Riccardo Mottola CC: macports-users@lists.macports.org Asunto: Re: I just wanted to upgrade my older MacPorts version On Mar 10, 2024, at 05:48, Riccardo Mottola wrote: > > 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". You don't need to run "git pull" manually. "sudo port sync" runs it for you.
Re: I just wanted to upgrade my older MacPorts version
On Mar 10, 2024, at 05:48, Riccardo Mottola wrote: > > 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". You don't need to run "git pull" manually. "sudo port sync" runs it for you.
Re: I just wanted to upgrade my older MacPorts version
On Mar 8, 2024, at 06:58, xmartin wrote: > > In fact, the the problem seems to be the restrictive corporate network. I was > able to run what is said in: > https://trac.macports.org/wiki/howto/SyncingWithGit Ok great. > 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”? Hopefully someday selfupdate can work over https: https://github.com/macports/macports-base/pull/184 Unfortunately for now it only operates over rsync, so if you cannot use rsync on your network then you cannot use selfupdate. You can use "sudo port sync" to update the ports collection periodically and you can subscribe to the macports-announce mailing list to learn when new releases of MacPorts base are made, and then download the installer for that version from our web site.
Re: I just wanted to upgrade my older MacPorts version
On Mar 8, 2024, at 03:18, xmartin wrote: > > 1) You are right. The directory /opt/local/var has always been part of > MacPorts. In fact, I had a backup of the older version and, obviously this > directory was still there… The only important difference is that now this > /var directory contains a new subdirectory (called /macports), and not > existing in the older MacPorts version, that contains the following > subdirectories: > /build /distfiles /home /incoming /logs /registry /sip-workaround > /software /sources > and a file called pingtimes. Most of those subdirectories contain a lot of > directories and files... /opt/local/var/macports has also always existed (well, at least since the project was renamed to MacPorts) but it is usually hidden. If you are now seeing it in the Finder, then I guess the hidden flag has gotten unset somehow. It won't affect MacPorts functionality. You can hide it again if you wish. > 2) After typing "sudo port version” I get the following answer: > [iMac-de-Martin:~] xmartin% sudo port version > Warning: port definitions are more than two weeks old, consider updating them > by running 'port selfupdate'. > Version: 2.9.1 Great, so MacPorts was indeed successfully updated to 2.9.1, but the post-update sync failed to update your ports collection due to your rsync problem.
Re: Building "poppler" failed
On Mar 10, 2024, at 23:08, Dave Horsfall wrote: > > High Sierra 10.13.6 on ancient MBP. > > Doing my weekly "port upgrade outdated", it went belly-up here: > > - > >---> Building poppler >Error: Failed to build poppler: command execution failed This error is tracked here: https://trac.macports.org/ticket/69200 And there is another problem that will prevent poppler from building on macOS < 10.15: https://trac.macports.org/ticket/69455
