visualpython-users

[Visualpython-users] vpython fink package for Mac OSX 10.3

[Martin C. <cos...@wa...>]

I made a Fink package for vpython that uses python2.3 from Fink. It 
compiles and installs fine and the vpython script starts the IDLE 
window, but when I try to run a demo or just run python and "import 
visual", it crashes with an error message:

 >>> import visual
Visual-2003-10-05
Traceback (most recent call last):
   File "<stdin>", line 1, in ?
   File "/sw/lib/python2.3/site-packages/visual/__init__.py", line 81, in ?
     scene = display()
   File "/sw/lib/python2.3/site-packages/visual/__init__.py", line 34, 
in __call__
     return apply(self.constr, args, kw)
TypeError: CXX: type error.
 >>>

Can anybody please tell me where this might come from?

I am a complete newbie when it comes to vpython and, for that matter, to 
python. I would like to release this Fink package as soon as this 
problem is solved.

-- 
Martin

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Jonathan B. <jbr...@ea...>]

On Sun, 2004-01-25 at 15:35, Martin Costabel wrote:
> I made a Fink package for vpython that uses python2.3 from Fink.

Outstanding!  How exactly does fink packaging work?  Are the scripts
something that should be kept in CVS for version control?

>  It 
> compiles and installs fine and the vpython script starts the IDLE 
> window, but when I try to run a demo or just run python and "import 
> visual", it crashes with an error message:
> 
>  >>> import visual
> Visual-2003-10-05
> Traceback (most recent call last):
>    File "<stdin>", line 1, in ?
>    File "/sw/lib/python2.3/site-packages/visual/__init__.py", line 81, in ?
>      scene = display()
>    File "/sw/lib/python2.3/site-packages/visual/__init__.py", line 34, 
> in __call__
>      return apply(self.constr, args, kw)
> TypeError: CXX: type error.
>  >>>
> 
> Can anybody please tell me where this might come from?

I don't know.  I haven't seen this kind of error before.  What process
did you follow to build the package?  Maybe that will offer some clues
for further investigation.

> I am a complete newbie when it comes to vpython and, for that matter, to 
> python. I would like to release this Fink package as soon as this 
> problem is solved.

Dr. Sherwood and I would like to help you release it too!  Is this
package destined for inclusion in fink itself, or are you going to
provide a separate repository for it?

Thanks,
Jonathan Brandmeyer

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Martin C. <cos...@wa...>]

Jonathan Brandmeyer wrote:
[]
> I don't know.  I haven't seen this kind of error before.  What process
> did you follow to build the package?  Maybe that will offer some clues
> for further investigation.

I don't know if this list allows attachments. If yes, you will find 
attached the info and patch files that constitute the Fink package 
description. They are not very long and should be more or less 
self-explanatory. If the attachments don't arrive, I can try to explain. 
In any case, there is nothing extraordinary. I followed basically the 
instructions for Unix installation on the vpython web site.

> Dr. Sherwood and I would like to help you release it too!  Is this
> package destined for inclusion in fink itself, or are you going to
> provide a separate repository for it?

This is for inclusion in Fink itself.

-- 
Martin

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Jonathan B. <jbr...@ea...>]

On Sun, 2004-01-25 at 15:58, Martin Costabel wrote:
> Jonathan Brandmeyer wrote:
> []
> > I don't know.  I haven't seen this kind of error before.  What process
> > did you follow to build the package?  Maybe that will offer some clues
> > for further investigation.

Well, like you said, the build procedure looks pretty standard.

> I don't know if this list allows attachments. If yes, you will find 
> attached the info and patch files that constitute the Fink package 
> description. They are not very long and should be more or less 
> self-explanatory. If the attachments don't arrive, I can try to explain. 
> In any case, there is nothing extraordinary. I followed basically the 
> instructions for Unix installation on the vpython web site.
> 

Excellent, I got it.  I have a build going as I write this on a 10.2 box
with Python 2.2 and an Apple-distributed GCC 3.1.

First off, unless you have CPPFLAGS set to include -I/sw/include already
as part of the fink environment, it should be set by visual-py23.info.

cvisual/Makefile is totally insensitive to the DESTDIR variable, exactly
why is it needed?  Is the makefile not picking up on the value of
'prefix' for some reason?

Since gtkglarea is distributed as a static lib, I think it should
actually be a build-dependency and not an install dependency.

With the changes that your patch makes to OSX_SORULE, the link step
fails with many undefined references to functions defined in the Python
executable itself.

Just exactly what does that sed script do?  I've never used sed.

What command do you execute to build the package? (eg, the counterpart
to dpkg-buildpackage in Debian).

visual/Makefile byte-compiles site-packages/visual/*.py already, why is
the post-install script doing this as well?

If you force CXXFLAGS=-O2 and CFLAGS=-O2, you will cut down on the size
of the package (Autoconf adds in -g by default unless you override it).

> 
> This is for inclusion in Fink itself.


Thanks for this work!
-Jonathan Brandmeyer

P.S.  There is a driving snowstorm between me and the OSX machine I
tested your stuff on, so any testing I can do on my end is limited to
text-only for a day or so.  Finally, the connection isn't forwarding GLX
properly even though X11 is forwarding.  Oh, well.

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Martin C. <cos...@wa...>]

Jonathan Brandmeyer wrote:


> Excellent, I got it.  I have a build going as I write this on a 10.2 box
> with Python 2.2 and an Apple-distributed GCC 3.1.

Yes, I found now that the error I am seeing comes from using gcc-3.3 
which is the standard on OSX 10.3. It goes away when I use gcc-3.1. It 
seems that the CXX library does not work with gcc-3.3. This is really 
weird, because all these things are in the end linked with the python2.3 
executable which was compiled with gcc-3.3, and C++-compiled binaries 
are, in general, not compatible between gcc-3.1 and gcc-3.3.

Anyway, if no solution is found to make the CXX stuff compatible with 
gcc-3.3, I can require that the package is built with gcc-3.1, crossing 
fingers that this will not break other things.

> First off, unless you have CPPFLAGS set to include -I/sw/include already
> as part of the fink environment, it should be set by visual-py23.info.

This is automatically set by fink.

> cvisual/Makefile is totally insensitive to the DESTDIR variable, exactly
> why is it needed?  Is the makefile not picking up on the value of
> 'prefix' for some reason?

It is, but the fink build process is like with debian or rpm: You don't 
install to the final destination, but to some build-root from which the 
package is then created. Thus the prefix is set to /sw (%p in the info 
file), but the make install has to install into 
/sw/src/root-visual-py23-2.1.9-1/sw/

Hence the need for the DESTDIR variable which is respected in all 
subdirectories except cvisual. cvisual/Makefile installs the vpython 
script directly into /sw/bin which is illegal, because in this way it 
does not get into the package.

> Since gtkglarea is distributed as a static lib, I think it should
> actually be a build-dependency and not an install dependency.

OK, noted.

> With the changes that your patch makes to OSX_SORULE, the link step
> fails with many undefined references to functions defined in the Python
> executable itself.

The "-bundle_loader $PYTHON" flag takes care of this. It tells ld to 
look for undefined symbols in the python executable. There was just a 
syntax error: -bundle_loader doesn't take a "=" sign. I removed the 
-flat_namespace, because the python executable is compiled as a 
two_level binary, but I guess this doesn't make much difference.
In any case, it compiled OK for me, both with gcc-3.3 and with gcc-3.1.

> Just exactly what does that sed script do?  I've never used sed.

This is something completely unimportant. I wanted to have something 
other than the license.txt in the doc directory. For every fink package 
there is a doc directory in /sw/share/doc, in this case 
/sw/share/doc/visual-py23. I took the docs/index.html to put there, 
renamed to visual.html, and the sed changes the links in that file so 
that they point to the other local vpython html files in 
/sw/lib/python2.3/site-packages/visual/docs. I don't know enough about 
the inner workings of vpython to see whether the latter need to remain 
in the site-packages/visual/docs directory or whether they could be 
moved to /sw/share/doc/visual, so I let them where they were installed 
by default.

> What command do you execute to build the package? (eg, the counterpart
> to dpkg-buildpackage in Debian).

The command is simply "fink install visual-py23". Fink actually creates 
a *.deb package and then uses dpkg to install it at its final 
destination. If one wants to build only the deb package without 
isntallation, the command is "fink build visual-py23".

The package will first go into the unstable tree, so that fink users 
will have to activate this. After some time, it will migrate to the 
stable tree, and in this case it can then become part of Fink's binary 
distribution. When this is achieved, Fink users can use "apt-get install 
visual-py23" to get the precompiled binary directly.

> visual/Makefile byte-compiles site-packages/visual/*.py already, why is
> the post-install script doing this as well?

I saw that the *.pyc files have the buildroot directory hardwired inside 
and suspected that this could have something to do with my error, so I 
compiled them a second time after they were installed at their final 
place. But I think this is useless, after all. OK, while I wrote this, I 
compiled it again without this PostInstScript, and the ball is still 
bouncing, so I guess I'll remove this part.

Another question: I read Kelvin Chu's installation instructions, and he 
says that gdbm3 is needed, too. Is this true? I don't see anything 
gdbm-related in the compile log.

-- 
Martin

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Gary P. <pa...@in...>]

> Yes, I found now that the error I am seeing comes from using gcc-3.3
> which is the standard on OSX 10.3. It goes away when I use gcc-3.1. It
> seems that the CXX library does not work with gcc-3.3. This is really
> weird, because all these things are in the end linked with the python2.3
> executable which was compiled with gcc-3.3, and C++-compiled binaries
> are, in general, not compatible between gcc-3.1 and gcc-3.3.

FYI, these are the kinds of problems that have popped up on the fink
discussion board, and have been giving me agita about upgrading to 10.3.

I'm happy that Jonathan has been having success building on 10.2.  I
encourage you again to ensure that it works in 10.2.

(Mine's already working on 10.2 ... but you are doing a great thing for
future users.
You deserve a medal.)

-Gary

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Martin C. <cos...@wa...>]

Gary Pajer wrote:
[]
> I'm happy that Jonathan has been having success building on 10.2.  I
> encourage you again to ensure that it works in 10.2.

It works on 10.2 in the same way as on 10.3, that is, it works when 
compiled with gcc-3.1 and doesn't when compiled with gcc-3.3.

-- 
Martin

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Aaron T. <ti...@ma...>]

Martin,

I also want to say "thank you" for creating the fink package. I use 
10.2, and will probably upgrade to 10.3 sometime this summer. I 
presently use visual, but it's not even the latest version. I'm too 
nervous to attempt the upgrade until I have time to troubleshoot. A 
Fink package will be welcomed indeed.

Thank you!

AT


> (Mine's already working on 10.2 ... but you are doing a great thing for
> future users.
> You deserve a medal.)

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Martin C. <cos...@wa...>]

Gary Pajer wrote:
[]
> (Mine's already working on 10.2 ... but you are doing a great thing for
> future users.

OK guys, I have put the visual-py23 package into the Fink 10.3/unstable 
and 10.2-gcc3.3/unstable trees (Yes, 10.2-gcc3.3, although the package 
requires to be built with gcc-3.1, but the old 10.2 tree is not 
supported any more). They should show up on the next selfupdate soon. I 
let you in the later timezones give them a hard time while I sleep (1:30 
am here now).

-- 
Martin

[Visualpython-users] vpython fink package for Mac OSX 10.4

[Aaron T. <ti...@ma...>]

Martin,

I upgraded to Tiger (OS 10.4). I just installed Fink and Fink  
Commander. However, I couldn't install the visual-py23 package. I got  
an error regarding dependencies.

Have you tried to install VPython using Tiger?

Aaron

On Jan 25, 2004, at 7:35 PM, Martin Costabel wrote:
>
> OK guys, I have put the visual-py23 package into the Fink 10.3/ 
> unstable and 10.2-gcc3.3/unstable trees (Yes, 10.2-gcc3.3, although  
> the package requires to be built with gcc-3.1, but the old 10.2  
> tree is not supported any more). They should show up on the next  
> selfupdate soon. I let you in the later timezones give them a hard  
> time while I sleep (1:30 am here now).
>
> -- 
> Martin
>

Re: [Visualpython-users] vpython fink package for Mac OSX 10.4

[Martin C. <cos...@wa...>]

Aaron Titus wrote:
> Martin,
> 
> I upgraded to Tiger (OS 10.4). I just installed Fink and Fink  
> Commander. However, I couldn't install the visual-py23 package. I got  
> an error regarding dependencies.
> 
> Have you tried to install VPython using Tiger?

Yes, it builds here without problem. What error do you get?

-- 
Martin

Re: [Visualpython-users] vpython fink package for Mac OSX 10.4

[Aaron T. <ti...@ma...>]

When I install from source, I get the error:

"Failed: Can't resolve dependency "gcc3.1" for package "visual- 
py23-2.1.9-6" (no matching packages/versions found)"

When I install the binary, I get the error:

Reading Package Lists...
Building Dependency Tree...
You might want to run `apt-get -f install' to correct these:
Sorry, but the following packages have unmet dependencies:
   storable-pm: Depends: storable-pm560 but it is not installable.  
For Fink users, this often means that you have attempted to install a  
package from the binary distribution which depends on a "Restrictive"  
package. See <http://fink.sourceforge.net/faq/usage- 
fink.php#bindist>, <http://fink.sourceforge.net/doc/users-guide/ 
packages.php#bin-exceptions> or
                         storable-pm561 but it is not installable.  
For Fink users, this often means that you have attempted to install a  
package from the binary distribution which depends on a "Restrictive"  
package. See <http://fink.sourceforge.net/faq/usage- 
fink.php#bindist>, <http://fink.sourceforge.net/doc/users-guide/ 
packages.php#bin-exceptions> or
                         perl580-core but it is not installable. For  
Fink users, this often means that you have attempted to install a  
package from the binary distribution which depends on a "Restrictive"  
package. See <http://fink.sourceforge.net/faq/usage- 
fink.php#bindist>, <http://fink.sourceforge.net/doc/users-guide/ 
packages.php#bin-exceptions> or
                         perl581-core but it is not installable. For  
Fink users, this often means that you have attempted to install a  
package from the binary distribution which depends on a "Restrictive"  
package. See <http://fink.sourceforge.net/faq/usage- 
fink.php#bindist>, <http://fink.sourceforge.net/doc/users-guide/ 
packages.php#bin-exceptions> or
                         perl584-core but it is not installable. For  
Fink users, this often means that you have attempted to install a  
package from the binary distribution which depends on a "Restrictive"  
package. See <http://fink.sourceforge.net/faq/usage- 
fink.php#bindist>, <http://fink.sourceforge.net/doc/users-guide/ 
packages.php#bin-exceptions>
   visual-py23: Depends: gtk+-shlibs but it is not going to be installed
                Depends: python23 but it is not going to be installed
                Depends: numeric-py23 but it is not going to be  
installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or  
specify a solution).


I installed x11 and xcode (developer tools) when I installed the OS.  
I'm using Fink Commander.

Aaron


On May 15, 2005, at 3:17 AM, Martin Costabel wrote:

> Aaron Titus wrote:
>
>> Martin,
>> I upgraded to Tiger (OS 10.4). I just installed Fink and Fink   
>> Commander. However, I couldn't install the visual-py23 package. I  
>> got  an error regarding dependencies.
>> Have you tried to install VPython using Tiger?
>>
>
> Yes, it builds here without problem. What error do you get?
>
> -- 
> Martin
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

Re: [Visualpython-users] vpython fink package for Mac OSX 10.4

[Martin C. <cos...@wa...>]

Aaron Titus wrote:
> When I install from source, I get the error:
> 
> "Failed: Can't resolve dependency "gcc3.1" for package "visual- 
> py23-2.1.9-6" (no matching packages/versions found)"
> 
> When I install the binary, I get the error:
> 
> Reading Package Lists...
> Building Dependency Tree...
> You might want to run `apt-get -f install' to correct these:
> Sorry, but the following packages have unmet dependencies:
>   storable-pm: Depends: storable-pm560 but it is not installable.  For 

Did you follow the instructions on the Fink home page for upgrading to 
Mac OSX 10.4? The package versions you are showing are those for 10.3. 
Your best bet at the moment for upgrading (or installing a fresh Fink) 
is to follow the instructions for the "stable" tree (keyword 
"bootstrap"). Once this is running, you can activate the unstable tree 
and install packages from there, but this is not necessary for the 
version of vpython in Fink. It is the same in stable and unstable.

If you are more adventurous, you can try to get from the mixture of old 
and new that you have now to a working 10.4 installation by running 
"fink selfupdate" at least twice. Then "fink install visual-py23".

Note that for all of this you need the XTools developer tools installed. 
Precompiled binaries for 10.4 do not yet exist. They are being prepared 
right now, but this will still take a while.

I am planning to upgrade the vpython Fink package for 10.4 to a more 
recent version, but I am not yet quite there.

-- 
Martin


-- 
Martin

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Jonathan B. <jbr...@ea...>]

On Sun, 2004-01-25 at 18:22, Martin Costabel wrote:
> Jonathan Brandmeyer wrote:
> 
> 
> > Excellent, I got it.  I have a build going as I write this on a 10.2 box
> > with Python 2.2 and an Apple-distributed GCC 3.1.
> 
> Yes, I found now that the error I am seeing comes from using gcc-3.3 
> which is the standard on OSX 10.3. It goes away when I use gcc-3.1. It 
> seems that the CXX library does not work with gcc-3.3. This is really 
> weird, because all these things are in the end linked with the python2.3 
> executable which was compiled with gcc-3.3, and C++-compiled binaries 
> are, in general, not compatible between gcc-3.1 and gcc-3.3.

It isn't an issue because the interface between cvisualmodule.so and
Python(.exe) is exclusively C-based, and the C ABI did not change
between those releases.  The only conflict would arise if you linked
some other shared object to cvisualmodule.so, which I can't imagine
anyone doing.

> Anyway, if no solution is found to make the CXX stuff compatible with 
> gcc-3.3, I can require that the package is built with gcc-3.1, crossing 
> fingers that this will not break other things.
> 

> > cvisual/Makefile is totally insensitive to the DESTDIR variable, exactly
> > why is it needed?  Is the makefile not picking up on the value of
> > 'prefix' for some reason?
> 
> It is, but the fink build process is like with debian or rpm: You don't 
> install to the final destination, but to some build-root from which the 
> package is then created. Thus the prefix is set to /sw (%p in the info 
> file), but the make install has to install into 
> /sw/src/root-visual-py23-2.1.9-1/sw/
> 
> Hence the need for the DESTDIR variable which is respected in all 
> subdirectories except cvisual. cvisual/Makefile installs the vpython 
> script directly into /sw/bin which is illegal, because in this way it 
> does not get into the package.

OK.  I'll put this change into CVS.

> 
> > With the changes that your patch makes to OSX_SORULE, the link step
> > fails with many undefined references to functions defined in the Python
> > executable itself.
> 
> The "-bundle_loader $PYTHON" flag takes care of this. It tells ld to 
> look for undefined symbols in the python executable. There was just a 
> syntax error: -bundle_loader doesn't take a "=" sign. I removed the 
> -flat_namespace, because the python executable is compiled as a 
> two_level binary, but I guess this doesn't make much difference.
> In any case, it compiled OK for me, both with gcc-3.3 and with gcc-3.1.

It was the "=" sign that was the problem, I didn't see notice that
before.  I'll put this into CVS as well.

> > Just exactly what does that sed script do?  I've never used sed.
> 
> This is something completely unimportant. I wanted to have something 
> other than the license.txt in the doc directory. For every fink package 
> there is a doc directory in /sw/share/doc, in this case 
> /sw/share/doc/visual-py23. I took the docs/index.html to put there, 
> renamed to visual.html, and the sed changes the links in that file so 
> that they point to the other local vpython html files in 
> /sw/lib/python2.3/site-packages/visual/docs. I don't know enough about 
> the inner workings of vpython to see whether the latter need to remain 
> in the site-packages/visual/docs directory or whether they could be 
> moved to /sw/share/doc/visual, so I let them where they were installed 
> by default.

No, they don't need to be in any place special.  We did that for a
distribution-independent location, and I fully expect distributors to
rearrange file locations as required to satisfy the distribution's
policies.

> > What command do you execute to build the package? (eg, the counterpart
> > to dpkg-buildpackage in Debian).
> 
> The command is simply "fink install visual-py23". Fink actually creates 
> a *.deb package and then uses dpkg to install it at its final 
> destination. If one wants to build only the deb package without 
> isntallation, the command is "fink build visual-py23".
> 
> The package will first go into the unstable tree, so that fink users 
> will have to activate this. After some time, it will migrate to the 
> stable tree, and in this case it can then become part of Fink's binary 
> distribution. When this is achieved, Fink users can use "apt-get install 
> visual-py23" to get the precompiled binary directly.
> 
> > visual/Makefile byte-compiles site-packages/visual/*.py already, why is
> > the post-install script doing this as well?
> 
> I saw that the *.pyc files have the buildroot directory hardwired inside 
> and suspected that this could have something to do with my error, so I 
> compiled them a second time after they were installed at their final 
> place. But I think this is useless, after all. OK, while I wrote this, I 
> compiled it again without this PostInstScript, and the ball is still 
> bouncing, so I guess I'll remove this part.

If the *.pyc files have something wrong with them, then they would
normally be recompiled on use, but since normal users don't have access
to that directory, it is silently ignored and the interpreter will use
the plain .py files instead.  The only consequence would be a slightly
slower module loading time.  So, if there is a problem, you should
probably go ahead and re-run py-compile on those files.

> 
> Another question: I read Kelvin Chu's installation instructions, and he 
> says that gdbm3 is needed, too. Is this true? I don't see anything 
> gdbm-related in the compile log.

Is that the GNU Database Manager?  AFAIK it isn't needed.

Thanks again,
Jonathan Brandmeyer

Re: [Visualpython-users] vpython fink package for Mac OSX 10.3

[Gary P. <pa...@in...>]

----- Original Message ----- 
From: "Jonathan Brandmeyer" <jbr...@ea...>
To: <Vis...@li...>
Sent: Sunday, January 25, 2004 3:47 PM
Subject: Re: [Visualpython-users] vpython fink package for Mac OSX 10.3


> On Sun, 2004-01-25 at 15:35, Martin Costabel wrote:
> > I made a Fink package for vpython that uses python2.3 from Fink.
>
> Outstanding!

Agreed!!

One pleading request:  make it work for 10.2 also.

I for one don't plan on upgrading to 10.3 any time soon.
10.2 works for me, and I've seen lots of trouble with 10.3 discussed on the
fink disscusssion group.  I have all the trouble I need, thank you.
Additionally, there's the cost / difficulty dealing with our IT people.

-gary