Hi,
up to now I didn't subscribe to "macports-dev" mailing list, even if I
use and collaborate in MacPorts for years!
Questions about bugs (e.g. discussions similar to track) belong to which
list best? Is "dev" only for "macports" itself or also for the ports in it?
I thought the former,
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 Leopard... intel first,
they were working well enough to get gimp starting up (gtk2...)
The only other GTK3 app I use is meld, which is now
Hi,
Sergio Had wrote:
Could you refer me to the beginning of this discussion please?
it started on the Mac Users mailing list, you can find in the archives!
I am also involved in AF project:)
Oh, I am curious, how?
I am essentially the only active developer currently, except Roy who
Hi,
Joshua Root wrote:
(Moving to macports-dev as it is a better fit for this topic.)
indeed, it is a development issue, although well, not for a MacPorts
package (yet?) but use of MP development tools.
Issues that only appear at higher optimisation levels also often
involve undefined
Hi,
after all the talk about gcc versions, I tried to build gcc 8 here.
Officially it says "gcc8 is known to fail".
I first did just "build" on Intel 64bit and PPC 32bit - Intel 32bit
later, I fear my MacBook has fan issues.
Intel 64bit finished build! Took several hours. I thus tried to
Hi,
I actually agreed with you, just skip from gcc7 to gcc13.
Ken Cunningham wrote:
Just yesterday I fixed gcc10-bootstrap to build on Tiger PPC and pushed that to
master, which required YA new bootstrap compiler. So the parts are now in place
for the attempt.
ohhh :) it took me 4 days to
Hi,
Ken Cunningham wrote:
My only question is whether to skip over gcc8-12, or include them.
If we skip over gcc8-12, we can probably have a new release that uses
gcc13 as the primary gcc on all systems in macports done by Monday.
Less maybe. Last time I jumped the version, it took me an
Hi,
Sorry - I missed these replies, ended up in the wrong mail folder. Was
about to re-write!
We had discussions in many points, tickets, ecc... lots of different
opinions.
Sergio Had wrote:
You should not need gcc8. I had gcc11 working on 10.5 ppc (and ppc64
too). I have seen people
Hi,
Ken Cunningham wrote:
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 a questionable benefit.
on my PowerMac dual-G4 about a week of compilation, given the time to
build gcc8...
But I understand we
Hi,
Ryan Schmidt wrote:
I propose to keep even versions, because they are stable ones
Do you have a source for this claim? It's the first I've heard of it. As far as
I know, all gcc version numbers are stable.
I did a quick search and couldn't find one. It is something I pked up
years
Hi,
I just noticed this on 10.5 intel 64bit... Often I don't check the
console so I don't know if it is fresh.
Artax:~ multix$ wget
https://github.com/macports/macports-ports/archive/70b148d6b0c465b2483ca2d6f9a12fb0841d639e.zip
wget(77577) malloc: *** error for object 0x7fff7020c200:
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 systems, and then newest supportable (3.28.4) for 10.7
> and < 10.6.
>
I deactivated cmake and installed cmake-devel as test on
Hi,
I use meld to compare and develop, especially ArcticFox against full
Gecko tree. I don't know if there are alternatives, but it proves to
handle big trees and also complicated compare details. However, it is
highly complex in its dependencies being in python, gtk3 and related.
There was a
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 needed
... time will tell.
for me it is gcc48 (or apple 4.2 on tiger or such) for old software.
gcc6 covers most
Hi,
Kirill A. Korinsky wrote:
I really doubt that anyone care about of macOS 10.6 these days with
exception for a few folks in the world, and probably half of them read this
mail list:)
But propose a patch for git isn't bad idea, indeed.
I care for 10.5 and 10.6, but I read this mailing list
Hi,
I have a situation where I am unable to upgrade cleanly on my MacBook,
took me a bit to realize.
In the past, I had a complete systems, maybe also helped to have Ken's
ports overlay.
While doing upgrade, I am stuck on several rebuild failures (not
installing anything new). One is:
Hi,
Sergey Fedorov wrote:
Some on MacRumors, for instance; quite likely that those who are on
KDX and Hotline also run those on 10.4–10.5, though I have no
statistics on that.
this is a little off-topic and gave me a little tear. Hotline and KDX
were my thing many years ago, like more than
Hi!
Kirill A. Korinsky wrote:
Keep in mind that suggested method removes support osx keyring from that
system. User still be able to use SSH-based auth or enter password by hand
for HTTP-based push.
My point: I assume that nobody uses HTTP-based auth on git on 10.5 and 10.6,
I do not assume
18 matches
Mail list logo
