Re: C++ exception handling on PPC with gcc 6.4.0 doesn't work

do exceptions work with the default gcc7 compiler? K

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

Hi Ken, I’ve updated the port here, just waiting for the CI system to validate on arm, etc before pushing: https://github.com/macports/macports-ports/pull/24159 I don’t know how to use or test those bindings you are asking for, and I

Re: [Pan-users] running pan gives many errors

> On May 8, 2024, at 2:20 AM, Dominique Dumont wrote: > > $ ./debug-build/pan/gui/pan That does it! I had no idea it would matter where you ran pan from, but I can see now that it does, and this works. Thank you for the explanation. Ken ___

Re: [Pan-users] running pan gives many errors

be the intended message content in plain text > (unless I trimmed the HTML incorrectly): > > Ken Cunningham posted on Tue, 7 May 2024 06:01:43 -0700 as excerpted: > >> I don’t know much about gtk programming, but it looks like software is >> meant to ask gtk where the

Re: [Pan-users] running pan gives many errors

I don’t know much about gtk programming, but it looks like software is meant to ask gtk where the icons are installed usingGtk.IconTheme.get_search_pathdocs.gtk.orgI can’t see that function being used in pan so far.KOn May 7, 2024, at 02:58, Duncan <1i5t5.dun...@cox.net> wrote:Ken Cunningham

Re: [MacPorts] #69892: python312 reportedly fails to build on G3: Python: incompatible cpu-subtype

and file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python312/python312/work/Python-3.12.3/Python.framework/Versions/3.12/Python ? On Thu, May 2, 2024 at 9:23 AM MacPorts wrote: > #69892: python312 reportedly fails

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

> On Apr 7, 2024, at 11:24 PM, Riccardo Mottola > wrote: > > Hi, > > Ken Cunningham wrote: >> Up to now, though, older systems have used gcc7, and in a few cases gcc5 or >> gcc48 are used for specific issues. So those gcc versions may still be >> ne

Re: PPC64 install && Firefox

> On Apr 8, 2024, at 1:02 AM, John Paul Adrian Glaubitz > wrote: > > On Mon, 2024-04-08 at 19:38 +1200, Mike Hosken wrote: >> As for Firefox thanks for the info, hopefully it will get fixed as it would >> make >> ppc64 still very useable in this modern era. > > Well, someone interested

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

Once gcc13 is the default gcc used on older systems, it would be hoped that it would cover off most needs. Up to now, though, older systems have used gcc7, and in a few cases gcc5 or gcc48 are used for specific issues. So those gcc versions may still be needed ... time will tell. If the whole

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

Two of the libgccs are stubs, the rest are not. so it is pretty much as bad as it looks.

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

It’s important you understand how the libgcc ports work now, to see how this libgcc chain is set up and the problems it might cause on slower older systems that have no buildbot. Go to an Intel system like 10.7, uninstall all ports. Disable the buildbot by clearing archive_sites in

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

In general, the more a given system deviates from the main herd of ports, the more likely there are to be problems and the less likely they are to be fixed. To be honest, I don’t see why a new gcc port to be used only for powerpc is needed. My only question is whether to skip over gcc8-12, or

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

ith me then to move 10.4–10.5 to libgcc13, > since we should not have a disagreement anymore. > > >> On Mar 29, 2024, at 5:34 AM, Ken Cunningham >> wrote: >> >> I was not aware that supporting the bootleg crippled 10.6 PPC pre-beta had >> anything to do

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

supporting all the gcc versions between gcc 8 and 12 on older systems will be quite a bit of work and require a lot of build time for poor users of these systems. To have libgcc7, the way it is now, you need to build libgcc13, 12, 11, 10, 9, 8, and then 7. That is -- a lot of gcc building for

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

I was not aware that supporting the bootleg crippled 10.6 PPC pre-beta had anything to do with why nobody had gotten around to updating the gcc version used on older systems. At least, it was not anywhere on my radar. Just -- nobody did the legwork. Ken On 2024-03-28, at 11:47 AM, Sergio

Re: cmake-devel --> cmake coming .... please test if you care to

verification. K > On Mar 27, 2024, at 02:29, Riccardo Mottola > wrote: > > Hi Ken, > > Ken Cunningham wrote: >> the cmake port is very very far behind. >> >> cmake-devel has been updated to the newest version currently available >> (3.29.0) for most sy

cmake-devel --> cmake coming .... please test if you care to

the cmake port is very very far behind. cmake-devel has been updated to the newest version currently available (3.29.0) for most systems, and then newest supportable (3.28.4) for 10.7 and < 10.6. Please try out if you care to, as cmake-devel should become cmake soon. If you are interested in

Re: inserting -stdlib=libstdc++ into cxxflags

sorry, clang-11-bootstrap > On Mar 23, 2024, at 00:01, Ken Cunningham > wrote: > > the clang-10-bootstrap port builds against libstdc++ now. > > K

Re: inserting -stdlib=libstdc++ into cxxflags

the clang-10-bootstrap port builds against libstdc++ now. K

Re: GTK on PowerPC: does anyone have it actually working?

> On Mar 15, 2024, at 6:05 PM, Ken Cunningham > wrote: > > > >> On Mar 14, 2024, at 4:07 AM, Sergio Had wrote: >> >> I guess you ask Ken, but anyway, does anyone have X11 GUI working for >> `transmission-x11` > > transmission-x11 works

Re: GTK on PowerPC: does anyone have it actually working?

> On Mar 14, 2024, at 4:07 AM, Sergio Had wrote: > > I guess you ask Ken, but anyway, does anyone have X11 GUI working for > `transmission-x11` transmission-x11 works on 10.6 PPC. (I had to do a little minor surgery on the transmission source code to make it build with gcc7.) Ken

Re: GTK on PowerPC: does anyone have it actually working?

5:33 PM, Riccardo Mottola via macports-dev >>> wrote: >>> >>> Hi, >>> >>> Ken Cunningham wrote: >>> gtk3 (x11 variant) is working fine for me on PowerPC Leopard, for one. >> >> I'm hacking on GTK2 and GTK3 quartz support for Leo

Re: GTK on PowerPC: does anyone have it actually working?

nothing special. if it’s not working for you, we can probably work through it in a ticket… > On Mar 11, 2024, at 00:45, Sergio Had wrote: > > Thank you, Ken, this is helpful. > > Could you say whether you did any specific manual setup for X11? > > > >>>

Re: GTK on PowerPC: does anyone have it actually working?

> Sergey said: > It looks like while even gtk4 builds fine with no hacks (and of course gtk2 > and gtk3 do), none of the apps built against then actually work. Everything > crashes on start. > > Could anyone confirm if any GTK version is known to work on a PPC system, and > point at a

Re: How to force run tests as non-root?

On 25/2/2024 03:07, Ken Cunningham wrote: >> Some of your macports installations are installed as the root user, instead >> of the macports user. >> This happened because there is no installer for 10.6-ppc to automatically >> create the macports user. You have an op

Re: How to force run tests as non-root?

in the master has no support for tests, as of now, so running it gonna fail anyway.)On Sat, Feb 24, 2024 at 11:24 PM Ken Cunningham <ken.cunningham.web...@gmail.com> wrote:Some of your macports installations are installed as the root user, instead of the macports user. This happened b

Re: How to force run tests as non-root?

Some of your macports installations are installed as the root user, instead of the macports user. This happened because there is no installer for 10.6-ppc to automatically create the macports user. You have an open ticket about this too, where I pointed to the commands to be run to generate

How to snapshot debian

What's a relialble way to snapshot debian installations? Ken

thank you for the arm64 sonoma buildbot, Ryan

I installed fresh copy of the 2.9 base beta and then all new ports -- and it is just ripping along now that many of them are already built. Appreciate all your efforts keeping that going ... must be a ton of work. Ken

Re: Support for unreleased beta apple operating systems (was Support for ancient machines and operating systems)

I think you just don't realize the wreckage you've done. Here is one of hundreds of your typical commits, although this is a simpler one than most, to be honest. The commit below has no purpose other than to allow the port to build as PPC on 10.6. And as that is really only of interest on

Support for unreleased beta apple operating systems (was Support for ancient machines and operating systems)

There is no hiccup in MacPorts support for PowerPC systems, despite the dramatic title of the PR. Also there is no hiccup in support for older released Apple operating systems. 10.4 and 10.5 remain fully supported by MacPorts (although 10.4 might be on last legs). There is also no need (IMHO)

Key universal build failures

One of MacPorts' most significant differences from the other available package mangers is it's preserved support for universal building. It is perhaps the most impressive feature that MacPorts offers that the other package managers do not (AFAIK). However, at present, there are several core

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

c >> [ 91%] Building CXX object CMakeFiles/primesieve.dir/src/app/cmdoptions.cpp.o >> [ 93%] Building CXX object CMakeFiles/primesieve.dir/src/app/help.cpp.o >> [ 95%] Building CXX object CMakeFiles/primesieve.dir/src/app/main.cpp.o >> [ 97%] Building CXX object CMakeFi

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

Someone can make a port for this, but here you are for a quickie, to show you how this is done: % sudo port install cmake % git clone --depth=1 https://github.com/kimwalisch/primesieve % cd primesieve % mkdir build % cd build % cmake .. % make % ./primesieve 100 --count --print 2 3 5 7 11 13

Re: Sonoma Apple Silicon build machine

no Sonoma arm64 builder yet:build.macports.org

Re: What are the current available browser options for debian-ppc64?

Hi Adrian, I’m getting stuck building firefox, and as you’re building it already, how do we get past this? thanks, Ken I did this: $ apt-get build-dep firefox $ apt source firefox $ apt install python-is-python3 $ cd firefox-120.0 $ dpkg-buildpackage -us -uc but I keep getting this: ——

Re: What are the current available browser options for debian-ppc64?

I added an 8GB swapfile, and (slowly) got this backtrace: # cat error.txt Thread 1 "firefox" received signal SIGSEGV, Segmentation fault. i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146 146 rlbox.wasm.c: No such file or directory. (gdb) bt #0 i32_load8_u (addr=2014643200, mem=) at

Re: What are the current available browser options for debian-ppc64?

Trying to run firefox under gdb with the debug symbols installed appears to result in an out-of-memory situation on my DualG5 with 3.5GB ram, I’m afraid. Perhaps someone else has a system with more memory, or set up better than mine, that could help. Ken - $ gdb firefox GNU gdb (Debian

Re: What are the current available browser options for debian-ppc64?

aul Adrian Glaubitz > wrote: > > Hello! > >> On Mon, 2023-11-20 at 15:39 -0800, Ken Cunningham wrote: >> on my system I had another segfault, in libxul. > > A more detailed backtrace would be useful. libxul is basically all of > Firefox, so referring to

Re: What are the current available browser options for debian-ppc64?

> On Nov 20, 2023, at 12:37 PM, Jeffrey Walton wrote: > > On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham > wrote: >> >> On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote: >> >>>> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen &g

Re: What are the current available browser options for debian-ppc64?

On 2023-11-20, at 3:21 PM, John Paul Adrian Glaubitz wrote: > On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote: >> Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder >> whether >> it might be fixed by this particular patch [3]. > > I have rebuild

Re: What are the current available browser options for debian-ppc64?

On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote: > Hello! > >> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen wrote: >> >> Firefox does not work. > > Did you try the latest version 119? > > If there is a patch which fixes the crash on big-endian targets, we could > include it in

Re: What are the current available browser options for debian-ppc64?

is no doubt sinful: ln -s libffi.so.8 libffi.so.6 Ken > On Nov 19, 2023, at 4:48 PM, DistroHopper39B Business > wrote: > > SeaLion (https://github.com/wicknix/SeaLion > <https://github.com/wicknix/SeaLion>) is the best choice for PowerPC. > > On Sun,

What are the current available browser options for debian-ppc64?

I am aware of a few projects out there working to try to keep a repackaged TenFourFox going that have *.deb archives available, and I think there are some official channels for a few different browsers inside debian (Firefox, Epiphany). Does anyone have or know about a browser they use on

Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)

> On Nov 4, 2023, at 4:51 PM, Ken Cunningham > wrote: > > So to clean that up: > > sudo port -f uninstall perl5 perl5.36 > > and then: > > sudo port -f install perl5 That last line should have been: sudo port -v install perl5 K

Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)

MacPorts current "default" perl is perl5.34. I tooks like you have manually installed perl5.36 and there is no need for perl 5.36, so you could uninstall that if you care to. Everything else is pegged to perl 5.34 currently, except your "perl5" port which must have manually been installed with

Re: Help with legacysupport PortGroup for building GIMP for older MacOS's

Building and using legacysupport on a newer system to target an older system is tricky to design and implement properly. I think it is possible to do it, but issues will probably arise that only show up at deployment time. If I wanted to deploy gimp to 10.13, I would set up a 10.13 VM in

Re: [Pan-users] good non-gui test of functionality for homebrew?

> On Oct 25, 2023, at 2:10 AM, Dominique Dumont wrote: > > On Sunday, 22 October 2023 23:08:40 CEST Ken Cunningham wrote: >> It works well, but the homebrew devs would like to see a test that can be >> automatically run by the CI system to show that the built &am

[Pan-users] good non-gui test of functionality for homebrew?

Hi there, After using pan for a few years, I thought I would put together a formula for homebrew to make it more easily available. It works well, but the homebrew devs would like to see a test that can be automatically run by the CI system to show that the built & installed but never

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

There was a time when the only version of gcc that built on arm64 was gcc-devel/libgcc-devel. So ports put a specific dependency on that on arm. This was a long time ago now. It got things built. Then various gcc versions came out, gcc-12, gcc-13 that would build on arm64 (with extra patches,

Re: Xcode PortGroup: Xcode compiles code twice?

the xcode portgroup has always done this. it builds everything in the build phase, and then builds everything again in the destroot phase. we have discussed this over the years and the previous conclusion was that this was completely unavoidable, and we’d just have to live with it. sometimes

Re: VLC for PowerPC: make a separate port or modify existing?

orks.On Sat, Aug 5, 2023 at 7:02 AM Ken Cunningham <ken.cunningham.web...@gmail.com> wrote:For playing videos on older systems, I think MPlayer is the way to go.Give that a try if you haven't.KenOn 2023-08-04, at 3:57 PM, Sergey Fedorov wrote:I need an advice.We got VLC2 port (which is totall

Re: VLC for PowerPC: make a separate port or modify existing?

rov wrote: > > Don’t worry, I will not submit a PR for VLC unless it actually works with > video. There is no point otherwise. > > If it does not, I just leave it. But for now it still makes sense to have an > idea what to do with the port IF it works. > > On Sat,

Re: VLC for PowerPC: make a separate port or modify existing?

For playing videos on older systems, I think MPlayer is the way to go. Give that a try if you haven't. Ken On 2023-08-04, at 3:57 PM, Sergey Fedorov wrote: > I need an advice. > > We got VLC2 port (which is totally broken for all systems) and VLC port, > which installs pre-built binary.

Re: Go Ports: Update PG to Ensure Ports Aren't Built if Version Required Not Available

The last time I looked at this, go had moved on to use newer features of the Security.Framework that couldn't be duplicated for older systems, so it was stuck at an older pegged version. I see here and there that some folks have managed to get newer versions of the Security.Frameworks from

macports-legacy-support PR 61 could be the end of Tiger support for MacPorts....

Some interested users discovered a deficiency in a part of legacy-support’s fdopendir implementation, and have come up with a fix. due to the way the system on 10.4 works, however, it looks like this fix will not work on Tiger. Unless someone comes up with a trick for this, this could be the

Re: SDL2 for older systems: which components we need enabled? Cocoa vs X11

gt;  > P. S. I wonder now if the current SDL2 gonna build with X11 backend and Cocoa > off. Given that upstream concentrated efforts on skillfully breaking Cocoa > beyond repair, everything else might be intact. >> On Jul 20, 2023 07:15 +0800, Ken Cunningham >> , wrote: >

Re: SDL2 for older systems: which components we need enabled? Cocoa vs X11

As far as I know, we don't have any ports that use SDL2 via X11/Xquartz. All the ports use the Cocoa interface. The modifications that were made to SDL2 by miniupnp to run on Tiger and Leopard were fairly extensive, to an older version of SDL2, but they worked to allow a number of ports that

Re: rldicl / rldicr for 32-bit powerpc?

Adding it into cctools for the standard assembler to use whenever it might be needed would be something of a project, to be sure... However, patching it into a source file that needs it on a case-by-case basis is probably a fairly trivial thing to do. > On Jul 15, 2023, at 11:45 AM, Sergio

3272 R supporting ports ...

Although I am truly awed by the amount of effort it required to generate this many portfiles from the CRAN network, I'm curious how we are going to try to keep this many R supporting ports even marginally up to date with their various intertwined updates, dependencies, etc. Without some kind

Re: Can gcc13 create fat binaries for Intel+ARM in one-liner?

The necessary parts Apple added (driverdriver.c) to enable that have not been updated since gcc-4.2, so one-pass universal is not available since then. People occassionaly talk about updating driverdriver.c, and there are a few shell scripts floating around that do some of it, but that’s as far

Re: best Xcode version for Mojave?

On 2023-06-12, at 7:25 PM, Richard L. Hamilton wrote: > "On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or later but you have > Xcode 10.3." > > 11.3.1 is the newest Xcode for Mojave. > > Is there any known downside to Xcode 11.3.1 on Mojave rather than the 10.3 I > have on there now?

Re: Exa port dependencies

I have long thought the doc variants should never be the default. Lots of bloat and extra deps and build errors. But I know others feel differently. I know I can set -doc in variants.conf, but then you’re building everything. K > On Jun 9, 2023, at 04:01, Joshua Root wrote: > >  >> >>

Re: Portfile question for 10.6.8

> On Jun 6, 2023, at 6:28 PM, raf via macports-users > wrote: > > On Wed, Jun 07, 2023 at 11:09:13AM +1000, raf via macports-users > wrote: > >> Yay! It worked. Many thanks. I'll fix my Makefile for the upcoming version >> of rawhide and create the Portfile for that. > > I spoke too

Re: Portfile question for 10.6.8

> On Jun 6, 2023, at 6:16 PM, raf via macports-users > wrote: > > On Wed, Jun 07, 2023 at 11:09:13AM +1000, raf via macports-users > wrote: > >> So if I use different macro names (e.g. ALL_CFLAGS and ALL_LDFLAGS), and just >> add $(CFLAGS) and $(LDFLAGS) from the environment to it, then it

Re: Portfile question for 10.6.8

it looks like the legacy support library is not being included in the link. This is common when only scripts are used, as there are many flags that might not be considered. If you run the build on 10.6 using some extra verbosity flags like "-d" it will show you all the ENVVARs and LDFLAGS etc

Re: gcc12 fault?

> On Jun 1, 2023, at 6:18 PM, Joshua Root wrote: > > Ken Cunningham wrote: > >> what you see is difficult to explain, unless the PATH changed between the >> two tests. >> >> if >> >> 'which gcc' gives /opt/local/bin/gcc >> >> t

Re: gcc12 fault?

what you see is difficult to explain, unless the PATH changed between the two tests. if 'which gcc' gives /opt/local/bin/gcc then gcc --version should give exactly the same as /opt/local/bin/gcc --version Now you know that /opt/local/bin/gcc will not actually exist, unless you have

Re: Fork of current version of »hfs« package

:37 PM, John Paul Adrian Glaubitz wrote: > On Tue, 2023-05-30 at 13:53 -0700, Ken Cunningham wrote: >> The blocksruntime library is easy to build and available broadly, >> in case just including it becomes the easier path. >> >> http://ftp.debian.org/debian/pool

Re: Fork of current version of »hfs« package

The blocksruntime library is easy to build and available broadly, in case just including it becomes the easier path. http://ftp.debian.org/debian/pool/main/libb/libblocksruntime/libblocksruntime_0.4.1.orig.tar.gz Ken On 2023-05-30, at 1:48 PM, John Paul Adrian Glaubitz wrote: > Hi Lennart!

Re: [MacPorts] #66723: pcre2 @10.42: no such instruction: `lzcnt %eax, %eax'

Everything is always open for discussion, being an opensource, volunteer project, for sure. We may never do what I suggested, or perhaps some variation of it. Someone may want to keep around clang-3.4 or 3.7 for some reason. I just look for the simplest, most direct approach. gcc10-bootstrap is

Re: Wine

est version on MacPorts really that old, or am I misunderstanding > something? > > Thanks > > Andre > >> On Apr 30, 2023, at 14:39, Ken Cunningham >> wrote: >> >> You probably won't want to build it, though. >> >> Dean uses MacPorts to bui

Re: Wine

You probably won't want to build it, though. Dean uses MacPorts to build wine, and then makes the binaries available here: https://github.com/Gcenx/macOS_Wine_builds/releases/ Homebrew just downloads and installs the premade binaries that are made by Dean's MacPorts overlay. These are

Re: Cannot build glib2

FYI I have had good luck with opencore legacy patcher on several machines. A macbookpro 9,2 can run the current Ventura, for example, very nicely (upgraded to 16GB Ram). Some machines don't fare as well -- a macbookpro 9,1 I tried to upgrade struggles. K On 2023-04-18, at 11:17 AM, Eldrid

Re: meson and NM

> On Apr 17, 2023, at 4:43 PM, Riccardo Mottola > wrote: > > Hi Ken! > > hmm... somehow your email got garbled? It is without subject and I cannot > relate.. but I think I got it. > > > Ken Cunningham wrote: >> meson is now more picky about unrecogni

Re: Cannot build glib2

if glib2 now links against dbus (and it seems at least one test does) then dbus will need to be added to the build deps of glib2 so that macports can work out the architecture matching needed to prevent this. I can't see any indication that any of the installed glib2 files link against dbus,

Re: compiling ArcticFox on 10.11 - atomic not found, cxx11

$ cat atomic.cxx #include int main(void) { return (0); } $ clang++-mp-9.0 -stdlib=libstdc++ atomic.cxx atomic.cxx:1:10: fatal error: 'atomic' file not found #include ^~~~ 1 error generated. $ clang++-mp-9.0 -stdlib=macports-libstdc++ atomic.cxx h$ clang++-mp-9.0 -stdlib=libc++

[no subject]

meson is now more picky about unrecognized arguments. This will have to be removed, and then making sure it uses the right NM might have to be done another way: lt_cv_path_NM=/opt/local/bin/nm > *info:configure meson: error: unrecognized arguments: >

Re: MacBook broken GPU workarounds

I disassembled my MacBookPro 2,1 and baked the motherboard in the oven for 8 minutes at 350F (IIRC), supported on some pyramids of tinfoil. It worked for another 1.5 years after that, but then died again and that was enough for me. I removed all the useful parts from it and moved on, giving it

Re: Installer doesn't find the mirrors

Your issue is in French, but it looks like the one I recently faced as well if I am reading it correctly. I fixed it using the information on this page: https://unix.stackexchange.com/questions/75807/no-public-key-available-on-apt-get-update I hope this helps you too. Ken > On Apr 9,

Re: Setting environment and support of older OS/arch

You can also look into how to use pkgconfig and cmake to find needed libraries. They can suffice for simpler header and library path additions, and often that might be all you need for a simpler project with just one or two things needed. K

Re: Setting environment and support of older OS/arch

If you are doing your own compilation using the compilers and libraries from MacPorts, you need to direct your build to use the specified tools, headers, and libraries. You can look at what MacPorts sets up itself for each build for a clue, for example this is setup for a generic build of

some jackass hosed the wikistart page

don't recognize the username

Re: For anyone looking for a worthy project -> not one of the boost ports can build universal x86_64/arm64, which prevents a lot of ports from building universal

building boost 176 universal on my M1 bogs down in the selection of the assembly context files. All the correct assembly files are not included, so the link phase fails. It looks fixable, but have to sort out how to get them right.

Re: For anyone looking for a worthy project -> not one of the boost ports can build universal x86_64/arm64, which prevents a lot of ports from building universal

thanks, that looks like a good start !

For anyone looking for a worthy project -> not one of the boost ports can build universal x86_64/arm64, which prevents a lot of ports from building universal

just thought I'd point that one out, for interested folks. Best, Ken

Re: libgcc11 failed build failed on macOS 13.0.1

On Ventura arm64, libgcc11 is not part of the youtube-dl dependency tree. You can use: port rdeps youtube-dl so see what is on the tree. I can install youtube-dl without any trouble. % port -v installed youtube-dl The following ports are currently installed: youtube-dl

Re: Legacy Support for GHC-Based Projects

of a project. The cabal config file needs some interesting additions to make everything work and force the system libs... Hope this is useful. Perhaps it might be used as a binary at least, until things are further sorted. Ken > On Jan 28, 2023, at 6:57 PM, Ken Cunningham > wrote: &

Re: ports website says port has been deleted ... but it is there.

oh, maybe it’s because the ports installation of macports does not accept the extract.rename option yet because it hasn’t been updated yet… K > On Feb 3, 2023, at 07:55, Ken Cunningham > wrote: > > Perhaps because the buildbots are down? Not sure why else this would say

ports website says port has been deleted ... but it is there.

Perhaps because the buildbots are down? Not sure why else this would say the port is deleted.. https://ports.macports.org/port/codeblocks-devel/ but here it is: https://github.com/macports/macports-ports/blob/master/devel/codeblocks-devel/Portfile Ken

Re: Legacy Support for GHC-Based Projects

ied > stack as the build tool: https://trac.macports.org/ticket/66764 > > Back to cabal. > >> On Jan 25, 2023, at 11:29 AM, Ken Cunningham >> wrote: >> >> Stack from MacPorts doesn’t build on snow leopard, and I don’t recall it >> ever built in previous years

Re: Legacy Support for GHC-Based Projects

’t stack-based pandoc also build back to Snow Leopard? Is this a > MacPorts issue or a Haskell-world issue? > >> On Jan 24, 2023, at 11:56, Ken Cunningham >> wrote: >> >> At least some of the buildbot ghc builds might be fixable — one of them >>

Re: Legacy Support for GHC-Based Projects

At least some of the buildbot ghc builds might be fixable — one of them failed due to a missing png-config I believe, for example. Because of the way upstream builds ghc on macos, their older system support has become more limited. They use homebrew, and current systems, with an older

Re: GIMP Quartz broken on 10.7, perhaps gtk

; > On 2023-01-12 14:12:38 +0100 Ken Cunningham > wrote: > >> My guess would be to look at harfbuzz…make sure our patches there still >> make sense, run the test suite. It can be touchy, different compilers can >> change test results, etc. >> >>

Re: GIMP Quartz broken on 10.7, perhaps gtk

n gtk3 is built with the quartz backend (on 10.7 at least), so that is unfortunate. Ken > On Jan 12, 2023, at 5:12 AM, Ken Cunningham > wrote: > > My guess would be to look at harfbuzz…make sure our patches there still make > sense, run the test suite. It can be touchy, differe

Re: GIMP Quartz broken on 10.7, perhaps gtk

My guess would be to look at harfbuzz…make sure our patches there still make sense, run the test suite. It can be touchy, different compilers can change test results, etc. To disable one port in an overlay with minimal fuss, rename to Portfile to something else (I use Portfile.disabled), and

Re: GIMP Quartz broken on 10.7, perhaps gtk

The default x11 installation of gimp works perfectly. I know that is not the version you want, you want the +quartz version. But there’s a data point, at least, and a likely clue as to where to look for the issue with font rendering. Ken > On Jan 8, 2023, at 2:24 PM, Ken Cunning

Re: GIMP Quartz broken on 10.7, perhaps gtk

I see the same thing on a fresh gimp2 install +quartz on 10.7 (one very tiny patch needed to gimp2 to change NULL -> 0 to keep clang-15 happy, otherwise a no-touch build). However, there is no text drawn on any gimp2 windows or dialog boxes, as you noted. Installing pan2 +quartz +gtk3, I see

Re: Location to store Rust binaries

Here is a commit where I installed a binary from the packages server onto a different system than it belonged to. Something similar might work to install the 10.9 binary of rust-bootstrap on 10.5 through 10.8…

Re: Location to store Rust binaries

although the 10.9 one needed has not as yet been built it seems.You would also have to manually access and download the 10.9 binary on older systems, as the automatic mechanism to install it wouldn’t work where it’s needed.KOn Dec 22, 2022, at 05:02, Ken Cunningham wrote:they are thereIndex

  1   2   3   4   5   6   7   8   9   10   >