[Numpy-discussion] help from OS X 10.5 users wanted

Russell E. Owen rowen@uw....
Fri Oct 15 12:54:30 CDT 2010


Sorry I missed this thread until just now. I think you have it under 
control, but for the record I have a 10.4 Intel machine I keep around 
for the sole purpose of building backward-compatible binary installers 
for PIL and matplotlib. If help is still wanted I'm happy to build numpy 
as well.

I did this because I was not able to figure out how to build matplotlib 
or PIL on 10.5 or 10.6 in such a way that it would run on older Macs. (I 
made static universal libraries for their dependencies, using the 10.4 
SDK, but somehow that was not enough).

So I'm not surprised you are having problems.

Note that the Mac Python 2.5 from python.org has some known issues with 
Tkinter so I never use it, but I could install it for this purpose (just 
not test it very easily) since numpy doesn't care about Tkinter.

-- Russell


In article <4CB5E208.5030909@noaa.gov>,
 Christopher Barker <Chris.Barker@noaa.gov> wrote:

> On 10/13/10 8:30 AM, Ralf Gommers wrote:
> >     For what it's worth, the posted binary seems to work fine on my OS-X
> >     10.5 PPC system (python2.6), so maybe the PPC part works, the Intel part
> >     not.
> >
> > Thanks, good to know.
> >
> >      > My conclusion is that binaries built on 10.6
> >      > do not work on 10.5 even when using the correct SDK and deployment
> >      > target.
> 
> It sounds like they work on everything except Intel 10.5 -- is that right?
> 
> >     Well, I still think if you do everything right, it works, but yes, it is
> >     a pain to get right, and a pain to test. Building on the oldest system
> >     you want to support is a lot easier.
> >
> > I don't think so - at least I have not been able to find a fix for the
> > error below in the many many bug reports one can find:
> >
> > ImportError?: dlopen(somefile.so, 2): no suitable image found. Did find:
> >
> >      somefile.so: unknown required load command 0x80000022
> 
> Well, there are two options now:
> 
> 1) keep trying to fix that error -- a post to the pythonmac list might 
> help there.
> 
> 2) Punt, and just build on an older system. It sounds like Vincent may 
> be able to help out with that.
> 
> (I've got a Intel 10.6 system and a PPC 10.5 system now, but I'll 
> probably lose the 10.5 one soon)
> 
> On 10/12/10 6:12 PM, Vincent Davis wrote:
> >>> install on 10.5 with binaries made on 10.6. So if I can learn
> >>> something and help others that is great.
> 
> Vincent -- if you are game, I suggest:
> 
> Set up a 10.4 system, install the python.org 2.5, 2.6 and 32bit 2.7 
> binaries.
> 
> On that, build:
> 
> >> Python 2.5: 32-bit PPC/i386 for Mac OS X 10.3.9 through 10.6
> >>
> >> Python 2.6: 32-bit PPC/i386 for Mac OS X 10.3.9 through 10.6
> >>
> >> Python 2.7 32-bit PPC/i386 for Mac OS X 10.3.9 through 10.6
> 
> On a 10.5 system, build:
> 
> >> Python 2.7 PPC/i386/x86-64 for Mac OS X 10.5 or later
> 
> As for Python 3k -- I have no idea!
> 
> I might be able to do the 10.5 builds -- but I don't know for how long.
> 
> Do you have the machines (or VMs) to do that?
> 
> Thanks so much!
> 
> NOTE: are there buildbots somewhere that could be used for this?
> 
> -Chris



More information about the NumPy-Discussion mailing list