FilePlugin maximum size
I just encountered a I guess it is because the position of 1073750701 is just slightly bigger than (2 raisedTo: 30 = 1073741824). Is there a way to get a full 32 bit range? thanks, Norbert
On Sun, Jun 07, 2015 at 04:02:10PM +0200, Norbert Hartl wrote:
I just encountered a
I guess it is because the position of 1073750701 is just slightly bigger than (2 raisedTo: 30 = 1073741824). Is there a way to get a full 32 bit range?
You need a VM compiled with large file support http://en.wikipedia.org/wiki/Large_file_support For gcc, the compiler flag is -D_FILE_OFFSET_BITS=64 Dave
Am 07.06.2015 um 17:01 schrieb David T. Lewis <lewis@mail.msen.com>:
On Sun, Jun 07, 2015 at 04:02:10PM +0200, Norbert Hartl wrote:
I just encountered a
I guess it is because the position of 1073750701 is just slightly bigger than (2 raisedTo: 30 = 1073741824). Is there a way to get a full 32 bit range?
You need a VM compiled with large file support http://en.wikipedia.org/wiki/Large_file_support
For gcc, the compiler flag is -D_FILE_OFFSET_BITS=64
Thanks. What are the reasons for not having that turned by default? Norbert
they are although you need to use latest vm :) Esteban
On 07 Jun 2015, at 17:06, Norbert Hartl <norbert@hartl.name> wrote:
Am 07.06.2015 um 17:01 schrieb David T. Lewis <lewis@mail.msen.com>:
On Sun, Jun 07, 2015 at 04:02:10PM +0200, Norbert Hartl wrote:
I just encountered a
I guess it is because the position of 1073750701 is just slightly bigger than (2 raisedTo: 30 = 1073741824). Is there a way to get a full 32 bit range?
You need a VM compiled with large file support http://en.wikipedia.org/wiki/Large_file_support
For gcc, the compiler flag is -D_FILE_OFFSET_BITS=64
Thanks. What are the reasons for not having that turned by default?
Norbert
How do I get the version of the Mac vm? The date of the plist file is from April. Has it been turned just recently? Norbert
Am 07.06.2015 um 17:40 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
they are although you need to use latest vm :)
Esteban
On 07 Jun 2015, at 17:06, Norbert Hartl <norbert@hartl.name> wrote:
Am 07.06.2015 um 17:01 schrieb David T. Lewis <lewis@mail.msen.com>:
On Sun, Jun 07, 2015 at 04:02:10PM +0200, Norbert Hartl wrote:
I just encountered a
I guess it is because the position of 1073750701 is just slightly bigger than (2 raisedTo: 30 = 1073741824). Is there a way to get a full 32 bit range?
You need a VM compiled with large file support http://en.wikipedia.org/wiki/Large_file_support
For gcc, the compiler flag is -D_FILE_OFFSET_BITS=64
Thanks. What are the reasons for not having that turned by default?
Norbert
Hi Norbert, as a stop gap you should be able to use a Mac VM from my site, e.g. http://www.mirandabanda.org/files/Cog/VM/VM.r3370/. All these VMs have been compiled with large file support. HTH On Sun, Jun 7, 2015 at 9:40 AM, Norbert Hartl <norbert@hartl.name> wrote:
How do I get the version of the Mac vm? The date of the plist file is from April. Has it been turned just recently?
Norbert
Am 07.06.2015 um 17:40 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
they are although you need to use latest vm :)
Esteban
On 07 Jun 2015, at 17:06, Norbert Hartl <norbert@hartl.name> wrote:
Am 07.06.2015 um 17:01 schrieb David T. Lewis <lewis@mail.msen.com>:
On Sun, Jun 07, 2015 at 04:02:10PM +0200, Norbert Hartl wrote:
I just encountered a
I guess it is because the position of 1073750701 is just slightly bigger than (2 raisedTo: 30 = 1073741824). Is there a way to get a full 32 bit range?
You need a VM compiled with large file support http://en.wikipedia.org/wiki/Large_file_support
For gcc, the compiler flag is -D_FILE_OFFSET_BITS=64
Thanks. What are the reasons for not having that turned by default?
Norbert
-- best, Eliot
participants (4)
-
David T. Lewis -
Eliot Miranda -
Esteban Lorenzano -
Norbert Hartl