Re: [Pytables-users] symbol not found _H5T_STD_I64LE_g

[Tony T. <to...@lo...>]

On 27 May 2010 09:43, Brett Calcott <bre...@gm...> wrote:
>
>
> On 27 May 2010 00:57, Brandt Belson <bb...@pr...> wrote:
>>
>> Thanks for your help. I followed your directions. First, I checked the
>> file type of python (which I installed from python.org):
>> $ file /Library/Frameworks/Python.framework/Versions/2.6/bin/python
>> /Library/Frameworks/Python.framework/Versions/2.6/bin/python: Mach-O
>> universal binary with 2 architectures
>> /Library/Frameworks/Python.framework/Versions/2.6/bin/python (for
>> architecture ppc): Mach-O executable ppc
>> /Library/Frameworks/Python.framework/Versions/2.6/bin/python (for
>> architecture i386): Mach-O executable i386
>> I assumed this was the first case you mentioned.
>
> Actually, It looks like the second case to me, not the first. You've got a
> universal build with 3 archs, no a single i386 arch (you have a default snow
> leopard python install, right?) That is what I've got, and it builds and
> works ok when the python "defaults" are set to use 64-bit. If I change it to
> run a 32-bit python, I get a "Symbol not found" message (though not the same
> one as you).

It's closer to the first since it's a non-Apple version and there's
only one arch that can be executed (I'm not even going to think about
trying to get a ppc running through Rosetta!). It resembles the second
since it looks like some 64-bit attempts need to be back tracked.

> I spent a lot of time getting it to run on my Snow Leopard install. It
> worked eventually, but I never understood the details. My best guess (could
> be wrong) was this:
> - hdf5 is NOT set up for a universal build. For some discussion of this have
> a look here http://www.kyngchaos.com/macosx/build/hdf. So, by default it
> just build as one arch (I think the default is 64-bit).
> - Whatever arch it is built with will be the only arch it will work with in
> python.
> - So you need to match the 1 arch of hdf5 lib with the arch of the python
> you are running.

That's a nice summary.

> You tried building 4 different times, but did you test each of this with
> both a 32-bit and a 64-bit python?
> ie:
> defaults write com.apple.versioner.python Prefer-32-Bit -bool no
>> python  etc etc
> defaults write com.apple.versioner.python Prefer-32-Bit -bool yes
>> python  etc etc

The python being used is only 32-bit, so that shouldn't have any impact.

> If you already did this, then I'm stumped too...
> Brett

The only thing I can think is that it's somehow finding the original
hdf5 build at runtime.

Tony