Craig Rodrigues wrote: > % gcc test.c > /tmp/cc6AHohn.o: In function `main': > /tmp/cc6AHohn.o(.text+0x11): undefined reference to `sigqueue' > /tmp/cc6AHohn.o(.text+0x22): undefined reference to `sigtimedwait' > /tmp/cc6AHohn.o(.text+0x31): undefined reference to `sigwaitinfo' > > If I look in signal.h, I find: > #ifdef _P1003_1B_VISIBLE > > __BEGIN_DECLS > int sigqueue __P((_BSD_PID_T_, int, const union sigval)); > int sigtimedwait __P((const sigset_t *, siginfo_t *, const struct timespec *)); > int sigwaitinfo __P((const sigset_t *, siginfo_t *)); > __END_DECLS > > #endif
FreeBSD 4.5 doesn't define these externs in the _P1003_1B_VISIBLE case. The system call slots are reserved, but not defined. THe same is true of the Linux emulation. So: 1) Upgrade your FreeBSD; FreeBSD 4.3 gets this wrong. 2) Don't use these functions in FreeBSD. > So, apparently _P1003_1B_VISIBLE is somehow being defined by the > header files, but these particular functions are not available. The 4.3 header file is incorrectly conditioning the prototypes on the manifest constant you are using. According to my copy of the SUS v2, this is part of the queued signals interface extension for the POSIX RT extensions. THe correct feature test macro for this is: #ifdef _POSIX_REALTIME_SIGNALS A correct workaround, if that doesn't work, is: #if defined(_POSIX_REALTIME_SIGNALS) && defined(SIGRTMIN) The "bash" shell uses "SIGRTMIN". If you use *just* that, then your code will be broken on AIX, just like "bash" is broken on AIX. > Can someone tell me how I can detect if these functions are available > on a system at compile time? I cannot use an autoconf type of test, > and need to use a preprocessor macro type of test. > > It seems to me that this particular definition of _P1003_1B_VISIBLE > is broken if it is enabling symbols in header files to appear > which cannot be linked on a generically configured FreeBSD system. Yes. It's both broken in 4.3, and your uise of it instead of the real manifest constant, _POSIX_REALTIME_SIGNALS, is also broken. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message