Re: trouble with files bigger than 4GB

Would it be sufficient to have kind of the following shell script (named 
gcc) before the real gcc in the path?

#!/bin/sh
exec /usr/local/bin/gcc -m64 ${1+"$@"}

/ Raimo Niskanen, Erlang/OTP, Ericsso AB



Vance Shipley wrote:
> I can tell you what I had to do to build a 64 bit emulator.  I built
> and installed a version of gcc which used -m64 as the default.  Then
> when running configure and make on the source distribution I had that
> version of gcc first in the path.
>
>         -Vance
>
> On Wed, Apr 23, 2003 at 10:18:49PM +0200, Daniel Solaz wrote:
> }  
> }  On 32bit Solaris, adding -D_FILE_OFFSET_BITS=64 to the cc call does the 
> }  trick: off_t becomes 8 bytes long, fopen() means fopen64(), etc.  
> }  However, according to the docs, this does interact badly with some 
> }  other OS subsystems.
> }  
> }  So I'd like to try this first and report whether things work, or at 
> }  least seem to.  But I lack the expertise required to hack configure so 
> }  that it compiles the off_t size test with -D_FILE_OFFSET_BITS=64 and 
> }  generates new Makefiles with -D_FILE_OFFSET_BITS=64 in them.  Can 
> }  anyone give me a pointer?
> }  
> }  -Daniel