David Blaikie wrote: > Excellent, thank you for the detailed response. That makes a lot of > sense. I'm going to try another Windows trial... > > I did manage to compile on Linux and run the program. When I tried to > do it on a test database, I got a "file not recognized" error (don't > have the text in front of me). When I looked up this error on google > I found a conversation from someone who was trying to migrate on a Mac > and began a discussion on endian byte order. I thought this might be > my issue as well but my colleague (helpful fellow, him) said that it's > processor-specific - Intel Linux will have same byte order as Intel > Windows. The only other variable I know about is that our Linux box > is 64-bit, but apparently that doesn't matter either. What do you > think? > Actually, it does matter. I have a dual boot box with both 32 and 64 bit copies of the Linux OS. I built and installed the current trunk on both OSes. The migration runs to completion on the i586 OS. When I run the migration on the x86_64 OS the migration fails almost immediately:
ssphys: unrecognized file Try `ssphys --help` for more information ERROR -- FAILED with non-zero exit status 255 (cmd: "ssphys" info -ewindows-1252 "/path/to/database/data/names.dat") at /usr/bin/vss2svn.pl line 1481 File does not exist: at /usr/bin/vss2svn.pl line 130 ssphys seems to have problems when built for 64-bit Linux. Leo _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
