On 1/8/2009 7:27 PM, Anthony Floyd wrote:
> I've seen mention of this in the archives, but no resolution.
> 
> - Using svn trunk (rev 594)
> 
> $ svn info
> Path: .
> URL: http://svn.pyinstaller.python-hosting.com/trunk
> Repository Root: http://svn.pyinstaller.python-hosting.com
> Repository UUID: 8dd32b29-ccff-0310-8a9a-9233e24343b1
> Revision: 594
> Node Kind: directory
> Schedule: normal
> Last Changed Author: lmancini
> Last Changed Rev: 592
> Last Changed Date: 2009-01-07 08:01:49 -0800 (Wed, 07 Jan 2009)
> 
> 
> - Ubuntu 8.04.1
> 
> $ cat /etc/issue
> Ubuntu 8.04.1 \n \l
> 
> - x86_64 (AMD64)
> 
> $ uname -a
> Linux Wyvern-II 2.6.24-22-generic #1 SMP Mon Nov 24 19:35:06 UTC 2008
> x86_64 GNU/Linux
> 
> I've checked out the WC from the SVN, gone to the source/linux
> directory, run python Make.py, then make clean, then make. Other than
> some warnings relating to pointer signedness, it seems to compile
> fine.
> 
> Then I go to the buildtests directory and try to run the tests. Quite
> a number of tests fail (1,2,5,6,7,8,9,10,11,12,13,14, 'site_module',
> 'getfilesystemencoding1'), all giving segfaults when the programs try
> to run.
> 
> The segfault is the problem I was seeing with my own script that I was
> trying to package.

Yes, there's something weird with x86_64. I've always been unable to 
reproduce it (I develop on Ubuntu x86_64 myself and cannot reproduce 
this problem).

If you are a C/C++ developer, I would appreciate if you could help me 
debugging it out. Providing me with a remote shell onto that computer 
would also be fantastic.
-- 
Giovanni Bajo
Develer S.r.l.
http://www.develer.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to