On 2/15/06, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> Peter Kropf <[EMAIL PROTECTED]> wrote:
>
> > I just tried building a simple hello world application on a FreeBSD
> > 6.0 system and it worked! I was wondering, is there a set of unit
> > tests that I can use to perform a bit more serious verification of
> > FreeBSD support? I see that there's a buildtest directory.
>
> Alas, there are no unittests at the moment. I'd really like them but I don't
> have much time at the moment (contributions are welcome). "buildtests"
> contains
> some tests, but they are nowhere as comprehensive as they should be.
>
> > Unfortunately when I use runtests.py, I see lots of syntax errors
> > like:
> >
> >
> > a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'),
> > os.path.join(HOMEPATH,'support\\useUnicode.py'), 'test9.py'],
> >
> > ^
> > SyntaxError: invalid syntax
> > disttest9/test9: not found
>
> Isn't just the backslash vs forward slash problem? Does it work if you remove
> it altogether, eg, os.path.join(HOMEPAGE, 'support', '_mountzlib.py') ?
The problem is that the .spec files were generated on Windows and have
a CRLF line terminator. I checked the .tar.gz distribution and the SVN
source and they both have it. I'm not certain why the problem exists
in SVN since it is supposed to take care of the platform text file
dependencies for you. I'll look at it a bit more to see why but this
causes a problem for Python on FreeBSD 6.0. I also tried it on a
Ubuntu Linux system and it worked just fine. Weird.
> > I admit that I haven't dug too far into the tests to see what's going
> > on. I wanted to check that I'm heading in the right direction before
> > going to far. Any insight that you can provide would be appreciated...
>
>
> It'd be very helpful if you tried the tests under FreeBSD to check if they
> work.
Next problem that I ran into was that the .spec files all create a
program with a .exe extension. However, the runtests.py program tried
to run the executable without specifying the .exe extension. And that
doesn't work all that well on non-Windows platforms ;-) BTW, this is
also a problem on Linux.
I'm also seeing a problem with test8 on FreeBSD but haven't looked
into it yet. Here's the output:
################## EXECUTING TEST test8.py ################################
Traceback (most recent call last):
File "../Build.py", line 830, in ?
build(sys.argv[1])
File "../Build.py", line 76, in build
exec open(spec, 'r').read()+'\n'
File "<string>", line 2, in ?
File "../Build.py", line 102, in __init__
raise ValueError, "script '%s' not found" % script
ValueError: script '../support\_mountzlib.py' not found
disttest8/test8: not found
Lastly, I tried to submit some bugs to Trac but received:
Trac detected an internal error:
{'[EMAIL PROTECTED]': (553, "sorry, that domain isn't in my list of
allowed rcpthosts (#5.5.3 - chkuser)")}
Should I submit them as anonymous? I'd like to receive notification if
/ when the tickets are changed. I can also create a svn diff patch for
the changes needed for the .exe problem. Should I email that? Or
attach to a ticket in Trac?
- Peter
_______________________________________________
PyInstaller mailing list
[email protected]
http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
