It seems that in the generic case, that testing to determine the size  
of off_t is the key.  If off_t is 4 and one wants to support large  
filesystems, then the xxxx64 variants of the file functions are  
needed.  If on the other hand off_t is 8 then they are not needed.

I chose MACOSX, because I saw it being passed on the command line in  
the make file execution.

I could use some help in proper placement, because I tried adding it  
to the top, and still got not defined in scope messages.

Bruce

On Apr 1, 2010, at 10:40 AM, Mark Miesfeld wrote:

> On Thu, Apr 1, 2010 at 9:53 AM, CVBruce <cvbr...@gmail.com> wrote:
>
>> Also, open64() is not supported because open() supports 64 bit
>> operating systems.
>>
>> My quick and dirty #define lseek64 lseek didn't work.  It looks  
>> like I
>> have some more work to do.
>
> This looks like it works for other people:
>
> #ifdef __APPLE__ & __MACH__
> #define lseek64 lseek
> #define open64 open
> #endif
>
> Not suggesting it as the proper long term fix.  Just something to try
> to see if it works.  Are you sure you are putting the defines in a
> place where they are picked up properly?
>
> Long term, fixing the configure script seems like a possible  
> solution to me.
>
> Rick usually has good ideas for portable code, maybe he has an idea.
>
> --
> Mark Miesfeld
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to