Hello Alex, Ok, thanks for letting me know. Could you try and run PyInstaller from the console and do a Build.py to see if you get the same error output?
Regards, Mathias [EMAIL PROTECTED] wrote: > Thanks, it worked like a charm, however I'm having some trouble with > the application itself now. I'm running make then build using one- > file, and I'm getting the following output in the application: > > wrote /home/alex/Desktop/pyelection/pyelection.spec > now run Build.py to build the executable > > > checking Analysis > building Analysis because out0.toc non existent > running Analysis out0.toc > Analyzing: /home/alex/Desktop/pyinstaller-1.3/support/_mountzlib.py > Analyzing: /home/alex/Desktop/pyinstaller-1.3/support/useUnicode.py > Analyzing: /home/alex/python_stuff/PyElection/pyelection.py > Warnings written to /home/alex/Desktop/pyelection/warnpyelection.txt > checking PYZ > rebuilding out1.toc because out1.pyz is missing > building PYZ out1.toc > checking PKG > rebuilding out3.toc because out3.pkg is missing > building PKG out3.pkg > checking ELFEXE > rebuilding out2.toc because pyelection missing > building ELFEXE out2.toc > > > and the following in the console > > [EMAIL PROTECTED]:~/Desktop$ ./G4PI > Traceback (most recent call last): > File "/home/alex/Desktop/pyinstaller-1.3/Build.py", line 839, in > <module> > build(sys.argv[1]) > File "/home/alex/Desktop/pyinstaller-1.3/Build.py", line 76, in > build > exec open(spec, 'r').read()+'\n' > File "<string>", line 11, in <module> > File "/home/alex/Desktop/pyinstaller-1.3/Build.py", line 466, in > __init__ > self.__postinit__() > File "/home/alex/Desktop/pyinstaller-1.3/Build.py", line 94, in > __postinit__ > self.assemble() > File "/home/alex/Desktop/pyinstaller-1.3/Build.py", line 546, in > assemble > self.copy(exe, outf) > File "/home/alex/Desktop/pyinstaller-1.3/Build.py", line 558, in > copy > inf = open(fnm, 'rb') > IOError: [Errno 2] No such file or directory: '/home/alex/Desktop/ > pyinstaller-1.3/support/loader/run_d' > > > I'm not sure whether this is a G4PI problem, or something with > pyinstaller itself. I'll be going over to windows later to test it > there. > > On Feb 13, 1:35 pm, hybris <[EMAIL PROTECTED]> wrote: >> I have found a solution to the problem. You have to have wxPython 2.8 >> installed on your ubuntu system. You can install this by doing >> >> sudo apt-get install python-wxgtk2.8 >> >> Then G4PI should work. >> >> Regards, >> >> Mathias >> >> On Feb 13, 11:45 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >> wrote: >> >>> Ok, in the mean time I'll give it a try in windows and report back >>> later today. >>> On Feb 13, 4:20 am, "Mathias Anlér" <[EMAIL PROTECTED]> wrote: >>>> Hello Alex, >>>> 2008/2/13, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: >>>>> Thanks! From the looks of the problem some value is hard coded which >>>>> is causing the problem(I assume this is it because I don't have a clue >>>>> where my system would get /home/mathias/ from). I can't wait to get >>>> Yes, that might be the case. >>>> to try this out, although it means I'll have to get a windows dev> >>>> enviroment together to create my exes! >>>> I have tried the windows version on a separate machine and I works ok. I >>>> was >>>> unable to try the ubuntu version on another machine. I will recompile and >>>> post and update as soon as I know what caused the problem. >>>> Regards, >>>> Mathias > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
