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

List:       pythonmac-sig
Subject:    Re: [Pythonmac-SIG] bdist_mpkg issues
From:       Christopher Barker <Chris.Barker () noaa ! gov>
Date:       2010-09-16 23:31:21
Message-ID: 4C92A8C9.1000503 () noaa ! gov
[Download RAW message or body]

Russell Owen wrote:
> I'll expect our observatory to send me a 10.4 Mac in a few weeks. I plan 
> to build the packages on that -- both to assure that the packages will 
> run on 10.4 and as a way of testing my released application.
> 
> I'm sure the gcc will be rather outdated, but I hope it will be tolerable.

I was having pretty good luck with my 10.4 system when I still had a a 
couple months ago.

> All that said, I sure wish I knew what was wrong. bdist_mpkg is not 
> getting any attention and at some point it may just break, leaving us 
> with no obvious way to build binary installers.

well -- I don't think it does all that much, and the only tricky part 
should be what's also used in py2app, so it may not be that bad.

I suspect the problem is with binary libs, not with bdist_mpkg.

-Chris



> Regards,
> 
> -- Russell
> 
> On Sep 16, 2010, at 2:06 PM, Christopher Barker wrote:
> 
>> Russell E. Owen wrote:
>>> At your suggestion I built new universal unix libraries using 
>>> MACOSX_DEPLOYMENT_TARGET=10.3. As always, I deleted the dylibs so 
>>> only the static libraries remained (so they would be included in the 
>>> final binary) and I verified that the libraries contained both ppc 
>>> and intel code. I then used bdist_mpkg to build a matplotlib 
>>> installer. Unfortunately I see the same problem as before: when I try 
>>> to import pylab on a 10.3.9 PPC computer I get a segfault.
>>
>> Darn.
>>
>> Is there any simple test code we could use to test the libraries them 
>> selves? It would be nice to maybe build a really simple executable 
>> that uses each of the dependencies, so they could be individually 
>> tested. At least that would narrow down the issue.
>>
>> It also should be possible to run it under a debugger or something, so 
>> that we could see where the segfault occurred -- anyone know how to do 
>> that?
>>
>> -Chris
>>
>>
>>
>>
>> -- 
>> Christopher Barker, Ph.D.
>> Oceanographer
>>
>> Emergency Response Division
>> NOAA/NOS/OR&R            (206) 526-6959   voice
>> 7600 Sand Point Way NE   (206) 526-6329   fax
>> Seattle, WA  98115       (206) 526-6317   main reception
>>
>> Chris.Barker@noaa.gov
> 


-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker@noaa.gov
_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
[prev in list] [next in list] [prev in thread] [next in thread]