Menu
▾
▴
visualpython-users
|
From: Andrew M. <agm...@gm...> - 2011-09-21 15:50:17
|
Hi, I'm running Ubuntu 11.04. Originally vpython (gotten by apt-get install python-visual) works great. After installing NVIDIA CUDA software, vpython completely fails to work. E.g. $ python >> from visual import box >> box() Segmentation Fault $ I asked a similar question before, and it was suggested that the problem might be that I was using visual.materials in my code. The example above, however, shows that even the most basic application isn't working. Any ideas? -- Sincerely, Andrew McCormick |
|
From: Bruce S. <Bru...@nc...> - 2011-09-21 21:59:27
|
Alas, I at least have no clue as why there is this problem. I hope someone else on this list is knowledgeable about the possible interaction of Visual and CUDA. Bruce Sherwood On Wed, Sep 21, 2011 at 9:50 AM, Andrew McCormick <agm...@gm...> wrote: > Hi, > > I'm running Ubuntu 11.04. Originally vpython (gotten by apt-get install > python-visual) works great. After installing NVIDIA CUDA software, vpython > completely fails to work. E.g. > > $ python >>> from visual import box >>> box() > Segmentation Fault > $ > > I asked a similar question before, and it was suggested that the problem > might be that I was using visual.materials in my code. The example above, > however, > shows that even the most basic application isn't working. Any ideas? > > > -- > Sincerely, > > Andrew McCormick > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
|
From: Kevin K. <ka...@so...> - 2011-09-21 22:10:56
|
The problem could be with Vpython requiring a 32-bit python and the CUDA code requiring a 64-bit python. I still don't understand why Vpython requires 32-bit python. Kevin Karplus |
|
From: Bruce S. <Bru...@nc...> - 2011-09-22 02:39:39
|
The reason is very simple. Someone knowledgeable needs to update the autoconfig machinery to handle Linux 64-bit Python and send it to me to replace what exists. I recall some people having built for 64-bit Python on Linux, though I think they had to kludge it, whereas what's needed is for the autoconfig machinery to detect the bitness and exploit it. Bruce Sherwood On Wed, Sep 21, 2011 at 4:10 PM, Kevin Karplus <ka...@so...> wrote: > > The problem could be with Vpython requiring a 32-bit python and the > CUDA code requiring a 64-bit python. > > I still don't understand why Vpython requires 32-bit python. > > Kevin Karplus > |
|
From: Thomas S. <to...@fe...> - 2011-09-22 10:49:54
|
On Wed, 21 Sep 2011 15:10:48 -0700 Kevin Karplus wrote: > > The problem could be with Vpython requiring a 32-bit python and the > CUDA code requiring a 64-bit python. > > I still don't understand why Vpython requires 32-bit python. It works on 64-bit python, but I don't know how ubuntu handles that... Here, we have 64 bit apps/libs in /usr/lib64 and 32 bit apps/libs in /usr/lib/ so when building on a 64 bit machine, this works as expected... Don't know, how ubuntu users could solve that... Tom |
|
From: Kevin K. <ka...@so...> - 2011-09-22 12:52:12
|
I'm using a Mac, and had to reinstall Python 2.7.2 in the 32-bit version, because the Mac Vpython would not run with the 64-bit version. I've no idea why. |
|
From: Bruce S. <Bru...@nc...> - 2011-09-22 14:32:53
|
As it says on the vpython.org download page, "VPython does not work with Mac 64-bit Python, but this 32-bit version of Python works fine on 64-bit Macs." The reason is that VPython is based on Apple's Carbon environment, which is now deprecated and does not support 64-bit environments. Graphics applications such as VPython are now supposed to be built on the newer environment Cocoa. Unfortunately, this seems to be impossible. David Scherer and I were unable to find a way to use Cocoa, due to incompatible thread priority issues. Experts on the Cocoa dev list when asked agreed that there is a big problem. Bruce Sherwood On Thu, Sep 22, 2011 at 6:51 AM, Kevin Karplus <ka...@so...> wrote: > I'm using a Mac, and had to reinstall Python 2.7.2 in the 32-bit > version, because the Mac Vpython would not run with the 64-bit > version. I've no idea why. |
|
From: Kevin K. <ka...@so...> - 2011-09-22 14:46:39
|
OK, the use of Carbon rather than Cocoa explains why Vpython doesn't run on 64-bit implementations. It also means that most likely within 5 years Vpython will not run on Macs at all, unless it is reimplemented. |
|
From: Bruce S. <Bru...@nc...> - 2011-09-22 18:28:13
|
As I've said before, this is indeed a big threat. There is however a fallback position if no one finds a Cocoa solution, which is to revert to what VPython used to do on Macs, which is to run on the Unix side, using GTK. There is in fact a version like this maintained in the Fink distribution. The disadvantage is that the look and feel is native Mac. Bruce Sherwood On Thu, Sep 22, 2011 at 8:46 AM, Kevin Karplus <ka...@so...> wrote: > > OK, the use of Carbon rather than Cocoa explains why Vpython doesn't > run on 64-bit implementations. It also means that most likely within > 5 years Vpython will not run on Macs at all, unless it is > reimplemented. > > |
|
From: Bruce S. <Bru...@nc...> - 2011-09-22 21:09:38
|
Careless typo. Of course I meant "The disadvantage is that the look and feel is NOT native Mac." Bruce Sherwood On Thu, Sep 22, 2011 at 12:28 PM, Bruce Sherwood <Bru...@nc...> wrote: > As I've said before, this is indeed a big threat. There is however a > fallback position if no one finds a Cocoa solution, which is to revert > to what VPython used to do on Macs, which is to run on the Unix side, > using GTK. There is in fact a version like this maintained in the Fink > distribution. The disadvantage is that the look and feel is native > Mac. > > Bruce Sherwood > > On Thu, Sep 22, 2011 at 8:46 AM, Kevin Karplus <ka...@so...> wrote: >> >> OK, the use of Carbon rather than Cocoa explains why Vpython doesn't >> run on 64-bit implementations. It also means that most likely within >> 5 years Vpython will not run on Macs at all, unless it is >> reimplemented. >> >> > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X