About errno
<< split from /usr/bin/ld: errno: TLS definition in /lib/libc.so.6 >>
Hello Folks,
thanks you helped me a lot. But I've still got one question: Is there a possibility to test out if I must either import errno or should include the file.
Something like
Thanks a lot!Code:#ifdef THIS_IS_THE_DEFINE_I_NEED #include <errno.h> #else extern int errno; #endif
beachcoder
You should always just include errno.h, for the reasons matsp says in the other thread.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Hi Salem!
Thanks for your info. The problem is that I've had this problem on a very old software, which must be backward-compatible and must compile under Linux same as unter AIX, Solaris and NCR and such systems.
Are you sure it is available on Systems released within the past 10 or 15 years?
Anyway, I now put the new version on and try to port. If the problem comes up, I will try to find another solution.
Thanks again,
beachcoder
errno.h has been a C-standard header file for the last 20 years.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
