[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Max file size problem on 32-bit



I figured this one out on my own. (newbie ignorance)

The python docs gave me a good tip to enable the appropriate CFLAGS for LargeFile Support
http://python.org/doc/2.5.2/lib/posix-large-files.html

So, a 'make clean', followed by
CFLAGS='-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64' OPT="-g -O2 $CFLAGS" ./configure
then, 'make'
and 'sudo checkinstall make install'

...fixed the scrypt binary installed on my workstation.

No worries.
Just thought i'd post it here, in case some other newbie ran into the same issue. (non-issue? :) )

@Colin : This LFS support option wouldn't be a bad default for the configure script.
(Gmail saved my draft instead of sending it. Hence the delay in posting this)

On Fri, Oct 30, 2009 at 2:39 PM, Vimal George <vimal@canthack.net> wrote:
Using the scrypt Proof-of-concept file encryption utility at http://www.tarsnap.com/scrypt/scrypt-1.1.4.tgz
I encrypted a 2.5 GB server backup tarball on a 64 bit linux server (Ubuntu Hardy LTS)

Upon attempting a 'scrypt dec' on the same downloaded encrypted file on a 32bit linux desktop (Ubuntu Hardy LTS),
i'm getting an error message as follows :

scrypt dec backup2009-oct20.tar.crypt backup2009-oct20.tar
scrypt: Cannot open input file: backup2009-oct20.tar.crypt: Value too large for defined data type

I'm guessing this has something to do with some 2GB filesize addressability problem on 32bit platforms(just guessing from the google results).

Any quick hacks to make this decrypt work on a 32bit linux kernel?
or Do i have to boot a 64-bit linux image and re-build scrypt on the same to do this decrypt?


--
Regards,
Vimal George
-----------------------------------------
"May the /src be with you"



--
Regards,
Vimal G George
Tech Team, Logicmanse.
-----------------------------------------
"May the /src be with you"