[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-dev
Subject:    Re: cmake-devel --> cmake coming .... please test if you care to
From:       Sergio Had <vital.had () gmail ! com>
Date:       2024-03-27 13:51:38
Message-ID: 45DEB4D5-E802-4284-BAA6-BA71ECC35F9F () gmail ! com
[Download RAW message or body]

Just for the record, cmake-devel 3.29.0 works fine for me on native systems where \
3.28.1 was failing (10.6 ppc and 10.6 i386).

It does not build on 10.6.8 Rosetta, likely due to an unrelated issue, but this is \
not a stopper, since no one uses Rosetta outside of testing/development. If anyone \
happens to use Macports in Rosetta (I recall Kirill had such a set-up), the last \
version to work there is 3.28.4 from Ken's recent update to the port.


> On Mar 27, 2024, at 8:48 PM, Ken Cunningham <ken.cunningham.webuse@gmail.com> \
> wrote: 
> We sorted out a workaround for the failing systems that was incorporated upstream, \
> and after some further testing, updated the cmake port to the current version on \
> all systems. 
> Both cmake and cmake-devel are about the same now, so feel free to go back to the \
> main cmake port. 
> Tiger needs verification.
> 
> K
> 
> > On Mar 27, 2024, at 02:29, Riccardo Mottola <riccardo.mottola@libero.it> 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 systems, and then newest supportable (3.28.4) for 10.7
> > > and < 10.6.
> > > 
> > 
> > I deactivated cmake and installed cmake-devel as test on 10.5 intel
> > 64bit, 10.7, 10.11
> > 
> > Build when file on all systems. I think the best test is using it during
> > more upgrades... I don't remember off-hand which ports use to test.
> > I hope that w e don't get red-herrings of failures on other packages due
> > to that.
> > 
> > > 
> > > https://trac.macports.org/ticket/67540
> > > 
> > > If you are a keener with debugging on 10.7, and can sort out a proper
> > > fix for 3.29.0 on 10.7, upstream will love you. Most likely eventually
> > > we/they will use the commits they added to the 3.28.N branch to fix it
> > > for those systems, although those commits are more involved that we
> > > usually like to carry.
> > 
> > At a first glance I don't understand the issue, it looks like
> > compiler/linker gets confused. If you want... we can try to tinker on it.
> > 
> > Riccardo


[prev in list] [next in list] [prev in thread] [next in thread]