On Mon, 19 Jan 2004, Hanspeter Roth wrote: > On Jan 19 at 12:58, Thomas Dickey spoke: > > > On Mon, 19 Jan 2004, Hanspeter Roth wrote: > > > > > On Jan 19 at 08:58, Bob Friesenhahn spoke: > > > > > > > The key is to not use C++ to execute these tests. Use C while > > > > checking for library functions. Only set the language to C++ while > > > > testing C++ related features. > > > > > > Does it make sense to run test in C while the function getloadavg() is > > > used in a C++ Module? > > > > no. He's telling you how to get some use out of the tool as it is > > written. (Another one for the unwritten autoconf-FAQ). Some of the > > autoconf tests for C functions may happen to work when run from C++. > > So should the invokation of getloadavg() be moved to a separate C > module and then call the C function that calls getloadavg() from a > C++ module? That might be a better design - it would at least get rid of the problem of C++ breaking the configure test. Since it's not standard, there's no guarantee that its prototype is the same across all implementations. The various Linux and *BSD platforms tend to make random uncoordinated changes to the legacy BSD functions, sprinking const's in their prototypes. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net