[openbeos] Build issues: close(), rmdir(), etc called without being defined on several places!?
- From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 21 May 2003 14:08:59 GMT
Hi all,
Am I the only to find strange that build choke on missing close(),
rmdir(), read() & co functions definitions, when
it was clearly not an issue previously?
I've started to fix that by including unistd.h in some place :
- current/src/add-ons/print/transports/parallel_port/
print_transport.cpp
- current/src/servers/print/Printer.cpp
But, then, I fall on current/src/kits/storage/Node.cpp:
C++ ../objects/x86.R1/kits/Node.o
/data/projects/openbeos/current/src/kits/storage/Node.cpp: In method
`void BNode::close_fd()':
/data/projects/openbeos/current/src/kits/storage/Node.cpp:687: implicit
declaration of function `int close(...)'
Same for Session.cpp:
C++ ../objects/x86.R1/kits/storage/Session.o
/data/projects/openbeos/current/src/kits/storage/Session.cpp: In method
`status_t BSession::GetPartitioningParameters(const char *, class
BString *, class BRect = BRect(), bool * = 0)':
/data/projects/openbeos/current/src/kits/storage/Session.cpp:308:
implicit declaration of function `int close(...)'
So, I start to wonder if I don't miss something here, maybe there is no
problem at all, but my local configuration?
Yes, I run ./configure recently.
AFAIK, close(), rmdir(), read(), etc are only defined in unistd.h, no?
These files should have include it to use these functions calls,
shouldn't they?
-Philippe, seeing build issues where they're... or not!?
--
Fortune Cookie Says:
Good news is just life's way of keeping you off balance.
Other related posts:
- » [openbeos] Build issues: close(), rmdir(), etc called without being defined on several places!?
