Re: boost176 + py311 vs +py312

Forcing things is never really the best way to go. In this case vigra just needs to have py312 support added. https://github.com/macports/macports-ports/pull/22655 Chris > On 12 Feb 2024, at 6:42 pm, Lenore Horner wrote: > > I'd like to have both TexLive and Hugin-app installed. However,

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

> On 1 Dec 2023, at 6:52 am, Kenneth Wolcott wrote: > > Hi; > > So what is the proper way for X to be started? If properly configured the X11 server will automatically start on demand. You really should never need to manually start it. > > Do I need to manually create a launch entry

Re: Clang 17.0.3 fails to build on Sonoma.

Sending a 31MB log to a mailing list is not a great idea.. Please open a trac ticket. https://trac.macports.org/ Chris > On 20 Oct 2023, at 10:11 pm, doa via macports-users > wrote: > > This port was recently outdated, so this seems rather strange. Attached is > the log I received. > >

Re: problem with py311-scipy on M1 MacBook Pro

Oct 2023, at 5:04 pm, Frank Schima wrote: > > Correct. I installed the beta CLT (as I mentioned). > > No joy. boost176 does not build. > > >> On Oct 20, 2023, at 2:26 AM, Christopher Jones >> wrote: >> >> >> Do you also have CLT installed and

Re: problem with py311-scipy on M1 MacBook Pro

iated CLT. I can only hope I’m doing something wrong. > > I cannot even get past boost176 which is required. I modified my local > Portfile to use boost181 (which does build) but py311-scipy still does not > build. > > > >> On Oct 19, 2023, at 1:11 PM, Chris

Re: problem with py311-scipy on M1 MacBook Pro

The fix is in Xcode 15.1, not 15.0.1 Chris > On 19 Oct 2023, at 5:27 pm, Jim Secan wrote: > > I see that there’s an Xcode 15.0.1 released yesterday. Anyone tried that? > > Jim > Seattle, WA > >> On 10/19/2023, at 8:00 AM, Chris Jones wrote: >> >> >> >> On 19/10/2023 3:59 pm, Chris Jones

Re: Help me understand dependents of libgcc-devel vs gcc13?

> > Clever! > > One question of mine which did not get answered: "Q: why are ports like > fftw-3 reported as dependents of port libgcc-devel? I don't see anything in > fftw-3's portfile[2] which mentions port libgcc-devel, or indeed any gcc or > libgcc, are dependencies. > > "I suspect

Re: Segfault 11 of sshfs

> On 14 Oct 2023, at 10:39 am, Christoph Kukulies via macports-users > wrote: > > Trying to use sshfs under BigSur and errouneously typing an imcomplete > command: > > $ sshfs foobar.de :/home/foo > Segmentation fault: 11 > $ > > leads to a Segmentation fault: 11. > >

Re: Xcode 15 issues - my temporary workaround

Hi, Thanks. We will need to see how widespread problems are due to this, but we might need to. at least temporarily, set this as the default in some central place if it ends up affecting a lot of ports. Just to note, a potentially more convenient way to force the legacy linker is via the

Re: g++ errors after upgrading XCode Command Line tools to version 15.0.0.0.1.1694021235

> > Workaround, for now, is to not use gcc to build C++ sources. Clang is anyway > the default compiler on Mac’s, and is what MacPorts uses for the vast > majority of ports, so if you can use clang++ (either Xcode or MacPorts own > builds). Both these are still fine. Or, of course,

Re: g++ errors after upgrading XCode Command Line tools to version 15.0.0.0.1.1694021235

> On 22 Sep 2023, at 1:27 pm, Christopher Jones > wrote: > > > >> On 22 Sep 2023, at 1:09 pm, Carlo Tambuatco wrote: >> >> macOS 13.5.2 >> package-id: com.apple.pkg.CLTools_Executables >> version: 15.0.0.0.1.1694021235 >> >> My g+

Re: g++ errors after upgrading XCode Command Line tools to version 15.0.0.0.1.1694021235

> On 22 Sep 2023, at 1:09 pm, Carlo Tambuatco wrote: > > macOS 13.5.2 > package-id: com.apple.pkg.CLTools_Executables > version: 15.0.0.0.1.1694021235 > > My g++-mp-12 (from gcc version 12) install on macports started giving me > these errors compiling > C++ programs after upgrading my

Re: ports that are outdated but cannot be upgraded.

iants (which the commands you where given do not) or if you are using a non-default installation prefix. Chris > > Thanks, > Ken > > On Wed, Mar 29, 2023 at 10:12 AM Bill Cole > wrote: >> >> On 2023-03-29 at 07:49:28 UTC-0400 (Wed, 29 Mar 2023 12:49:28 +0100) >&g

Re: ports that are outdated but cannot be upgraded.

Hio, Your problem is precisely what it says at the end > Error: Failed to configure libtorrent-rasterbar: boost176 must be > installed with +python311. you will likely have it installed with a different python version selected, and port respects this as your ‘choice’. You need to uninstall

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

ote: > > Please see the attached transcript. > > > > > On Nov 16, 2022, at 6:00 AM, Christopher Jones > > wrote: > > > > CAUTION: The Sender of this email is not from within Dalhousie. > > > > There is no indication below as to why your system

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

There is no indication below as to why your system is trying to build llvm-10 as part of installing grace, it does not appear in the dips tree please run sudo port clean grace sudo port -d configure grace and post the complete transcript of what you get back. > On 16 Nov 2022, at 9:53 am,

Re: Library Problem

https://trac.macports.org/ticket/65503#ticket > On 18 Jul 2022, at 9:53 am, Christopher Jones > wrote: > > > Actually, there might be something I can do to address this, more in a bit... > >> On 18 Jul 2022, at 9:22 am, Christopher Jones >> wrote: >> &g

Re: Library Problem

Actually, there might be something I can do to address this, more in a bit... > On 18 Jul 2022, at 9:22 am, Christopher Jones > wrote: > > Hi, > > No, you need to recompile everything… > > Chris > >> On 17 Jul 2022, at 10:31 pm, Jim Secan wrote: >> &

Re: Library Problem

Hi, No, you need to recompile everything… Chris > On 17 Jul 2022, at 10:31 pm, Jim Secan wrote: > > I’m a gfortran user and by no stretch of the imagination a guru on how the > gcc compilers are rigged up. I just recently did a full update of my > MacPorts codes, after which I get the

Re: Uninstalling MacPorts on Mac M1 Chip

ote: > > Hi Chris! > > Thanks for your email. > Unfortunately, when I try 2.4.2 or 2.4.3, I get the same output: “-bash: $: > command not found” > > Lisa > > From: Christopher Jones > Date: Wednesday, January 12, 2022 at 10:49 AM > To: Lisa Kim > Cc: macpor

Re: Uninstalling MacPorts on Mac M1 Chip

Sorry, read your post again… If the port command is not working for you, then just skip that command. go on with 2.4.2 and 2.4.3 Chris > On 12 Jan 2022, at 4:48 pm, Christopher Jones > wrote: > > > Did you follow all the steps under > > https

Re: Uninstalling MacPorts on Mac M1 Chip

Did you follow all the steps under https://guide.macports.org/#installing.macports.uninstalling ? > On 12 Jan 2022, at 4:45 pm, Lisa Kim wrote: > > Hi, > > I would like to uninstall MacPorts entirely from my Macbook Pro M1. I

Re: certbot for 'arm64' dependency py39-zope-hookable only supports 'x86_64' #64364

:p...@ehealth.id.au> > “Behold, this child is appointed for the fall and rising of many in Israel, > and for a sign that is opposed (and a sword will pierce through your own soul > also), so that thoughts from many hearts may be revealed.” > >> On 5 Jan 2022, at 8:44 pm, Christoph

Re: certbot for 'arm64' dependency py39-zope-hookable only supports 'x86_64' #64364

Few maintainers/users have arm machines at this time, so for those that do you have to expect to do some leg work yourself. I suggest trying to edit the Portfile in question, removing the line that limits the platforms

Re: ffmpeg unexpectedly uninstalled

> On 4 Jan 2022, at 9:38 am, Ryan Schmidt wrote: > > On Jan 4, 2022, at 02:52, Christopher Jones wrote: > >> Personally, I also occasionally run >> >>> port list requested >> >> to see the list of ports I have actively *requested* to be inst

Re: ffmpeg unexpectedly uninstalled

As others have already commented, the best way to perform regular clean up on your installation is to just run > sudo port reclaim that does a number of tasks, all designed to clean up your installation. Personally, I also occasionally run > port list requested to see the list of ports I

Re: ImageMagick failure to install

cal/lib/libstdc++.6.dylib already exists. Moving to: > /opt/local/lib/libstdc++.6.dylib.mp_1639575707. > ---> Cleaning libgcc-devel > • miniadmin@mm02:~ > > After that I could install ImageMagick. > > So, should I happily disregard those warming messages? > > And, a

Re: ImageMagick failure to install

ome packages will force the install of libgcc and some > others will require libgcc-devel. Will see and report the outcome... > > Thanks > > Franco > > >> On 15 Dec 2021, at 12:51, Christopher Jones wrote: >> >> Hi, >> >> gcc-devel is the (current) pre

Re: ImageMagick failure to install

Hi, gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow

Re: python ports depend on openssl not in index

Just to be clear, are you saying running > sudo port selfupdate ran without warnings or error, but did not actually update ? If thats the case we should file a bug against base as if the rsync fails it should indicate this to the user ? cheers Chris > On 10 Dec 2021, at 3:13 pm, SeaQuench

Re: mozjs60 doesn't want to install

Follow the instructions given to you below. i,e, https://guide.macports.org/#project.tickets > On 9 Dec 2021, at 2:59 pm, Stevan Tiefert via macports-users > wrote: > > Hello, > > if I execute following: > > sudo port install mozjs60 > > I

Re: liboil fail to compile

Hi, yes, Ryan beat me to reply here ;) https://github.com/macports/macports-ports/commit/d5397ebb011482fd219217c44b21d2c0b329180d Chris > On 23 Nov 2021, at 1:41 pm, Ryan Schmidt wrote: > > On Nov

Re: xorg-server

See https://trac.macports.org/ticket/63990 rev bumping the xinit port fixed things, at least for me. Please if you are having trouble with the X11 server see if that update helps... > On 18 Nov 2021, at 8:02 am, Ryan Schmidt wrote: > > On Nov 15,

Re: provide latest OS root certificates via port?

> >> it uses the libcurl support compiled into macports base, which >> defaults to using the system curl. To change that you need to rebuild >> base against an updated lib curl. > > Is that something that can be made to happen for all users by the creation > of a new version of something (e.g.,

Re: provide latest OS root certificates via port?

> > Unfortunately, mpstats submit still doesn't work on 10.6.8, > even with /usr/bin/curl replaced with a symlink to > /opt/local/bin/curl. I don't understand that. > /usr/bin/curl https://ports.macports.org works there with > the symlink in place. mpstat doesn’t use the command line curl

Re: do I have to reinstall my ports after upgrading to Monterey?

González López via macports-users > wrote: > > >> On 31 Oct 2021, at 16:46, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> >> Yes you do. You should always follow the migration instructions under >> >> https://trac.m

Re: do I have to reinstall my ports after upgrading to Monterey?

Yes you do. You should always follow the migration instructions under https://trac.macports.org/wiki/Migration Chris > On 31 Oct 2021, at 3:45 pm, Artemio González López via macports-users > wrote: > > I just installed macOS 12.0.1 on an M1

Re: provide latest OS root certificates via port?

> On 29 Oct 2021, at 4:17 pm, Richard Bonomo TDS personal > wrote: > > > I don't know what to think about MacPorts, specifically, providing > new certificates, but, pertaining to some of the arguments presented > against doing this on old Macs generally, it must be kept in mind > that some

Re: Youtube-dl install failure

create a trac ticket, with a *complete* build log. > On 27 Oct 2021, at 5:11 pm, dan d. wrote: > > > If I had to guess the install routine is not fetching the youtube-dl > distribution files to install. > > I get this error message > > Error: Failed to install youtube-dl: no destroot found

Re: Question about realeasing *pkg for macOS 12 on website

I don’t know about an ETA, but you do not need to wait for them to get started. Just follow the install from source instructions in the meantime. > On 26 Oct 2021, at 1:26 pm, xgfvc via macports-users > wrote: > > Hello everyone, > > Hope you’re doing well. I have a question: Do we have an

Re: Macports for Monterey on M1, M1 Pro, M1 Max

Hi, In that MacPorts already supports arm for macOS11, adding support for macOS12 will likely not be as much of a deal as it was for macOS11, where it was a brand new arch. I imagine it will be, give or take, as much work as any other OS has been on the x86_64 side. As for if/when there will

Re: Error: Failed to build librsvg: command execution failed

ls: /opt/local/bin/clang-mp-11: No such file or directory > > >> On Oct 13, 2021, at 19:31, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> oh, and to be sure please first run `sudo port sync` t make sure your ports >> are fully up t

Re: Error: Failed to build librsvg: command execution failed

oh, and to be sure please first run `sudo port sync` t make sure your ports are fully up to date…. > On 13 Oct 2021, at 1:30 pm, Christopher Jones > wrote: > > That old ticket indeed has nothing to do with the issues here > > The rust port does indeed require macports clang

Re: Error: Failed to build librsvg: command execution failed

That old ticket indeed has nothing to do with the issues here The rust port does indeed require macports clang (on older systems) to be available when building with rustic. However, macOS 10.13 is not one of these (at starts with 10.12) so it shouldn’t be needing it. Please run `port info

Re: What is the best way of installing Python's scientific libraries in MacPorts?

> On 4 Oct 2021, at 9:18 pm, Artemio González López via macports-users > wrote: > >> >> On Oct 4, 2021, at 4:24 PM, Giuseppe 'ferdy' Miceli > > wrote: >> >> ciao artemio, >> >>> Hi, Giuseppe, >> >> >> >>> So my questions are: >>> >>> 1. Should I activate python39

Re: What version of Xcode for which macOS ?

> On 27 Sep 2021, at 8:49 am, Bjarne D Mathiesen > wrote: > > This thread led me to search for the relationships between > * Xcode version > * macOS / OS X version > and I couldn't find a table with these > > So far, I've come up with > > Mac OS X / mac OS | Xcode >

Re: XCode reinstall command-line tools

> On 23 Sep 2021, at 1:32 am, Tom wrote: > > Can’t you simply just ignore that error message? Generally no. things will start to fail to build if its not addressed. its there for a reason... > >> On 22. Sep 2021, at 21:48, Justin Vallon wrote: >> >> I upgraded XCode, and encountered the

Re: learning to trac

> On 16 Sep 2021, at 8:51 am, Epstein, David via macports-users > wrote: > > > Yesterday I submitted a Trac Ticket (my first), and there has been some > activity: the Trac system has been keeping me up-to-date with emails. > > I have been unable to find out either from Google or from the

Re: gcc<10 on M1 Mac

Hi, Its highly unlikely you will ever get support for gcc<10 on arm. We only have support for 10 and 11 because we are using unreleased back ports of support from a development branch on arm for these two versions. The back port has not been done for anything older than 10, and is highly

Re: cdrtools streamripper

seppe Di Matteo > pinodimat...@me.com <mailto:pinodimat...@me.com> > > > > > >> Le 8 juin 2021 à 20:48, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> a écrit : >> >> >> For the smake issue see >> >> https://github.com

Re: cdrtools streamripper

For the smake issue see https://github.com/macports/macports-ports/commit/9040f7195e114173a42c71ee57e74c248ef7ebb1 > On 7 Jun 2021, at 5:15 pm, Andrew Udvare wrote: > > >> On 2021-06-07, at 09:34,

Re: Telnet not in netutils

recalled how to quit the telnet session (on the Mac keyboard): > CTRL-ALT-] > (^]) :) > > > >> Am 27.05.2021 um 22:04 schrieb Christopher Jones : >> >> Hi, >> >> I guess you didn’t read/notice the port notes when you installed inetutils ? >

Re: Telnet not in netutils

Hi, I guess you didn’t read/notice the port notes when you installed inetutils ? inetutils has the following notes: All clients are now installed with the "g" prefix. Oberon ~/Projects/MacPorts/ports > sudo port contents inetutils | grep telnet /opt/local/bin/gtelnet

Re: MacPorts 2.7.0 Warning

>> >> What is the output of: >> >> grep -F universal_arch /opt/local/etc/macports/macports.conf >> >> ? >> >> Are you on an M1 system? >> >> The default setting is "arm64 x86_64" (without quotes). You can comment out >> the universal_archs line with # to get the default. > > The output of

Re: [Xfig hangs on start]

Hi, fig is an X11 application, and thuis requires an X11 server to be installed to work. Do you have one installed ? If you are not sure run sudo port install xorg-server and follow the instructions at the end to log out and back in again, and then retry running xfig. Chris > On 17 May

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

OK, I have no idea if julia itself supports Arm yet. I suggest you search for tickets against julia at https://trac.macports.org and if not submit one. Chris > On 7 May 2021, at 2:01 pm, > wrote: > > With gcc10 installation fails as well: > > :info:build >

Re: Issue compiling simple code with clang++-mp-11

See https://trac.macports.org/ticket/62770 Its the macOS11.3 / Xcode 12.5 update, it has broken all MacPorts clang versions <= 11 At this time the only macports clang that works is the clang-level port. Chris > On 3 May 2021, at 1:14 pm, Andrew Udvare

Re: Blimey, but that was a huge update...

> > Looks like a good chunk was recompiled, the major culprits being LLVM and GCC > and friends. > > Are there no longer any binaries for Sierra? No, they are still being produced when possible, as for all other OSes. See https://build.macports.org/waterfall

Re: QEMU GUI

> On 25 Apr 2021, at 11:55 am, FritzS - gmx wrote: > > Why QEMU GUI are not available? > > https://sourceforge.net/projects/qemu-gui/ … because no one has been interested to submit a GitHub PR implementation them. Please feel free to do so

Re: Binary archive for mpich-default is available but not used

HI, It is expected. See https://github.com/macports/macports-ports/blob/7541d508815705d370fbe619b3a407e30963edf1/science/mpich/Portfile#L220 A message at that point might be

Re: Error: Failed to configure boost

Python 2.7 is no longer the default variant with boost, and your log shows you are still using this. > sudo port sync > sudo port -f uninstall boost > sudo ports install boost As others have said, the best way to avoid issues like this is to not leave things too long between port updates. >

Re: Trying to get macports running on my new M1 MacBook Air

> ---> Fetching distfiles for libgcc10 > Error: gcc10 10.3.0 is not supported on Darwin 20 arm > Error: Failed to fetch libgcc10: incompatible OS X version > Error: See >

Re: -march arm64

No released version of GCC supports Apple M1 machines. You need to use the gcc-devel port for now, which provides developmental snapshot build with (experimental) support. > On 21 Apr 2021, at 6:07 pm, Tom wrote: > > Hi, > > gcc does not seem to support -arch arm64 > Can ti be build with

Re: Update on Big Sur Problems

_tarballs_ports_math_atlas/atlas/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > Error: Processing of port atlas failed > > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math

Re: Update on Big Sur Problems

th_atlas/atlas/work/ATLAS/CONFIG/src/atlcomp.txt >> Error: Failed to configure atlas: sysctl failed: No such file or directory >> Error: See >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/main.

Re: Update on Big Sur Problems

libgcc8 >libgcc9 > libgcc > libgcc10 > pmm:~ pet$ > > ps: without +atlas sundials2 installs successfully > > pmm:~ pet$ uname -a > Darwin pmm.local 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST > 2021; root:xnu-7195.81.3

Re: Update on Big Sur Problems

Hi, Any port that forces the use of gcc10 or older on M1 macs cannot work, as these gcc versions are never going to be supported on these machines. Even gcc11 support seems unlikely at this time, so for a while gccdevel is likely going to be the only supported version on these machines, which

Re: Getting python3.8 with macports

Just like how you would install any other port... > sudo port install python38 gives the latest python 3.8 or > sudo port install python39 for the latest in the 3.9 series. > On 16 Apr 2021, at 3:47 pm, Christoph Kukulies wrote: > > How can I upgrade to the latest version of python (python

Re: Messed with a binary in /usr/local/bin

Hi, > On 16 Apr 2021, at 3:46 pm, Christoph Kukulies wrote: > > I messed up my macports structure a bit. > While I was in need of a newer tidy (tidy-html5) I deleted > /usr7local/bin/tidy (which is the macports binary if I’m correct). No, it is not from MacPorts. MacPorts (by default)

Re: gfortran for M1?

sorry… auto text correction turned ‘xcrun’ into ’scrub’…. > On 20 Mar 2021, at 3:50 pm, Christopher Jones > wrote: > > Hi, > > You probably need to specify the SDK location. There are a number ways you > can do this, gcc now supports the same mechanisms as cl

Re: gfortran for M1?

Hi, You probably need to specify the SDK location. There are a number ways you can do this, gcc now supports the same mechanisms as clang. i.e. using scrub or setting SDKROOT . I personally have export SDKROOT=`xcrun --show-sdk-path` in my shell profile for this very reason. Chris > On 20

Re: Debugging restore_ports.tcl

> On 9 Feb 2021, at 11:22 am, Pieter van Oostrum > wrote: > > Eric Gallager via macports-users > writes: > >> On Mon, Feb 8, 2021 at 1:03 PM Ryan Schmidt wrote: >>> >>> >>> >>> On Feb 7, 2021, at 20:59, Eric Gallager wrote: >>> When

Re: stdlib.h compilation error for macports gcc9.

what happens if you set SDKROOT and then try again export SDKROOT=`xcrun --show-sdk-path` ? > On 7 Feb 2021, at 11:12 pm, Carlo Tambuatco wrote: > > > >> On Feb 7, 2021, at 5:39 PM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> &g

Re: stdlib.h compilation error for macports gcc9.

macOS 11 brought big changes to how Apple versions its SDKs. They now potentially change each minor update, and as such we had to figure out how to deal with this. gcc is built against a specific SDK, and to handle this unpredictably it was recently changed to use the unversioned SDK, instead

Re: latest update to BigSur 11.1 broke gcc

From a combination of my memory, and reading the tickets referenced in the gcc port file, if we don’t use —with-sysroot we would need to use --with-build-sysroot in order for the build to work, and last time that was tried it didn’t work correctly. > On 16 Dec 2020, at 3:37 am, Ken Cunningham

Re: latest update to BigSur 11.1 broke gcc

Hi, This is another consequence of a change Apple has introduced with macOS11 which is the SDK version now changes on every incremental OS update. So updating from 11.0 to 11.1 (and I presume Xcode 12.3) you now have SDK 11.1, not 11.0, and thus the current build of gcc, which has the sys root

Re: Running X11 in MacOS-window-as-X11-display mode?

nked. It >> was unusable. I complained on macports-users on April 1st 2019. There was >> a thread about it and Christopher Jones created a xorg-server-1.18 port, >> which made things better for me. > > Oh yes I do remember that. I've stayed on High Sierra so I haven't

Re: Running X11 in MacOS-window-as-X11-display mode?

> On 9 Dec 2020, at 5:52 am, Ken Preslan via macports-users > wrote: > > On Tue, Dec 08, 2020 at 09:47:54PM -0800, Ken Cunningham wrote: >>> In the Mojave time-frame the xorg server was updated from 1.18 to 1.20. >>> Performance for xterm scrolling tanked. >> There was indeed one update

Re: Libgcc: new version won't deactivate the old version

> On 4 Dec 2020, at 2:36 am, Michael wrote: > >> ---> Computing dependencies for libgcc >> The following dependencies will be installed: libgcc10 >> Continue? [Y/n]: y >> ---> Activating libgcc10 @10.2.0_3 >> Error: Failed to activate libgcc10: Image error: >>

Re: Removing all non-requested ports?

> sudo port uninstall leaves sometimes you need to run it more than once to pick everything up. that said, I use > sudo port reclaim these days which does the above, and a bit more. Chris > On 3 Dec 2020, at 9:08 am, Michael wrote: > > What's the command to remove non-requested ports

Re: Problem with building poppler

Yes, known. See the last ticket at https://ports.macports.org/port/poppler/tickets > On 25 Oct 2020, at 9:44 pm, Dave Horsfall wrote: > > Sierra 10.12.6 (won't go any further), MacPorts 2.6.3 on a mid-2010 MacBook > Pro. > > (Looks like

Re: Failure to upgrade outdated

Hi, The error Error: Failed to activate libgcc10: Image error: /opt/local/lib/libgcc/libatomic.1.dylib is being used by the active libgcc port. Please deactivate this port first, or use 'port -f activate tells me its really been a very very long time since the ports where last updated

Re: macports-users Digest, Vol 168, Issue 7

Hi, What does ~ > xcode-select -p /Applications/Xcode.app/Contents/Developer If it does not point to the correct Xcode installation, then you need to do what the instructions below say, use the utility to set the correct location. Chris > On 7 Aug 2020, at 7:20 pm, Thomas Bodlien > wrote:

Re: cltversion error

ampusvej 55, 5230 Odense M > Denmark > Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/> > >> On 12 Jun 2020, at 10.35 PM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> Hi, >> >> Glad I could help. >> >>

Re: cltversion error

5230 Odense M > Denmark > Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/> > >> On 12 Jun 2020, at 10.06 PM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> Hi, >> >> Please run this, and check you get

Re: cltversion error

Hi, Please run this, and check you get something similar > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables package-id: com.apple.pkg.CLTools_Executables version: 11.5.0.0.1.1588476445 volume: / location: / install-time: 1591989507 groups: com.apple.FindSystemFiles.pkg-group If

Re: SDK 10.15 available but not found

> On 23 May 2020, at 5:13 pm, Christopher Chavez wrote: > > On 5/23/2020 10:57 AM, Philippe Morey-Chaisemartin wrote: >> xcode version: 11.5 (11E608c) > > I think new Xcode versions had to first be whitelisted by MacPorts, so > it's likely that the recent 11.5 release just hasn't been added

Re: Building xorg fails

> On 9 May 2020, at 4:12 pm, Christoph Kukulies wrote: > > > >> Am 09.05.2020 um 17:02 schrieb Lenore Horner > >: >> >> Try cleaning after uninstalling (although when I recently uninstalled >> inactive, I think clean happened automatically). >> >>> On

Re: X11 no longer working

warned... > > So I didn’t run into this error below again. > > Thanks to all. > > > X11 working again. > > — > Christoph > > >> Am 09.05.2020 um 14:09 schrieb Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>>: >> >>

Re: X11 no longer working

Thats not what I am referring to. There was likely a warning earlier on directing you to the macports problem hot list. > On 9 May 2020, at 1:07 pm, Christoph Kukulies wrote: > > > >> Am 09.05.2020 um 13:51 schrieb Christopher Jones > <mailto:jon...@hep.phy.cam.ac.u

Re: Building xorg fails

ou most probably would have found an error message directing you to https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt> Go there and follow the instructions therein. Chris > > >> Am 09.05.2020 um 13:53 schrieb C

Re: Building xorg fails

you do not need to install all off xorg just to get the X11 server. You only need xorg-server for that. > On 9 May 2020, at 9:12 am, Christoph Kukulies wrote: > > In my desperation about this - currently unresolvable x11/Quartz server > problem - I’m trying tp build Xorg/Quartz under

Re: X11 no longer working

looks like your xorg-server installation is not working. Try removing it, reinstall, then log out and back in again. > On 9 May 2020, at 12:39 pm, Christoph Kukulies wrote: > > > >> Am 09.05.2020 um 13:22 schrieb Richard Tobin > >: >> >> > Does running

Re: X11 Server (Quartz 1.20.4) not having security extensions

Hi, I am not an expert on this, but my understanding is this was intentionally disabled by default by the Xorg server build system, when XACE was added. The MP port stays as close to the upstream defaults as it can. That said, adding an optional variant to enable this, if the user wishes to,

Re: Cannot do anything with port - upgrade, uninstall not possible

Hi, Thats because you starting following the instructions *after* upgrading, not before. You need to reinstall macports over the top of your current installation, to update to the binary to that for your current system, then try again. https://www.macports.org/install.php

Re: Is SSL really a dependant of everything?

> On 6 Apr 2020, at 8:42 am, Dave Horsfall wrote: > > On Mon, 6 Apr 2020, Ryan Schmidt wrote: > >> You should not routinely use the -p flag like this. > > I did that following advice on this list about a year ago, when some port > ("guile"?) that I'd never even heard of would not build. >

Re: installing patched okular: cannot open Portfile

> On 17 Mar 2020, at 6:11 pm, Ryan Schmidt wrote: > > > > On Mar 16, 2020, at 14:53, Ken Cunningham wrote: > >> It is a permissions error. Although Chris and others seem to make this work, >> it has never worked for me to put a macports repo in my home folder. I don’t >> know why, and I

Re: macports-users Digest, Vol 163, Issue 12

> On 17 Mar 2020, at 3:04 pm, Murray Eisenberg > wrote: > > I did that: used mode 755 for directories, mode 644 for files there. > > Still, same error Unable to execute port: Could not open file: > /Users/murray/macports/myports/kde/okular/Portfile > > Did you get this to work with your

Re: Why are my por definitions still out of date after this?

> On 22 Feb 2020, at 1:39 pm, Gerben Wierda wrote: > > > >> On 22 Feb 2020, at 13:32, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> Have you told macports to use your git clone ? >> >> i.e. >>

Re: catalena

Generally speaking mac OS 10.15 works just as well as any other, and as with other OSes there are some known issues. Like 32 bit support (not possible on 10.15). Only you know which ports you use, and without this it is impossible to be any more specific. note though, if you new machine was

  1   2   >