Very Computer

I used autoconf+automake with a little program I'm working on (lang:C).
There's really no network code except for gethostname and gethostbyname,
the latter which causes some trouble on SunOS (unresolved symbol) but no
other *nix I've tried yet.

When I compile manually on SunOS I use -lnsl (NSL lib). I thought
autoconf/automake was supposed to automate detection of just such things?
Or not? Is this a 'special case' I should add into my configure.ac ? So far
I have these relevant references in configure.ac

AC_CHECK_HEADERS(... netdb.h ...)
AC_CHECK_FUNCS(gethostname)

But apparently that's not enough. Any suggestions?

--
Jem Berkes
Student IEEE (Canada)

http://www.pc-tools.net/
Windows, Linux & UNIX software

  The code you show will let autoconf detect whether you have the headers
 and functions defined - but it doesn't do the job of updating your build
 command to include the correct libraries in the link stage.

  What you've done is tested that you have the headers, so in your code
 you can use:

#ifdef HAVE_NETDB
#include <netdb.h>
#endif

   To actually include the nsl library, conditionally, you should make use
 of the macro from the GNU Autoconf archive:

   http://www.gnu.org/software/ac-archive/Miscellaneous/etr_socket_nsl.html

   Include that code in your configure.in, then add a call to it:

ETR_SOCKET_NSL

   That will then do the linking properly.  (Notice that the macro as
 presented only updates the flags for gcc, not g++...)

Steve
----
# GNU MP3 /OGG Streamer
http://www.gnump3d.org/

Quote:>> When I compile manually on SunOS I use -lnsl (NSL lib). I thought
>> autoconf/automake was supposed to automate detection of just such
>> things? Or not?

>   What you've done is tested that you have the headers, so in your
>   code
>  you can use:

OK, I discovered that config.h file so now I better understand how to use
that in my application.

Quote:>    To actually include the nsl library, conditionally, you should make
>    use
>  of the macro from the GNU Autoconf archive:
> ETR_SOCKET_NSL

I checked that out, but I also found another way that seems to do it. The
only network function call I use is gethostbyname, so:

AC_CHECK_LIB(nsl, gethostbyname)

This seems to work on my Linux system and the SunOS systems. Wish I had
more *nix systems to test on!!

--
Jem Berkes
Student IEEE (Canada)

http://www.pc-tools.net/
Windows, Linux & UNIX software

It works because gethostbyname is linked it via the C library and
adding -lnsl doesn't make a difference. You need to test it first
_without_ -lnsl and then with to find out if the nsl library is
required. Or at least this is one of the ways to do it.

--
Thamer Al-Harbash    http://www.whitefang.com/