Re: Port Reclaim

Run > port list requested and check everything you expect to be there is. If not, manually set it as requested yourself > sudo port setrequested XYZ port reclaim will not remove anything in the above list, or anything in the dependency tree of something in that list. Anything else is fair

call for Xcode15 Intel testers ?

Hi all, Could I ask if anyone is running an Intel system, with Xcode 15 installed to take a look at https://trac.macports.org/ticket/68322 and in particular report if they can build libgcc12 or not. The report there is seemingly showing issues with the ‘ld -ld_classic’ workaround we are

Re: { darwin any } ports getting reinstalled after OS upgrade

> On 27 Sep 2023, at 2:01 pm, Nils Breunese wrote: > > Christopher Jones wrote: > >> I had no idea we supported single tarballs for multiple OS versions. >> >> I must say, the distinction between >> >> platforms { darwin any } >> >>

Re: { darwin any } ports getting reinstalled after OS upgrade

> On 27 Sep 2023, at 12:32 pm, Ryan Schmidt wrote: > > On Sep 27, 2023, at 06:09, Christopher Jones wrote: >> >> That just means they are *supported* on any drawn version. Each version >> still have its own build. > > But that's just what "any&qu

Re: { darwin any } ports getting reinstalled after OS upgrade

That just means they are *supported* on any drawn version. Each version still have its own build. b.t.w. When upgrading to a new major OS version, you anyway should follow the migration instructions, which involves manually removing all ports anyway. https://trac.macports.org/wiki/Migration

Re: Why some ports seem to install universal when I do not request it ?

but this seems unnecessary as remove it they build fine for arm64, so can be removed. cheers Chris > On 15 Aug 2023, at 5:59 am, Joshua Root wrote: > > On 15/8/2023 05:06, Christopher Jones wrote: >> Hi All, >> Just migrated from an intel to AppleSilicon machine. >>

Why some ports seem to install universal when I do not request it ?

Hi All, Just migrated from an intel to AppleSilicon machine. Reinstalling MacPOrts, from scratch off course, I’ve noticed some ports get install universal, when it’s not something I have requested. e.g. ---> Fetching archive for zlib ---> Attempting to fetch

Re: The State of Rust in MacPorts Today

t of i386 isn't yet finished at upstream. I plan to fix >> it, but it requires time and availability of hardware to test it :) >> >> I do have a commits which implements rust bootstrap by cahin: mrustc -> rust >> 1.54 -> rust 1.55 -> rust 1.56; I can start to o

Re: The State of Rust in MacPorts Today

Hi, In my opinion, hosting and maintaining these ‘bootstrap’ compilers outside the macports infrastructure was a poor choice, for all the reasons you mention below. I thought this at the time it was done, and even more so now. Personally, I would suggest you think about a change to how the

Re: MacPorts 2.8.0-beta1 now available for testing

ays worked in the past. > >> On Oct 20, 2022, at 7:26 AM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> The message >> >> There is no tracking information for the current branch. >> Please specify which branch you want to re

Re: MacPorts 2.8.0-beta1 now available for testing

The best I can do is monitor it and see if I can spot any pattern as to when >> it happens or not. I am now on the official 2.8.0 release and still see it >> happen, so lets also see if any others start to see the same or not. >> >> Chris >> >>> On 19 Oct 2

Re: MacPorts 2.8.0-beta1 now available for testing

git-pull(1) for details. > > git pull > > If you wish to set tracking information for this branch you can do so with: > > git branch --set-upstream-to=origin/ master > > Command failed: /opt/local/bin/git pull --rebase --autostash > Exit code: 1 &

Re: MacPorts 2.8.0-beta1 now available for testing

. You might have to do some more digging to > figure out a repro recipe I'm afraid. > > - Josh > > On 2022-10-18 20:09 , Christopher Jones wrote: >> Hi, >> I’m not running the beta but the current master branch of base, but I guess >> its similar. >> I’

Re: MacPorts 2.8.0-beta1 now available for testing

Hi, I’m not running the beta but the current master branch of base, but I guess its similar. I’m noticing with the latest version `sudo port sync` just hangs up after updating my local git clone. e.g. Oberon ~/Projects/MacPorts/ports > sudo port -d sync DEBUG: Copying

Re: ports.macports.org gives strange port dependencies

> On 24 Sep 2022, at 3:52 pm, Arjun Salyan wrote: > > The output of "port info pciids” from the same Docker container says: Can you please run > port -d info pciids pipe the output to file and send it here ? I want to see if we can figure out what is leading port to decide to add these

Re: ports.macports.org gives strange port dependencies

> On 24 Sep 2022, at 4:00 pm, Christopher Jones > wrote: > > > >> On 24 Sep 2022, at 3:52 pm, Arjun Salyan > <mailto:ar...@macports.org>> wrote: >> >> The output of "port info pciids” from the same Docker container says: >> >

Re: ports.macports.org gives strange port dependencies

> On 24 Sep 2022, at 3:52 pm, Arjun Salyan wrote: > > The output of "port info pciids” from the same Docker container says: > > Build Dependencies: clang-3.4 > > And the PortIndex on the same machine (generated using “-p macosx_19_i386”) > has: > > depends_build port:clang-15 right,

Re: CalculiX build error using clang

clang is correct in this case, gcc is being sloppy. Basically you cannot return a value, from a function declared as void… fairly basic stuff really.. > On 26 Jul 2022, at 5:34 pm, Mark Brethen wrote: > > I’m seeing this build error when using clang (gcc doesn’t complain): > > info:build

Re: fetch timeout

> On 20 Jul 2022, at 6:32 pm, Dave Allured - NOAA Affiliate via macports-dev > wrote: > > On Wed, Jul 20, 2022 at 2:30 AM Christopher Jones <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> On 20 Jul 2022, at 1:13 am, Dave Allured - NOAA Affiliate via macports-

Re: fetch timeout

> On 20 Jul 2022, at 1:13 am, Dave Allured - NOAA Affiliate via macports-dev > wrote: > > Hmmm. If port curl is already installed and active, then why would > subsequent port fetches prefer /usr/bin/curl? Is this a search path issue? No. port does not rely on finding ‘curl’, from PATH. It

Re: fetch timeout

> On 17 Jul 2022, at 7:12 pm, Mark Brethen wrote: > > It’s interesting that curl fails from my older MacBook Air, but passes on the > M1 iMac, both with OS 11 installed. Even after a clean reinstall. I suspect > it’s something about Apple’s openssl. Browsers don’t seem to mind the >

Re: +universal for x864+arm64 on Macintel

> On 15 Jun 2022, at 3:25 pm, René J.V. Bertin wrote: > > >> Base is exactly smart enough. When supported_archs contains only 1 arch, it >> does make sense to offer a universal variant, therefore base prevents it. > > As I said before, supported_archs contains x86_64 and arm64. what about

latest git version no longer detected by base

Hi All, Does anyone have any ideas on https://github.com/macports/macports-ports/commit/053dbb666a57972ceefba10b1edd12f16d886fd4#commitcomment-71271508 something about the

Re: /usr/bin/python will be removed in macOS 12.3!

are finds python from MacPorts? Not so easy, as it could be hidden away in the build infrastructure. It might not be at all obvious from just looking at the port file... Probably the only way is to wait for the bug reports once 12.3 is out ... > > G > > Sent from my iPhone > >

Re: /usr/bin/python will be removed in macOS 12.3!

> On 19 Feb 2022, at 1:58 pm, Gerben Wierda via macports-dev > wrote: > > Oof. > > I’m happy to check as soon as 12.3 is out, but I wonder how to check. > Installing a port is easy enough to do, but how do I find out if a port uses > it in some arcane way? And if it does, how should one

Re: bazel build points to builder directory _opt_bblocal_var_buildworker_ports_build_ports_devel_bazel

l-3.7/bin/bazel for the > string “_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel” but it’s > not there, at least not in plain text. I have no idea how this path is being > introduced at the build stage. > > > Attachments: > > > > >

Re: bazel build points to builder directory _opt_bblocal_var_buildworker_ports_build_ports_devel_bazel

> On 14 Jan 2022, at 3:14 am, Steven Smith wrote: > > I’m trying to build/update py-tensforflow-metadat and am hitting this > (bizarre) bazel issue. > > First, the build fails with the error: > >> :info:build Execution platform: @local_config_platform//:host >> :info:build Use

Re: SecTrustEvaluateWithError on 10.12 and earlier?

Have you reported it to the developers to see what they say ? > On 9 Jan 2022, at 7:31 pm, Herby G wrote: > > The latest Go (1.17.6) isn't building on 10.12 and earlier due to missing > SecTrustEvaluateWithError >

Re: [10.6.8] MySQL 5.7.36_1 compile hell

> > DEBUG: configure phase started at Mon Dec 20 14:44:46 CET 2021 > ---> Configuring mysql57 > DEBUG: Preferred compilers: macports-clang-9.0 macports-clang-8.0 > macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 > macports-clang-11 macports-clang-10 macports-clang-3.7 macports-clang-3.4

Re: [10.6.8] MySQL 5.7.36_1 compile hell

protobuf-cpp and protobuf3-cpp are two different ports… anyway, looks like you have got your registry into a screwy state in someway, to get DEBUG: Registry error: protobuf3-cpp not registered as installed & active. try installing protobuf3-cpp (i.e. with a 3…) and then see what happens. > On

Re: Acceptability of depends_build bin:…

> On 13 Dec 2021, at 10:48 am, Christopher Chavez wrote: > > I recently specified bin:node:… build dependency in qt5-qtwebengine. I would > not consider Node.js to be a lightweight dependency, so I thought it would be > preferable to allow using whichever is present, even a non-MacPorts one,

Re: Recent OpenSSL changes and CA certs

ink was no worse than anyway not having the file it pointed at. > > 2. Does openssl10 not need the same workaround? yes, and openssl3. Just doing some test builds on these before pushing them. Chris > > -Aaron > > On Wed, Oct 13, 2021 at 5:35 PM Christopher Jones &

Re: Recent OpenSSL changes and CA certs

Should be addressed by https://github.com/macports/macports-ports/commit/f972290289d1d8370b3ca69554cbcf046c7023fa <https://github.com/macports/macports-ports/commit/f972290289d1d8370b3ca69554cbcf046c7023fa> > On 13 Oct 2021, at 9:21 am, Christopher Jones > wrote: > >

Re: Recent OpenSSL changes and CA certs

Sorry, forget the comment below, read it the wrong way around… > On 13 Oct 2021, at 9:00 am, Christopher Jones > wrote: > > Hi, > > Howe does > > /opt/local/libexec/openssl11/etc/openssl/cert.pem > > get created, as its not actually part of the opens

Re: Recent OpenSSL changes and CA certs

Hi, Howe does /opt/local/libexec/openssl11/etc/openssl/cert.pem get created, as its not actually part of the openssl11 port itself ? Oberon ~/Projects/MacPorts/ports > port contents openssl11 | grep cert.pem Oberon ~/Projects/MacPorts/ports > Chris > On 13 Oct 2021, at 5:58 am, Aaron

Re: upgrade to openssl 3.0.0

https://github.com/macports/macports-ports/pull/12514 <https://github.com/macports/macports-ports/pull/12514> > On 6 Oct 2021, at 5:46 pm, Christopher Jones wrote: > > I’m working on the basic changes to implement my suggestion at the moment. > Once that is there test

Re: upgrade to openssl 3.0.0

en > > > On Tue, Oct 5, 2021 at 12:54 PM Fred Wright <mailto:f...@fwright.net>> wrote: > > On Mon, 4 Oct 2021, Christopher Jones wrote: > >> On 4 Oct 2021, at 5:54 pm, Ken Cunningham >> <mailto:ken.cunningham.web...@gmail.com>> wrote: > >>

Re: upgrade to openssl 3.0.0

system where in future it will be > much easier to deal with future new major versions, without having to > have these discussions again... Say 3.1 or 4.0 comes out, a new isolated > opensslXY port can be added to provide that, that will live alongside > the current ones. A few ports c

Re: upgrade to openssl 3.0.0

> On 2 Oct 2021, at 8:06 pm, Ken Cunningham > wrote: > > That is exactly the approach that I don't find workable, Chris. > > Specifically: > > 1. every single port (think: rust, ghc, blah blah) will have to be needlessly > managed to build against an alternate openssl location. why ? They

Re: upgrade to openssl 3.0.0

> On 2 Oct 2021, at 9:03 pm, Renee Otten wrote: > > I was initially suggesting the same approach, which is a slightly more > conservative approach, in the Trac ticket > (https://trac.macports.org/ticket/63461 > ) but by now I am in favor of the >

Re: [NEW] www/unit

Rather than sending around attachments, it would be much more convenient for commenting if you could open a PR with the update. https://github.com/macports/macports-ports Chris > On 29 Sep 2021, at 10:50 am, Sergey A. Osokin wrote: > > Hi, > >

Re: Haskell Stack Ports on Apple Silicon

That line is indeed limiting support to intel machines. If it works on arm add that to the list, or probably better just remove it and rely on the defaults. Chris > On 13 Aug 2021, at 1:55 pm, Steven Smith wrote: > > Is this line in the stack Portfile the issue? Ports (like pandoc) that are

Re: upgrade outdated finals with can't read "epoch_installed": no such variable

thanks, that was it. Chris > On 7 Jul 2021, at 3:04 pm, Kurt Hindenburg wrote: > > Hi, I had the same issue on src master a few weeks ago; Joshua fixed it on > June 26th. > > Kurt > >> On Jul 7, 2021, at 9:21 AM, Christopher Jones >> wrote: >>

upgrade outdated finals with can't read "epoch_installed": no such variable

Hi, My usual update procedure is now failing with Oberon ~/Projects/MacPorts/ports > sudo port -v upgrade outdated Error: process_cmd failed: can't read "epoch_installed": no such variable Any ideas what might be wrong here ? Started in last few days… Chris smime.p7s Description: S/MIME

Re: live check fetch failures

Hi Ken, To get specific/technical, if you view the raw source for the first mail I sent in this tread, you will see it has in its headers Message-Id: thats the unique identifier for that mail. Then, if you look at Joshua’s reply, it has References: Message-ID: Its that Reference line

Re: live check fetch failures

> On 19 Jun 2021, at 1:35 pm, Joshua Root wrote: > > On 2021-6-19 20:12 , Christopher Jones wrote: >> A quick web search suggests this could be an issue with an older version of >> (lib)curl being used ? Does anyone have any insights into this ? > > Certainly

Re: list ports that depend on a given port

> On 4 Jun 2021, at 8:14 pm, Gregory Anders wrote: > > port echo depends:'(^|\W)boost(\W|$)’ Thanks, that seems a bit better but it still matches port it should not. i.e. it matches py39-scikit-hep-hist which in fact only depends on > port deps py39-scikit-hep-hist Full Name:

Re: list ports that depend on a given port

> > This exact question came up on IRC a while back. IIRC the query is > interpreted as a regular expression. So in order to get matches for only > dependents that begin with “boost” you could try > > port echo depends '^boost' > > (I’m not at my computer ATM so I can’t test this to verify.)

Re: list ports that depend on a given port

> On 4 Jun 2021, at 6:16 pm, atmail.dreamhost.com wrote: > > On Jun 4, 2021, 11:55 AM -0500, Christopher Jones , > wrote: > Hi, > > I want to get a list of all the ports that depend on a given port, boost. I > have been using this > > port echo depends:boost

list ports that depend on a given port

Hi, I want to get a list of all the ports that depend on a given port, boost. I have been using this port echo depends:boost as per https://guide.macports.org/chunked/using.common-tasks.html to do this, but just noticed it is

Re: mailutils: update to version 3.12 - building from command line but failing to build using macports

> ciao! thanks for the prompt reply. > > i have checked and if i am not mistaken there is no ticket for this port. > — > > >> On 28 May 2021, at 12:13, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> Hi, >> >&g

Re: mailutils: update to version 3.12 - building from command line but failing to build using macports

Hi, Please check for open tickets against this port at https://trac.macports.org/wiki/Tickets and if there is none open one with the relevant information. Chris > On 28 May 2021, at 11:09 am, Giuseppe 'ferdy' Miceli wrote: > > Ciao, > > as

Re: Ports updated without maintainer notification?

> OSL in particular appears to be a problem on my machine. I've copied the > newer version of the portfile directly to my local machine, and tried to > build it, but it's failing to build because osl is indirectly dependent on > opencolorio (by way of openimageio), and apparently there's a new

Re: Ports updated without maintainer notification?

> > In addition, I have run a "port selfupdate" on my machine, and yet the > MacPorts on my machine isn't seeing the new version of the port. Is something > broken, either on my machine, or on GitHub? If you aren’t already, I strongly recommend using a direct git clone of the ports tree

Re: OpenMPI Builds for MacOS 10.8 and Earlier, Targetting GCC

> > clang: warning: argument unused during compilation: '-I > /opt/local/include/LegacySupport' > clang: warning: argument unused during compilation: '-I /opt/local/include' > clang: warning: argument unused during compilation: '-I /opt/local/include' > clang: warning: argument unused during

Re: M1 CPU features

> On 26 Apr 2021, at 6:28 pm, Jason Liu wrote: > > Thanks Arno :) > > I'm kind of surprised that the M1 doesn't seem to support any SSE or AVX Thats not at all surprising as those instruction sets are very much specific to X86_64 systems. RISC processors, Arm, do have their own sets

Re: GitHub CI Jobs Failing During MacPorts Bootstrap

See the mail Ryan sent a few days back The Bintray service will cease to exist on May 1. Our pull request CI checks rely on being able to download certain assets from Bintray, so unless we do something to fix this before then, our pull request CI checks will no longer work as of May 1.

Re: Publicizing MacPorts

Hi, > On 24 Apr 2021, at 12:04 pm, Georges Martin wrote: > >> Le 22 avr. 2021 à 17:46, Steven Smith > > a écrit : >> >> Another reason major news like M1 support must be announced. > > > May I ask: how do we *define* "M1 support" in MacPorts? What are the >

Re: emacs-app-devel build fail on master not detected by buildbot

> On 23 Apr 2021, at 3:48 am, Dan Ports wrote: > > On Thu, Apr 22, 2021 at 11:05:34PM +0900, Aaron Madlon-Kay wrote: >> However it was rejected by the maintainer because he *wants* the current >> setup. If the port no longer builds because the referenced commit is more >> than 1,000 commits

Re: emacs-app-devel build fail on master not detected by buildbot

> On 22 Apr 2021, at 10:44 pm, Aaron Madlon-Kay wrote: > > > all it does is save a bit of bandwidth during the fetch > > In the case of Emacs, it saves *gigabytes* during fetch. OK, fair enough. I didn’t realise emacs had quite that much history ;)… > > The depth restriction was a

Re: emacs-app-devel build fail on master not detected by buildbot

> On 22 Apr 2021, at 10:04 pm, Christopher Jones > wrote: > > > >> On 22 Apr 2021, at 9:59 pm, Nathaniel W Griswold >> wrote: >> >> Thank you, Christopher. >> >> Are you saying the date-style depth would be the right way forward? That

Re: emacs-app-devel build fail on master not detected by buildbot

the maintainers decision to change …. Chris > > Nate > >> On Apr 22, 2021, at 3:55 PM, Christopher Jones >> wrote: >> >> >> >>> On 22 Apr 2021, at 3:05 pm, Aaron Madlon-Kay wrote: >>> >>> I proposed in a past PR to emacs-

Re: emacs-app-devel build fail on master not detected by buildbot

> On 22 Apr 2021, at 3:05 pm, Aaron Madlon-Kay wrote: > > I proposed in a past PR to emacs-app-devel to use a modern git flag that lets > you specify a depth based on commit date. That would be the “real” solution > in the direction you’re going. > > However it was rejected by the

Re: Tcl help ...

Hi, > On 29 Mar 2021, at 9:40 pm, Joshua Root wrote: > > On 2021-3-30 06:35 , Christopher Jones wrote: >> Hi All, >> Working on fixing a build issue and hitting a limit in my current >> understanding of Tcl… I am trying to set some new env vars in the build

Tcl help ...

Hi All, Working on fixing a build issue and hitting a limit in my current understanding of Tcl… I am trying to set some new env vars in the build.env set ldflags ${configure.ldflags} build.env-append GO_EXTLINK_ENABLED=1 build.env-append

Re: 11_x86 build - build failures due to 'no space on device'

empty cache, enabling this does not help us at all, and just uses resources. So I will turn this off. Chris > On 23 Mar 2021, at 4:04 pm, Ryan Schmidt wrote: > > On Feb 11, 2021, at 04:21, Christopher Jones wrote: > >> I am seeing some large builds fail due to drive s

Re: github portgroup regex stopped matching

Hi, Yes, it appears something changed here as I am seeing this for all ports that use the GitHub PG defaults. Seems fixed with https://github.com/macports/macports-ports/commit/3f55e163e05ed4c0a7595bfb5b394e0766039c86

Re: warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

> On 15 Dec 2020, at 4:34 pm, Joshua Root wrote: > > On 2020-12-16 02:53 , Christopher Jones wrote: >> >> Suggestion for a fix... >> >> <https://github.com/macports/macports-base/pull/221> > > I don't think we can assume that users will always

Re: warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

> On 15 Dec 2020, at 4:06 pm, Joshua Root wrote: > > On 2020-12-16 03:03 , Christopher Jones wrote: >> >> >>> On 15 Dec 2020, at 3:55 pm, Joshua Root wrote: >>> >>> On 2020-12-16 02:40 , Christopher Jones wrote: >>>> >&g

Re: warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

> On 15 Dec 2020, at 3:55 pm, Joshua Root wrote: > > On 2020-12-16 02:40 , Christopher Jones wrote: >> >> Yes, you are right, ${configure.sdkroot} does indeed fallback to the >> versionless SDK path, but there are other variables like >> ${configure.sdk_versi

Re: warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

> On 15 Dec 2020, at 3:40 pm, Christopher Jones > wrote: > > > >> On 15 Dec 2020, at 3:26 pm, Joshua Root > <mailto:j...@macports.org>> wrote: >> >> On 2020-12-16 02:11 , Christopher Jones wrote: >>> Hi All, >>> >>>

Re: warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

> On 15 Dec 2020, at 3:26 pm, Joshua Root wrote: > > On 2020-12-16 02:11 , Christopher Jones wrote: >> Hi All, >> >> Just a warning that following the macOS 11.1 update (and corresponding >> Xcode 12.3) the SDK version has indeed changed from 11.0 to 11.1

Re: warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

> On 15 Dec 2020, at 3:26 pm, Joshua Root wrote: > > On 2020-12-16 02:11 , Christopher Jones wrote: >> Hi All, >> >> Just a warning that following the macOS 11.1 update (and corresponding >> Xcode 12.3) the SDK version has indeed changed from 11.0 to 11.1

warning - base incorrectly sets SDK version with macOS 11.1 / Xcode 12.3

Hi All, Just a warning that following the macOS 11.1 update (and corresponding Xcode 12.3) the SDK version has indeed changed from 11.0 to 11.1 Oberon ~/Projects/MacPorts/base > ls /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs DriverKit20.2.sdk

Re: Problem with libomp (was supertux)

Hi, > On 5 Dec 2020, at 5:20 pm, Eric Borisch wrote: > > It's part of the LLVM project, and can be built at the same time > (-DLLVM_ENABLE_PROJECTS=openmp)as other tools; I think losing OpenMP support > for MP's clang by default is a step backwards, but most of the google results > for

Re: Problem with libomp (was supertux)

should be fixed with https://github.com/macports/macports-ports/commit/d88607f06cd18787529edcd9f7fb6dd5c26114bd <https://github.com/macports/macports-ports/commit/d88607f06cd18787529edcd9f7fb6dd5c26114bd> built for for me in my 10.9 VM. > On 5 Dec 2020, at 1:11 pm, Christopher Jon

Re: Problem with libomp (was supertux)

Hi, c++ standard support in compilers isn’t always black and white. Compilers often claim to support a given standard, but then fail in some corner cases.. That said, in this case looking at

Re: homebrew moving to /opt/homebrew

The young learn, eventually... > On 18 Nov 2020, at 3:12 pm, Ken Cunningham > wrote: > > As of Apple silicon, apparently. > > https://github.com/Homebrew/brew/issues/7857 > > > Being in /usr/local was always said to be

Re: Problems with Darwin 20 tarballs ?

> On 17 Nov 2020, at 2:18 am, Zero King wrote: > > On Tue, Nov 17, 2020 at 02:09:11AM +, Christopher Jones wrote: >> Hi, >> Is anyone else having problems installing tarballs from the new Darwin20 >> builedbot ? > > Yes, see https://trac.ma

Problems with Darwin 20 tarballs ?

Hi, Is anyone else having problems installing tarballs from the new Darwin20 builedbot ? Oberon-macOS-11 ~/Projects/MacPorts/ports > sudo port -v install llvm-9.0 ---> Computing dependencies for llvm-9.0. ---> Fetching archive for llvm-9.0 Warning: Your DNS servers incorrectly claim to know the

Re: macOS Big Sur 11.0.1 crashes when MacPorts tries to install p5.28-locale-gettext

Installed just fine for me here on mac OS 11.0.1 …. so shrug… Chris > On 13 Nov 2020, at 10:43 pm, Nils Breunese wrote: > > Hello, > > Every time MacPorts tries to install the p5.28-locale-gettext port on my Big > Sur 11.0.1 machine, the OS crashes and the Problem Reporter shows the crash >

Re: does libhttpseverywhere have to have a 7MB uncompressed file of rules in the files dir?

Hi, This file has annoyed me on a number of occasions. I work with a full git checkout and tend to use utilities like ‘git grep’ a lot, and this file often gets a hit in those searches, and due to its size spams the results rendering it almost impossible to view any after that file. One

Re: port "cask" -- installing prebuilt binaries

> On 6 Aug 2020, at 8:02 pm, Ken Cunningham > wrote: > > category-only identifier is > > less clear and less obvious > harder to remember how to search for > name conflicts with a non-binary version (eg for newer systems that can build > it) > > so far, name-suffix is winning on all

Re: Help with UsingTheRightCompiler

You should be setting CXX, not CC, to define the c++ compiler to use… Chris > On 24 Jul 2020, at 7:47 pm, Frank Schima wrote: > > Hi Ken, > >> On Jul 23, 2020, at 10:38 PM, Ken Cunningham >> mailto:ken.cunningham.web...@gmail.com>> >> wrote: >> >>> You have to use clang++ if you are

Re: Help with UsingTheRightCompiler

> Mojave 10.14 and later doesn't provide /usr/include anymore. System headers > like are only in the SDK now. Note the -isystem flag with the > path to the SDK isn't in that compile line. MacPorts put that flag into > CFLAGS, CXXFLAGS, CPPFLAGS, and a comparable one into LDFLAGS for you, so

Re: Deepmind Tree Bazel Build Portfile Help Request

onds when run by hand). > > I must also add the bazel-based builds tensorflow-probability and others, so > getting a robust bazel build approach would be very helpful and useful. > > Steve > > >> On Jul 6, 2020, at 11:57 AM, Christopher Jones > <mailto:jon...@hep.

Re: Deepmind Tree Bazel Build Portfile Help Request

Hi, Are you using this option bazel --max_idle_secs=60 when building with bazel ? Bazel builds start an underlying ’server’ process, that by default hangs around for 3600 secs (yes, 1hour) before disappearing. Without the above your build will hang around waiting for this to happen… Chris

Re: Need some advice regarding patches for old AppKit compatibility

coa.framework/Headers/Cocoa.h, has #import > . Hopefully just wrapping AppKit.h will be sufficient? > > Jason > > -- > Jason Liu > > > On Thu, Jun 4, 2020 at 5:49 AM Christopher Jones <mailto:jon...@hep.phy.cam.ac.uk>> wrote: > > >> On 4 Jun 2020, a

Re: Need some advice regarding patches for old AppKit compatibility

te: > Great, I'll have a look at the stuff in that area. Thanks, Chris. > > Jason > > -- > Jason Liu > > > On Wed, Jun 3, 2020 at 2:38 PM Christopher Jones <mailto:jon...@hep.phy.cam.ac.uk>> wrote: > Hi, > > Sounds like this *could* be a candidate for someth

Re: Need some advice regarding patches for old AppKit compatibility

Hi, Sounds like this *could* be a candidate for something to add to our legacy support package. see https://github.com/macports/macports-legacy-support A port for this exists in MacPorts, and is applied as required to ports that need the

Re: Best way to get submodules into extracted source?

Hi, No, there is I believe no way. If the project has sub modules that need to be initialised, I think the only real way out is to use a direct git fetch. i.e. follow https://guide.macports.org/#reference.portgroup.github.submodule

Re: control verbose mode in Portfile?

> On 21 May 2020, at 9:31 am, René J.V. Bertin wrote: > > Hi, > > Out of curiosity: is it possible to control verbose mode in a Portfile, like > with `set +x` / `set -x` in shell scripts? > > I'd be interested to use that in the post-activate block of a number of my > ports, as an easy way

Re: make xorg-server a dependency of x11 ports?

> On 20 May 2020, at 3:55 pm, Rainer Müller wrote: > > On 20/05/2020 15.30, Ken Cunningham wrote: >> Should xorg-server should be made a dependency of some key x11 component, so >> that when people install an x11 application, xorg-server installs and it >> actually works for them

Re: make xorg-server a dependency of x11 ports?

Hi, Personally, I would say yes, this makes sense given the current state of XQuartz.app cheers Chris > On 20 May 2020, at 2:30 pm, Ken Cunningham > wrote: > > Should xorg-server should be made a dependency of some key x11 component, so > that when people install an x11 application,

Re: One large pull request vs. several small ones?

Hi, > On 13 May 2020, at 3:05 pm, Jason Liu wrote: > > Maybe it would be better to start by submitting one PR for one isolated port. > We can then give you feedback on anything that might need to be changed and > merge it. This may enable you to make similar changes in your other ports >

build.macports.org sites down ?

Hi, Is there an issue with the build site ? e.g. if I try and load https://build.macports.org/waterfall I just get “Processing Failed” https://build.macports.org seems to be working, and some of the links from there, but a

Re: One large pull request vs. several small ones?

Hi, I would definitely say the many small PR approach is preferred to a single massive one with many many changes. A big PR like that is not going to help get it reviewed quicker. Mixing up new ports, with port updates, in one PR would really be a bit of a mess, I would say. So yes, please

Re: alternative for github clone with submodules -> make: *** [install] Error 71

destroy -> destroot ( blame auto-correct…. ) > On 7 May 2020, at 5:21 pm, Christopher Jones wrote: > > > >> On 7 May 2020, at 5:11 pm, macpo...@parvis.nl <mailto:macpo...@parvis.nl> >> wrote: >> >> >>> On 2020-05-07, at 17:46, Christo

Re: alternative for github clone with submodules -> make: *** [install] Error 71

> On 7 May 2020, at 5:11 pm, macpo...@parvis.nl wrote: > > >> On 2020-05-07, at 17:46, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> On 7 May 2020, at 4:41 pm, macpo...@parvis.nl <mailto:macpo...@parvis.nl> >> wrote: &g

Re: alternative for github clone with submodules

> On 7 May 2020, at 4:41 pm, macpo...@parvis.nl wrote: > > >> On 2020-05-07, at 14:58, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> >> see >> >> https://github.com/macports/macports-ports/blob/master/python/py-pytorc

  1   2   >