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

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

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

Users should not need to do *anything* to get DISPLAY correctly set. Anything you have in your personal environment configuration should be removed. If you aren't getting DISPLAY set with the correct launchd socket by default then you must have something that is interfering with this. On

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

Hi, 'Quartz' has nothing to do with X11, its the primary compositor used by macOS itself to render graphics. I assume you are actually taking about the X11 server, which in MacPorts is provided by the 'xorg-server' port and historically was provided by the 'XQuartz' package. Some basic

Re: ruby-select problem - Sonoma

> On 20 Oct 2023, at 6:13 pm, Bill Cole > wrote: > > On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300) > Chris F > is rumored to have said: > >>> On 20/10/23 11:17 am, Chris Jones wrote: >>> >>>

Re: ruby-select problem - Sonoma

> On 19 Oct 2023, at 10:58 pm, Chris F wrote: > >  > I've just migrated to Sonoma 14.0 via a clean OS install plus Migration > Assistant and I'm now reinstalling my ports one at a time. > > Port ruby31 installed without problems but ruby-select doesn't seem to > work/be effective - after

Re: problem with py311-scipy on M1 MacBook Pro

On 19/10/2023 3:59 pm, Chris Jones wrote: On 19/10/2023 3:09 pm, Artemio González López via macports-users wrote: 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

Re: problem with py311-scipy on M1 MacBook Pro

On 19/10/2023 3:09 pm, Artemio González López via macports-users wrote: 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

Re: gfortran and ifort do not work after upgrading to Sonoma

atform load command found in > '/opt/intel/oneapi/compiler/2022.1.0/mac/bin/intel64/../../compiler/lib/libirc.a[126](ssse3_strncpy.o)', > assuming: macOS > ld: warning: no platform load command found in > '/opt/intel/oneapi/compiler/2022.1.0/mac/bin/intel64/../../compiler/lib/libirc

Re: X11 and grads do not work after upgrading to Sonoma

nks > Tao > > >> On 10/7/23 9:16 AM, Chris Jones wrote: >> Hi, >> >> /usr/local and /usr/X11 are not locations macports will install anything >> into, so you are not using a macports provided build of grads. >> >> You should remove everythin

Re: X11 and grads do not work after upgrading to Sonoma

Hi, /usr/local and /usr/X11 are not locations macports will install anything into, so you are not using a macports provided build of grads. You should remove everything from these locations, and then install instead macports grads port. Also, in order to have a X11 server you should install

Re: Status of Macports on Sonoma?

Hi,On 7 Oct 2023, at 3:40 pm, Murray Eisenberg wrote:OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton wrote:I'm pondering whether I should upgrade to macOS Sonoma now, or continue to wait.  Generally speaking, how well is Macports working on Sonoma?  I have seen a surprising

Re: Status of Macports on Sonoma?

Hi,On 7 Oct 2023, at 1:12 am, Kevin Horton wrote:I'm pondering whether I should upgrade to macOS Sonoma now, or continue to wait.  Generally speaking, how well is Macports working on Sonoma?  I have seen a surprising small number of issues posted on this list, and am wondering whether that is a

Re: work-around for Xcode 15 linker issue?

, Maxim Maxim Abalenkov \\ maxim.abalen...@gmail.com +44 7 486 486 505 \\ www.maxim.abalenkov.uk On 3 Oct 2023, at 21:25, Chris Jones wrote: Hi, Just incase any one else reads this, anything you add to your user profile will nit have any effect on port builds, as these do not run as your user. So

Re: work-around for Xcode 15 linker issue?

Hi,Just incase any one else reads this, anything you add to your user profile will nit have any effect on port builds, as these do not run as your user. So don’t try this expecting it to fix port builds. ChrisOn 2 Oct 2023, at 4:18 pm, Maxim Abalenkov wrote:Hello Murray,How are you? As mentioned

Re: work-around for Xcode 15 linker issue?

On 3 Oct 2023, at 9:03 pm, Murray Eisenberg wrote:Several ports I had been trying tore-ininstall under macOS Sonoma (in order to re-install, finally, maxima and wxMaxima,still seem to be failing configuration, even though I did add the two exports to my ~/.profile (and, of course, after

Re: Unable to build clang-14 under Sonoma

Hi, You haven’t posted enough information for anyone to really help. We need to see the complete log file. However, before that, please first make sure your ports are completely up to date, as some fixes have recently gone in for clang 14 that should have resolved build issues on the new OS.

Re: how do I fix this?

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

Re: Sonoma support?

> On 26 Sep 2023, at 10:18 pm, Chris Jones wrote: > >  > >>> On 26 Sep 2023, at 10:05 pm, Dave Horsfall wrote: >>> >>> On Tue, 26 Sep 2023, Chris Jones wrote: >>> >>> B.t.w. Ryan sent a detailed email on this very point on

Re: Sonoma support?

> On 26 Sep 2023, at 10:05 pm, Dave Horsfall wrote: > > On Tue, 26 Sep 2023, Chris Jones wrote: > >> B.t.w. Ryan sent a detailed email on this very point only last week. >> Please go back read the thread “ Timing of MacPorts Support for New >> macOS Versio

Re: Sonoma support?

B.t.w. Ryan sent a detailed email on this very point only last week. Please go back read the thread “ Timing of MacPorts Support for New macOS Versions” before posting any further follow up questions. > On 26 Sep 2023, at 9:48 pm, Chris Jones wrote: > >  > > >>> On

Re: Sonoma support?

> On 26 Sep 2023, at 9:44 pm, Murray Eisenberg > wrote: > > So I guess my question should be refined to: When might the Sonoma installer > become available? That is indeed an entirely different question. > >>> On Sep 26, 2023, at 4:42 PM, Chris Jones wrote: &g

Re: Sonoma support?

uirement, if you just follow the install from source instructions instead, which frankly are not at all hard to follow. Chris > >> On Sep 26, 2023, at 4:33 PM, Chris Jones wrote: >> >> Hi, >> >> The installers are just there for convenience, they are not

Re: Sonoma support?

Hi, The installers are just there for convenience, they are not a necessity for using MacPorts on any given OS, as you can also just follow the install from source instructions to install and use macports on any OS. These work, for the most part, on any OS release, including the early beta

Re: Exa port dependencies

Hi, I agree they should be the default, ‘by default’, but there are some ports which have a docs variant that drags in minimum build deps and thus having enable by default is probably fine. Anything though that drags in pandoc and the vast array of deps it needs should probably be optional…

Re: MacPorts Update Outdated Choking on libgcc9

Hi, gcc9 is indeed not available on 10.14.6 Uninstall it and libgcc9 > sudo port uninstall libgcc9 gcc9 if that complains because some port still thinks it needs it, then most likely you have that port (or port) installed with a old out of date variant. You will need to reinstall those

Re: Ventura builders

> On 28 Dec 2022, at 3:20 pm, Julien Salort wrote: > > Hello, > > Forgive me if this is documented and I didn't find out. I just updated to > Ventura, and reinstalled MacPorts (as I always do when I upgrade the OS). > > I notice that everything gets compiled from source. > > Is it because

Re: building audacity from source fails

> On 25 Dec 2022, at 1:40 am, Kenneth Wolcott wrote: > > Hi; > > I tried to build audacity from source on my Mac Mini (M1 chip) and it failed. > > Compressed log file attached. https://guide.macports.org/#project.tickets > > Thanks, > Ken Wolcott >

Re: "enscript" no longer working (fwd)

I have no definite suggestions but just looking at https://ports.macports.org/port/enscript/builds/ I see the builds for old OSes are themselves a good few years old now. Its possible I guess something else has updated that broke the port, and perhaps forcing a rebuild from source might

Re: evince post install launch tweaks help needed

> On 19 Dec 2022, at 12:31 pm, chilli.names...@gmail.com wrote: > > oops, probably want to add > > sudo port install xorg-server > > > so, altogether, > > sudo port install xorg xorg-server; sudo port load dbus If all you need is a X server, then installing everything brought in by

Re: ports not working with sudo

selfupdate requires sudo. try sudo /opt/local/bin/port -v selfupdate On 09/12/2022 1:16 pm, Kaustubh Bansal wrote: I get following error $ port Error: Insufficient privileges to write to MacPorts install prefix. On Fri, Dec 9, 2022 at 1:49 PM chilli.names...@gmail.com

Re: Installing Grace on Ventura fails due to llvm-10 configure failure: command execution failed

Hi, Your snippet below indicates that in fact you have not installed all the dependencies of grace, as it is failing in building llvm-10. Please run port rdeps grace To identify which port in the dependency tree of grace is bringing this in. llvm-10 is quite old at this point, and only time

Re: C compiler not found after upgrade to macOS 13.0.1

Looks like your ports are not up to date, please run > sudo port -d sync > sudo port upgrade outdated Then report back. > On 10 Nov 2022, at 7:12 pm, Artemio González López wrote: > >  > >>> On 10 Nov 2022, at 20:05, Chris Jones wrote: >>> >>>

Re: C compiler not found after upgrade to macOS 13.0.1

Does /opt/local/lib/libicui18n.71.dylib Actually exist in your system ? > On 10 Nov 2022, at 7:02 pm, Artemio González López via macports-users > wrote: > >  >> On 10 Nov 2022, at 18:52, Artemio González López wrote: >> >> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port

Re: Emacs.app does not run after upgrade to macOS 13.0.1

Please run > otool -L /opt/local/lib/libxml2.2.dylib and paste the output here, and also for each lib it references check it exists (and recursively check with otool for the libs they use). > On 10 Nov 2022, at 7:00 pm, Artemio González López via macports-users > wrote: > >  > >> On 10

Re: Emacs.app does not run after upgrade to macOS 13.0.1

.dylib is provided by: icuPerhaps the 'icu' port is not properly installed on your system (you can check with 'port installed icu').  Or you may need to rebuild it for MacOS 13.0.1.Best,-rangaOn Nov 10, 2022, at 10:48, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:On 10 Nov 2022, at 6:43 pm, Chris

Re: Emacs.app does not run after upgrade to macOS 13.0.1

> On 10 Nov 2022, at 6:43 pm, Chris Jones wrote: > >  > Hi, > > Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a > coincidence i think you see something relating to this (and you aren’t the > only one), Correction. The other message is als

Re: Emacs.app does not run after upgrade to macOS 13.0.1

Hi, Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a coincidence i think you see something relating to this (and you aren’t the only one), although I cannot say how the OS update could affect macports builds of this library. I do not personally run macOS13 yet so

Re: C compiler not found after upgrade to macOS 13.0.1

> On 10 Nov 2022, at 5:53 pm, Artemio González López via macports-users > wrote: > > After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), Upgrading from what OS ? > port cannot find any C compiler: > > checking for gcc... /opt/local/bin/clang-mp-14 > checking whether the C compiler

Re: how to move "Python Launcher" away from /Application folder?

May I ask, what exactly is your problem with having the Apps installed by MacPorts under /Applications/MacPorts ? I am not really sure I see what the problem is you are trying to fix. Chris On 09/11/2022 11:57 pm, supervisitor via macports-users wrote: ... ups, this I have probably

Re: Texmaker installation failed due to inability to build qt5 web engine

Apart from the glacial place of OS update migration (*every *app and dependency  is downloaded and built from source), Just on this point, if you don't want to have to build everything from source, then you should not update your OS before MacPorts has deployed buildbots for the new OS.

Re: Questions on migration to macOS Ventura

> On 25 Oct 2022, at 7:15 pm, Artemio González López wrote: > >  >> On 25 Oct 2022, at 20:09, Chris Jones wrote: >> >> Hi, >> >> Theres no reason to wait for an official installer, the build from source >> route works just fine, and

Re: Questions on migration to macOS Ventura

Hi, Theres no reason to wait for an official installer, the build from source route works just fine, and once complete gives you functionally as good a macports installation as the installer does. If you go this route, there is also no need to reinstall once the official installer is out.

Re: Guile-2.2.7

What you report makes no sense, as openssl3 does not depend at all on guile. If you have a problem, with either guile or openssl3 you should first search for an existing trac ticket for the port you have having issues with, and if that does not exist submit one.

Re: port history

On 26/09/2022 4:21 pm, Ralph Seichter via macports-users wrote: * Chris Jones: Cloning is not not necessary for this. Just use the web interface to navigate to the port of interest and then Examine the history for that file. Your assumption that the WebUI offers sufficient means

Re: port history

> On 25 Sep 2022, at 9:10 pm, Ralph Seichter via macports-users > wrote: > > * chilli: > >> Is it possible to see the version history of a port? > > You can clone the publicly available MacPorts Git repository from > g...@github.com:macports/macports-ports.git and then use 'git log ...' >

Re: Cannot build DOSBOX

> On 19 Sep 2022, at 5:40 am, Dave Horsfall wrote: > > Sigh; it never rains but it pours... > > Trying to build DOSBOX I get: > >---> Computing dependencies for dosbox >Error: Cannot install dosbox for the arch 'i386' because >Error: its dependency libsdl does not build for

Re: Unable to build XV

> On 19 Sep 2022, at 4:21 am, Bill Cole > wrote: > > On 2022-09-18 at 21:33:32 UTC-0400 (Mon, 19 Sep 2022 11:33:32 +1000 (EST)) > Dave Horsfall > is rumored to have said: > >> And because XV is broken I can't continue with upgrading following ports > > You can get around that by

Re: Unable to build XV

jasper was recently updated to provide version 3.x, previously it was 2.x A new port jasper2 was made providing the older version, and ports like xv updated to use it. Unfortunately though it appears if you attempt to build xv whilst having the newer jasper port installed it

Re: missing pre-compiled packages

Hi, Binaries aren’t available if the licenses of the port, and its dependencies, do not allow it. To check if this is the case you should refer to the build logs which you can find from the ports site. E.g. https://ports.macports.org/port/git Then check the builds tab. Pick one, and then

Re: Problem with rsync.macports.org mirror?

> On 31 Jul 2022, at 9:05 am, Gerben Wierda via macports-users > wrote: > >  > gerben@hermione macports-ports % sudo port -v selfupdate > ---> Updating MacPorts base sources using rsync > > Willkommen auf dem RSYNC-server auf ftp.fau.de. > Nicht all unsere Mirror sind per rsync verfuegbar.

Re: Has anyone been using Monterey 12.5 yet?

Yes, using it just fine for a short whole now… > On 31 Jul 2022, at 10:09 am, Gerben Wierda via macports-users > wrote: > > Has anyone been using Monterey 12.5 yet? > > Gerben Wierda (LinkedIn) > R IT Strategy (main site) > Book: Chess and the Art of Enterprise Architecture > Book: Mastering

Re: problem compiling libzzip (PPC, Sorbet Leopard)

On 27/07/2022 8:52 pm, Hangglider wrote: MacOSX 10.5.9, http://macintoshgarden.org/forum/introducing-sorbet-leopard-105-reinvigorated http://macintoshgarden.org/apps/sorbet-leopard So an unofficial OS. We don't really support those... On 27.07.22 20:55, Chris Jones wrote: Btw. What

Re: problem compiling libzzip (PPC, Sorbet Leopard)

> On 27 Jul 2022, at 7:54 pm, Chris Jones wrote: > >  > >> On 27 Jul 2022, at 7:29 pm, Hangglider wrote: >> >> Hello, >> >> somewhere in the dependencies for some package I have to compile >> libzzip. That's less easy than it sounds: >

Re: problem compiling libzzip (PPC, Sorbet Leopard)

Btw. What the heck is ‘sorbet Leopard’ ?? > On 27 Jul 2022, at 7:29 pm, Hangglider wrote: > > Hello, > > somewhere in the dependencies for some package I have to compile > libzzip. That's less easy than it sounds: > > The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 >

Re: problem compiling libzzip (PPC, Sorbet Leopard)

> On 27 Jul 2022, at 7:29 pm, Hangglider wrote: > > Hello, > > somewhere in the dependencies for some package I have to compile > libzzip. That's less easy than it sounds: > > The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 > and

Re: Why so many gcc updates in the last week or so?

Gcc12 brought a number of issues, that took time to be solved and required a number of updates in other gcc versions as well, and only became apparent as users submitted tickets etc. for those issues as they where found. I apologies for the number of updates, but I think now, touch wood,

Re: NCEPLIB in Mac

ave to build it by myself if Macport does not have these package. > Thanks > Tao > >> On 7/7/22 4:33 PM, Chris Jones wrote: >> >> Well, if those static libraries are not even built for macOS….. they are >> never going to work on a mac. >> >> You need to either

Re: NCEPLIB in Mac

. I download those *.a from other platform, not from Mac. > Gfortran works fine in my Mac if I do not call those *.a in a code. > > https://github.com/NOAA-EMC/NCEPLIBS does not mention which platform the > libs support. > > Thanks > Tao > > >> On 7/7/22

Re: NCEPLIB in Mac

These are really questions not for macports, but for the maintainers of the static libs, which I presume you downloaded in binary form from somewhere? The first question is what platforms do the libs support ? 64 or 32 bit, etc… Gfortran from macports works fine. This part is not your problem…

Re: NCEPLIB in Mac

The instructions given below are i think quite clear, just follow them… > sudo port -f deactivate libunwind-headers Then try again. > On 7 Jul 2022, at 11:11 pm, Tao Zhang wrote: > > Hi, > > > When I install wgrib2 into my Macbook pro (10.14.6), I get the following > error. > Does

Re: not seen the 404 before

On 05/05/2022 4:51 pm, chilli.names...@gmail.com wrote: I can't upgrade because of 404? Is this a problem on my end? Most probably yes. Update built just fine here. Check your local network / firewall. ---> Computing dependencies for curl-ca-bundle. ---> Fetching distfiles for

Re: During Migration to Arm64 mac, should I null out archs='x86_64' from installed ports list?

Hi, Speaking only for myself, I generally suggest *not* using the restore_ports.tcl script. When I migrate to a new OS I generate the list of installed ports *and* requested ones, and follow the instructions as far as wi[ping out my old ports prior to the update. However, when restoring the

Re: libusb-devel port

not new enough ? Chris > > Do the pkgconfig .pc files play a role in the installation mechanism? > > — > Christoph > >> Am 05.04.2022 um 15:36 schrieb Chris Jones : >> >> >>> On 05/04/2022 1:54 pm, Christoph Kukulies wrote: >>> Thanks. None

Re: libusb-devel port

without affecting the default X port. If you want a different version than libusb-devel currently provides, then you need to update the port to provide this. Btw, what is the correspondent to ldd under macOS? otool -L — Christoph Am 05.04.2022 um 12:56 schrieb Chris Jones

Re: libusb-devel port

On 05/04/2022 11:50 am, Christoph Kukulies wrote: $ sudo port deactivate libusb @1.0.25_0 Password: Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break:  libusb-compat @0.1.7_0  openocd @0.11.0_0  

Re: libusb-devel port

On 05/04/2022 11:33 am, Christoph Kukulies wrote: I’m in the need of testing a libusb issue with an intermediate build of libusb (1.0.26-rc1, that is) Since I’m always reluctant of mixing brew and macports - is that actually „dangerous“ or impossible at all, should that be avoided or can

Re: port diagnose and xcode

On 11/03/2022 8:02 am, Michele Venturi wrote: What is wrong is that a simple package manager requires an entire multigigabyte professional IDE; I have even taken the time to talk to them about it and file a bug about it,but they clearly don't care... It's surely not a new issue,it's like that

Re: MacPorts XCode Installation

kets from there. On Mar 7, 2022, at 10:22 AM, Michele Venturi mailto:dard...@gmail.com>> wrote: Should I submit a bug report before we even know if it's a MacPorts specific issue? Or how do we find that out? Il lun 7 mar 2022, 16:47 Chris Jones mailto:jon...@hep.phy.cam.ac.

Re: MacPorts XCode Installation

On 07/03/2022 3:31 pm, Michele Venturi wrote: I have the required libraries in /usr/lib/swift too,but MPV is looking for them in /opt/local/lib,so it doesn't find them: otool -l $(which mpv) ... cmd LC_RPATH cmdsize 32 path /opt/local/lib (offset 12) Should we change RPATH or add symbolic

Re: Is this git handling of a problem on my macports-ports fork OK?

> git pull --rebase --autostash origin master works pretty much just fine 99.9% of the time. cheers Chris * Its actually what 'port sync' does under the hood, if you have configured macports to work directly off a git checkout of the ports tree, instead of the dfault rsync tarball ** the

Re: certificate update for old Macs

In my opinion the best way to keep older hardware secure and useful past the point the max macOS version they can run is long since obsolete, is to stop using those OSes and install an alternative. There are, e.g. plenty of linux distros out there and offer a modern, maintained, OS and run

Re: ffmpeg unexpectedly uninstalled

> On 3 Jan 2022, at 11:54 pm, Michael Newman via macports-users > wrote: > > When I periodically update MacPorts I also run: > > sudo port -f uninstall inactive Why are you using the -f option here. That could force something to happen that might not be a good idea. Generally speaking

Re: [numpy @ bigsur: multithreading]

> On 3 Jan 2022, at 5:18 pm, Maxim Abalenkov wrote: > > Dear all, > > Thank you for all of your replies and suggestions! I have written my own > matrix multiplication script in order to test NumPy’s performance. Please > find it attached. I’m using the MKL variant of NumPy. Strangely

Re: Can some ports install config files inside '/usr/local/etc'?

Nothing in macports will be installing to /usr/local. If you have anything in that area it has been put there by some other means. Maybe homebrew?, but also a number of third party installers sometimes use this directory as well (which are the reasons why MacPorts specifically ignores this

Re: python ports depend on openssl not in index

ad is you did not pay enough attention to it in the first case ;) Chris > > ‐‐‐ Original Message ‐‐‐ > >> On Friday, December 10th, 2021 at 2:21 PM, Chris Jones >> wrote: >> >> Hi, >> >> Yes, the error is expected. What i am asking is if you get any

Re: python ports depend on openssl not in index

Migration Guide suggested a manual update (i.e. reinstall) which I >>> believe got me going again. Thanks guys! ~SeaQuench >>> >>> ‐‐‐ Original Message ‐‐‐ >>> >>>> On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt >>>&g

Re: python ports depend on openssl not in index

, Chris! > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ >> On Thursday, December 9th, 2021 at 2:47 PM, Chris Jones >> wrote: >> >> >> >> Did you follow the migration guide when moving to a new major os version ? >

Re: python ports depend on openssl not in index

Did you follow the migration guide when moving to a new major os version ? https://trac.macports.org/wiki/Migration If not, follow it now, to wipe out your ports and reinstall them correctly for the new os. If you did, your ports tree seems to be very out of date. Then try, > sudo port

Re: is macports getting rusty?

themselves will also have the problem. On Nov 29, 2021, at 09:15, Bill Cole <mailto:macportsusers-20171...@billmail.scconsult.com>> wrote: On 2021-11-29 at 08:32:46 UTC-0500 (Mon, 29 Nov 2021 13:32:46 +0000) Chris Jones mailto:jon...@hep.phy.cam.ac.uk>> is rumored to have said: If yo

Re: is macports getting rusty?

Give the developers of rust itself a piece of your mind if you like, over how slow it is to compile. Good luck with that - I suspect to be THAT slow (although really? compiling a C compiler suite plus library isn't exactly fast either) they might be doing some things by brute force that

Re: Does MacPorts depend on Spotlight?

is only 35GiB - and I frequently remove most inactive ports and run a port clean installed) and active in terms of changes. On Nov 16, 2021, at 16:06, Chris Jones <mailto:jon...@hep.phy.cam.ac.uk>> wrote: I am not aware of any use macports itself makes of spotlight, so for sure if

Re: Does MacPorts depend on Spotlight?

I am not aware of any use macports itself makes of spotlight, so for sure if you don’t plan on using it yourself to search the install prefix, you can disable it. > On 16 Nov 2021, at 6:26 am, Richard L. Hamilton wrote: > > Seems it'd thrash Spotlight a lot less during "port selfupdate" or

Re: xorg-server

> On 12 Nov 2021, at 6:59 pm, Tom wrote: > >  >> >>> Hi, >>> >>> when trying to run an X11 program, I get the following error message: >>> >>> (putty:8198): Gtk-WARNING **: 00:06:49.190: cannot open display: :0 >>> >>> How can I fix that? >> >> Assuming you are running Mac OS X 10.5 or

Re: provide latest OS root certificates via port?

I have always favoured VMWare over parallels myself, and they now offer a free license for non-commerical usages. https://customerconnect.vmware.com/web/vmware/evalcenter?p=fusion-player-personal > On 31 Oct 2021, at 12:07 pm, Richard L. Hamilton wrote: > > Years ago, creating a (then OS X,

Re: Does MacPorts need ALL of Xcode?

> On 27 Sep 2021, at 10:36 pm, Ian Wadham wrote: > > Hello Chris, > >> On 27 Sep 2021, at 8:42 am, Chris Jones wrote: >> The majority of ports will indeed build fine with just the CLT installed. > > So what is the “recipe” to install just the CLT with

Re: Does MacPorts need ALL of Xcode?

The majority of ports will indeed build fine with just the CLT installed. There are a number though where the build does indeed require a complete Xcode installation, which is why the baseline recommendation is to install Xcode. However if you are ok with perhaps running into the occasional

Re: code::blocks and X11 via MacPorts: is this as it is supposed to be?

sudo port install xorg-server Logout and back in again > On 12 Sep 2021, at 11:17 am, Gerben Wierda via macports-users > wrote: > > I’ve been trying out code::blocks and X11 installed via MacPorts and I’m > under the impression something is missing. > > I installed using > > sudo port

Re: cdrtools streamripper

> On 10 Jun 2021, at 9:05 am, Giuseppe Di Matteo > wrote: > > I opened ticket #63062. > What about streamripper. Configure failed for libmad. (Big Sur arm64) Same. Check for and if need be open tickets against failing ports. > > Pino Di Matteo > pinodimat...@me.com > > > >> Le 9 juin

Re: MacPorts 2.7.0 has been released

See `config.log' for more details We need to see what is in this file… (from the messages you posted below). Chris > On 19 May 2021, at 3:06 pm, Bjarne D Mathiesen > wrote: > > OK - > > on 10.6.8 I get : > > #=> ls -l /usr/bin/cc > lrwxr-xr-x 1 root wheel 32 4 Jan 14:50 /usr/bin/cc ->

Re: port update outdated 'Failed to archivefetch aom: version @3.1.0_0'

Error: Follow https://guide.macports.org/#project.tickets to report a bug. Please follow the instructions you were given above to either open a ticket or see if one for this issue already exists. > On 12 May 2021, at 8:25 pm, tom eee wrote: > > Error: Follow

Re: OpenMPI Users - Is Anyone Using openmpi-clang33 or openmpi-clang34?

lang10 around for arm until we can migrate the above to clang11. Cheers Chris > > K > > > >> On May 7, 2021, at 12:22 PM, Chris Jones wrote: >> >> Hi, >> >> Another clean up suggestion is to remove all clangs apart from 11+ for >> macOS11

Re: OpenMPI Users - Is Anyone Using openmpi-clang33 or openmpi-clang34?

Hi, Another clean up suggestion is to remove all clangs apart from 11+ for macOS11(arm). I just noticed the buildbots building the clang-9.0 version for arm, but its worth noting that clang 9.0 and 10 are not reliable for arm, I have seen them generate bad code, fail with ICEs, so really there

Re: OpenMPI Users - Is Anyone Using openmpi-clang33 or openmpi-clang34?

Hi, I would suggest maybe its worth pruning the gcc list a bit as well ? I believe e.g. gcc7 at least works all the way down to 10.5, perhaps even older ? Do we still need gcc 5, 6? Chris > On 7 May 2021, at 1:35 pm, Christopher Nielsen > wrote: > > Folks, > > We’re considering

Re: Is it possible to install Julia on M1 Mac?

Hi, Whilst the statement that the devel version of gcc was correct at the time it was made, gcc10 now has had support back ported. So I suggest you force uninstall libgcc-devel and let libgcc10 get installed in its place. Chris > On 7 May 2021, at 12:37 pm, Andrew Rohl wrote: > > I have

Re: Installing universal binaries on Apple M1 using macports

Hi, Llvm/clang 10 does not work reliably on apple silicon. use llvm/clang 11 instead. Chris > On 30 Mar 2021, at 7:19 am, Sandeep Thakkar > wrote: > >  > Hi, > > I'm installing llvm-10 on Apple M1 (macOS BigSur) with these changes in > macports.conf: > > # custom changes >

Re: gfortran for M1?

Hi, Gcc-devel provides gfortran for M1 machines by default. Chris > On 20 Mar 2021, at 1:01 pm, petr.2...@centrum.cz wrote: > > Is it already possible to install gfortran on M1? > It seems that gcc-devel does not have +gfortran variant and and other gcc > versions are not compatible. >

Re: OS Platform mismatch - while installing stm32flash

se errors messages. Chris > > Jim > 3222 NE 89th St > Seattle, WA 98115 > (206) 430-0109 > >> On Mar 11, 2021, at 6:44 AM, Chris Jones wrote: >> >> Hi, >> >> Looks like at some point you did not follow the migration instructions >> correctly

Re: OS Platform mismatch - while installing stm32flash

Hi, Looks like at some point you did not follow the migration instructions correctly. You should do so now. Chris > On 11 Mar 2021, at 2:41 pm, Christoph P.U. Kukulies wrote: > > Of course the error (OS platform mismatch) occurs on every command I'm > running on port, > > like > > port

Re: Warning: cltversion again

Hi, > On 7 Mar 2021, at 6:18 pm, Fielding, Eric J (US 329A) via macports-users > wrote: > >  > I am getting this warning again from running ‘port upgrade outdated’: > > Warning: cltversion: The Command Line Tools are installed, but MacPorts > cannot determine the version. > Warning:

Re: stdlib.h compilation error for macports gcc9.

e0fe9cd9377caa0fee122dd387a >>> In file included from >>> /opt/local/include/gcc9/c++/ext/string_conversions.h:41, >>> from /opt/local/include/gcc9/c++/bits/basic_string.h:6493, >>> from /opt/local/include/gcc9/c++/string

  1   2   3   4   >