Maybe it does something silly like assume sizeof(int) = 4 bytes? I don't know,
on modern compilers was the decision made that int should become 8 bytes (64
bits wide)? I know that size of pointers would have to change, but if it is
trying to do IO based on pointer sizes that would be really out
my mistake - ssphys has the problem...
On Nov 30, 2007 4:15 PM, David Blaikie <[EMAIL PROTECTED]> 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
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 <[EMAIL PROTECTED]> wrote:
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 th
