I understand from the zlib's SPKG.txt that OSX-specific thing was done by Michael Abshoff, who has left the project.
When you talk about "developing on OSX", there is a zillion possible, and quite different from each other, building environments * native Apple * Fink * MacPorts which all have their own quirks and features that might make the thing developed under them still in need of porting to Sage. Best, Dima On Feb 14, 7:17 am, "Dr. David Kirkby" <[email protected]> wrote: > The zlib package has been hacked quite a bit to generate a 64-bit shared > library > on OS X. My attempts to do likewise on Solaris failed, as though I could > generate a static library, I could not do so with a shared library. > > I contacted the zlib developer (Mark Alder), gave him access to 't2' and an > OpenSolaris machine of mine. He has fixed this. > > The latest beta can be found athttp://zlib.net/current/beta/ > > and will build 64-bit on OpenSolaris and Solaris 10 on SPARC. > > He is very surprised that it was necessary to hack the code at all on OS X, as > he does all his development on OS X, and said it should build 64-bit by > default, > and one need to add the -m32 switch to get it to build in 32-bit mode. > > The zlib package needs updating for Solaris, but it would be sensible if we > could double check the OS X situation, as he is confident no hacks should be > necessary at all. > > Mark's standard build machine is OS X, and all zlib development is done on OS > X, > so it should be more reliable on OS X than anything else. > > Does anyone know why the zlib package was hacked so much in Sage to work on OS > X? There is a completely new configure script in the Sage package, which is > specific to OS X, so the changes are not small. > > Dave -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
