|
List Info
Thread: Re: Fwd: Memory error
|
|
| Re: Fwd: Memory error |

|
2007-11-30 15:15:04 |
|
eek. This is the same error I was going to bring up next - the error I got when migrating a small database! Looks like I'm out of luck, then!
Anyone have any idea why this should be so? Why should vss2svn have trouble on 64?
David
On Nov 30, 2007 3:39 PM, Leo Davis < ldavis  fonix.com" >ldavis fonix.com> wrote:
David Blaikie wrote: > Excellent, thank you for the detailed response. That makes a lot of > sense. I9;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 http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
|
| Re: Fwd: Memory error |

|
2007-11-30 15:15:36 |
|
my mistake - ssphys has the problem...
On Nov 30, 2007 4:15 PM, David Blaikie < dbb14  columbia.e du">dbb14 columbia.edu> wrote:
eek. This is the same error I was going to bring up next - the error I got when migrating a small database! Looks like I'm out of luck, then!
Anyone have any idea why this should be so? Why should vss2svn have trouble on 64?
DavidOn Nov 30, 2007 3:39 PM, Leo Davis < ldavis  fonix.com" target="_blank">ldavis fonix.com
> wrote:
David Blaikie wrote: > Excellent, thank you for the detailed response. That makes a lot of > sense. I9;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 http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
|
[1-2]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|