Re: [Pythonmac-SIG] bdist_mpkg issues

[Christopher Barker]

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.bar...@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.bar...@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

Re: [Pythonmac-SIG] bdist_mpkg issues

[Christopher Barker]

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.bar...@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

Re: [Pythonmac-SIG] bdist_mpkg issues

[Russell E. Owen]

In article ,
 Ned Deily  wrote:

> In article ,
>  "Russell E. Owen"  wrote:
> > I'm having some surprising issues with bdist_mpkg and I wondered if 
> > anyone had advice.
> > 
> > Problem building a PIL 1.1.7 binary installer for Mac OS X 10.3.9 and 
> > later:
> > * The PIL binary for Python 2.6 does not work on 10.3.9 or 10.4: the 
> > _imaging C library cannot be loaded.
> > * The Python 2.5 PIL does not have this problem - it works fine on 
> > 10.3.9.
> > * There are no problems on 10.5 and 10.6.
> > 
> > 
> > Problem building a matplotlib 1.0.0 installer for Mac OS X 10.3.9 and 
> > later:
> > * The resulting matplotlib segfaults on Mac OS X 10.3.9 for both Python 
> > 2.5 and 2.6.
> > * The Python 2.6 version has incorrect permissions for some data files.  
> > I know how to work around this but am puzzled why it is necessary.
> > * The Python 2.5 version has no permission problems.
> > 
> > 
> > My setup:
> > - Mac OS X 10.5.8 Intel system
> > - Python 2.5.2 and Python 2.6.6 both from python.org
> > - bdist_mpkg 0.4.4 (installed using pip)
> > - Build instructions for matplotlib:
> >  > l> (the procedure for PIL is similar).
> > 
> > I tried building on 10.3.9, but the gcc is so old that I get buffer 
> > overflow vulnerability warnings so I'm not keen to go this route. I'll 
> > have a 10.4 machine in a few weeks and I'll try that.
> 
> Quick thoughts without any testing: the python.org 2.6.6 uses a 
> MACOSX_DEPLOYMENT_TARGET=10.3.  Make sure you set it when building all 
> your dependent libraries, too.   Make sure you use CC=gcc-4.0 (default 
> on 10.5 but not 10.6) for all building.  Don't bother trying to build on 
> 10.3.9.  In theory, you should be able to make this work.  A standard 
> python installer can be built these days on any of 10.4, 10.5, and 10.6 
> that will work on 10.3.9 through 10.6 so there's a good chance that PIL 
> should be able to be built similarly.  No experience with matplotlib or 
> bdist_mpkg.

It is nice to think that a binary installer could be built on 10.5 or 
10.6 but I sure don't know how to do it.

I built the original installers using MACOSX_DEPLOYMENT_TARGET=10.4 and 
gcc 4.0.1.

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.

-- Russell

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG

Re: [Pythonmac-SIG] bdist_mpkg issues

[Ned Deily]

In article ,
 "Russell E. Owen"  wrote:
> I'm having some surprising issues with bdist_mpkg and I wondered if 
> anyone had advice.
> 
> Problem building a PIL 1.1.7 binary installer for Mac OS X 10.3.9 and 
> later:
> * The PIL binary for Python 2.6 does not work on 10.3.9 or 10.4: the 
> _imaging C library cannot be loaded.
> * The Python 2.5 PIL does not have this problem - it works fine on 
> 10.3.9.
> * There are no problems on 10.5 and 10.6.
> 
> 
> Problem building a matplotlib 1.0.0 installer for Mac OS X 10.3.9 and 
> later:
> * The resulting matplotlib segfaults on Mac OS X 10.3.9 for both Python 
> 2.5 and 2.6.
> * The Python 2.6 version has incorrect permissions for some data files.  
> I know how to work around this but am puzzled why it is necessary.
> * The Python 2.5 version has no permission problems.
> 
> 
> My setup:
> - Mac OS X 10.5.8 Intel system
> - Python 2.5.2 and Python 2.6.6 both from python.org
> - bdist_mpkg 0.4.4 (installed using pip)
> - Build instructions for matplotlib:
>  l> (the procedure for PIL is similar).
> 
> I tried building on 10.3.9, but the gcc is so old that I get buffer 
> overflow vulnerability warnings so I'm not keen to go this route. I'll 
> have a 10.4 machine in a few weeks and I'll try that.

Quick thoughts without any testing: the python.org 2.6.6 uses a 
MACOSX_DEPLOYMENT_TARGET=10.3.  Make sure you set it when building all 
your dependent libraries, too.   Make sure you use CC=gcc-4.0 (default 
on 10.5 but not 10.6) for all building.  Don't bother trying to build on 
10.3.9.  In theory, you should be able to make this work.  A standard 
python installer can be built these days on any of 10.4, 10.5, and 10.6 
that will work on 10.3.9 through 10.6 so there's a good chance that PIL 
should be able to be built similarly.  No experience with matplotlib or 
bdist_mpkg.

-- 
 Ned Deily,
 n...@acm.org

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG

Re: [Pythonmac-SIG] bdist_mpkg issues

[Russell E. Owen]

In article ,
 "Russell E. Owen"  wrote:

> I'm having some surprising issues with bdist_mpkg and I wondered if 
> anyone had advice.
> 
>...
> Problem building a matplotlib 1.0.0 installer for Mac OS X 10.3.9 and 
> later:
>...
> * The Python 2.6 version has incorrect permissions for some data files.  
> I know how to work around this but am puzzled why it is necessary.
> * The Python 2.5 version has no permission problems.

I tracked this down to having an older version of some dependencies of 
bdist_mpkg in my Python 2.5. I upgraded to the latest py2app and now 
both Python 2.5 and Python 2.6 show the problem with files that users 
can't read:

build/lib.macosx-10.4-fat-2.5/matplotlib/mpl-data//images:
total 520
-rw---  1 rowen  staff   1465 Jul  6 07:43 back.png
-rw---  1 rowen  staff   1741 Jul  6 07:43 back.ppm
-rwx--  1 rowen  staff   3064 Jul  6 07:43 back.svg
-rw---  1 rowen  staff   3434 Jul  6 07:43 back.xpm
-rw---  1 rowen  staff   1121 Jul  6 07:43 filesave.png
-rw---  1 rowen  staff   1741 Jul  6 07:43 filesave.ppm

-- Russell

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG

[Pythonmac-SIG] bdist_mpkg issues

[Russell E. Owen]

I'm having some surprising issues with bdist_mpkg and I wondered if 
anyone had advice.

Problem building a PIL 1.1.7 binary installer for Mac OS X 10.3.9 and 
later:
* The PIL binary for Python 2.6 does not work on 10.3.9 or 10.4: the 
_imaging C library cannot be loaded.
* The Python 2.5 PIL does not have this problem - it works fine on 
10.3.9.
* There are no problems on 10.5 and 10.6.


Problem building a matplotlib 1.0.0 installer for Mac OS X 10.3.9 and 
later:
* The resulting matplotlib segfaults on Mac OS X 10.3.9 for both Python 
2.5 and 2.6.
* The Python 2.6 version has incorrect permissions for some data files.  
I know how to work around this but am puzzled why it is necessary.
* The Python 2.5 version has no permission problems.


My setup:
- Mac OS X 10.5.8 Intel system
- Python 2.5.2 and Python 2.6.6 both from python.org
- bdist_mpkg 0.4.4 (installed using pip)
- Build instructions for matplotlib:
 (the procedure for PIL is similar).

I tried building on 10.3.9, but the gcc is so old that I get buffer 
overflow vulnerability warnings so I'm not keen to go this route. I'll 
have a 10.4 machine in a few weeks and I'll try that.

-- Russell

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG