I plan to install Leopard sometime this weekend. So, what's the scoop with 10.5 and MacPorts? How many ports work? How many are busted? I see individual Trac entries but no overarching set of information about this. Cheers, Dave
On 10/24/07, Dave Peck <o-macports@delver.org> wrote:
I plan to install Leopard sometime this weekend.
So, what's the scoop with 10.5 and MacPorts?
How many ports work? How many are busted? I see individual Trac entries but no overarching set of information about this.
Cheers, Dave
On one of the last Developer Seeds, I had a problem building ruby with Macports. I believe Ruby Segfaults during its testing phase. I'm hoping that these will be found and squashed fairly quickly. Do any of the committers have access to Leopard? Or are planning on getting Leopard Friday? Patrick
On Oct 24, 2007, at 16:56, Dave Peck wrote:
I plan to install Leopard sometime this weekend.
So, what's the scoop with 10.5 and MacPorts?
How many ports work? How many are busted? I see individual Trac entries but no overarching set of information about this.
We don't have that information for Leopard, or for Tiger or Panther or any other OS in fact. If you find busted ports, on any OS, file tickets. That's the situation we have at this point.
On 25 oct. 07, at 00:02, Patrick Burleson wrote:
On one of the last Developer Seeds, I had a problem building ruby with Macports. I believe Ruby Segfaults during its testing phase. I'm hoping that these will be found and squashed fairly quickly.
The reason Ruby segfaults during build on Leopard is explained here: <http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12895> "In Leopard, the setcontext/getcontext functions have been modified to confirm to the UNIX norm, however, their implementation changed to not use the default structure by default, which makes Ruby segfaulting during initialization." Apple has offered their patches upstream, so to build Ruby from sources on Leopard you either have to apply the patches manually or wait for them to be merged to the Ruby source tree. -- Luc Heinrich
On 10/25/07, Luc Heinrich <luc@honk-honk.com> wrote:
On 25 oct. 07, at 00:02, Patrick Burleson wrote:
On one of the last Developer Seeds, I had a problem building ruby with Macports. I believe Ruby Segfaults during its testing phase. I'm hoping that these will be found and squashed fairly quickly.
The reason Ruby segfaults during build on Leopard is explained here: <http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12895>
"In Leopard, the setcontext/getcontext functions have been modified to confirm to the UNIX norm, however, their implementation changed to not use the default structure by default, which makes Ruby segfaulting during initialization."
Apple has offered their patches upstream, so to build Ruby from sources on Leopard you either have to apply the patches manually or wait for them to be merged to the Ruby source tree.
Thanks for that link. Nice of Apple to post those patches with only a day remaining, but hey, I guess patches is better than no patches. My other option is to grab those patches myself and edit the port file until they get merged with the 1.8 code. I'll have to keep an eye out for that. It's a good thing I'm not immediately upgrading to Leopard, so that maybe by the time I do, this will all be resolved.
participants (4)
-
Dave Peck
-
Luc Heinrich
-
Patrick Burleson
-
Ryan Schmidt