I call out for all you porting gurus

Hi!

I'm about to port my first Linux tool to Amiga (using OS4 and the public SDK), but the first error is this:
"error: sys/file.h: No such file or directory"

Simple, eh?
This file must be used by numeros ported tools, so what do I need to install etc. to not run into a million similar "easy" setbacks?

You porting gurus must know!

@Deniil

#ifndef __amigaos4__
#include <sys/file.h>
#endif

@Deniil

download my porting for dummies guide from os4depot.
i list a lot of common errors and how to fix them, good luck!

btw, what tool is it?

@afxgroup

Oh my god it worked! The whole program compiled

Well, almost, I got some linker errors about unix owner something. Think I can get around that..

Thankyou!

Btw. Do you happen to know if the ANSI file functions support 64-bit when using g++ straight off on OS4, or do I need to rewrite all that into OS4 dos.library??
No problem, just wondering...

@spotUp

That's a secret ;)
No it's unrar and my aim is 64-bit ability to be able to extract huge rar archives usually divided into 50MB chunks.

Perhaps it's already done in the existing port though without it being mentioned.... don't know..

@Deniil

Do you need to know how to call OS4 with 64-bit file sizes?

Maybe I could write a short tutorial if no one else has done so already.

@Deniil

Quote:The standard functions are 32 bit, to use 64 bit C library I/O you have to use 64 bit functions like fopen64(), ftello64(), fseeko64(), etc., which require a new SDK.

@tonyw

I'm not exactly new at programming so I'll probably figure that out.
Thanks anyway!
(unless there are some tricky pitfalls you know about that are common to fall into!)

@joerg

Ok. So since the program compiled when configured for 64-bit it expects normal fopen, fseek etc to return 64-bit sizes, which won't work at all then..?

So: Do I wait for a new SDK (how long?) or do I replace all file I/O functions with AmigaOS 64-bit calls?