Eric, Thanks for the report and the solution. I've checked it into Subversion so it will be included in the next release.
As for reports, this works as well as anything else. There is a SourceForge tracker that you could use as well but I'm fine with this, too. For anything more complex than the one line change I prefer the output from svn diff (or diff -u). Thanks again. Anthony On Wed, Jan 21, 2009 at 9:17 AM, Eric Brunel <[email protected]> wrote: > Hello all, > > I tried cx_freeze on a Solaris box and it didn't work because some > library dependencies weren't spotted. I investigated a bit and found > out the 'ldd' command on Solaris outputs the dependency list with a > tab after the '=>'. So the line.strip().split(" => ") in > Freezer._GetDependentFiles (module freezer.py, line 200 in version > 4.0.1) doesn't work and the wrong library dependencies are returned. > > Apparently, replacing this line by: > parts = line.expandtabs().strip().split(" => ") > seemed to solve the problem for me. > > Just thought it would be nice to include this in the next version. I > didn't find a more "official" way to report bugs than this list. If > there is, please tell me: I'll be glad to do it. > > Thanks! > -- > - Eric Brunel > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > cx-freeze-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/cx-freeze-users > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ cx-freeze-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
