Problem with configure falsely detecting presence of system routines (while porting to NSK)

[Kelly F. Hickel]

OK, it looks like the configure script is much more complicated since
1.10.x (big surprise!).  Now it builds a lot of conftest examples to try
and detect OS system calls that are available.  The problem is that the
linker writes the file anyway, you only find out about unresolved
symbols at run time.  Since configure doesn't actually attempt to run
the test, just see if it links, it thinks all the functions it wants are
available. (bummer).

There should be a way to make the linker act like I want it too (seems
like just putting it into static mode should do the trick, but it hasn't
worked that way yet), but I haven't found it yet, and the reams of
manuals (and the software I could use to access them online) are at the
office, so I can't use them until Monday.

Anyone have any bright ideas?

-Kelly