From: Kevin Pendleton <kevin@electron-pc.com>
Cc: guile-user@gnu.org
Subject: Re: Guile 6.4 on NCR MPRAS
Date: 30 Mar 2004 17:30:44 -0700 [thread overview]
Message-ID: <1080693044.17135.847.camel@s11> (raw)
In-Reply-To: <87brmedm7u.fsf@zip.com.au>
On Tue, 2004-03-30 at 15:05, Kevin Ryde wrote:
> Kevin Pendleton <kevin@electron-pc.com> writes:
> >
> > When checking for gethostbyname, it fails both
> > times, (undefined reference to `gethostbyname'), with and without
> > -lnsl.
>
> config.log will contain the code of the failing program, you can see
> if it works or if it needs to be massaged.
>
I am also working on compiling some other programs and I noticed that
Tcl's configure was able to find gethostbyname, so I took a look at the
way it is done there and noticed this comment:
#--------------------------------------------------------------------
# Check for the existence of the -lsocket and -lnsl libraries.
# The order here is important, so that they end up in the right
# order in the command line generated by make. Here are some
# special considerations:
# 1. Use "connect" and "accept" to check for -lsocket, and
# "gethostbyname" to check for -lnsl.
# 2. Use each function name only once: can't redo a check because
# autoconf caches the results of the last check and won't redo it.
# 3. Use -lnsl and -lsocket only if they supply procedures that
# aren't already present in the normal libraries. This is because
# IRIX 5.2 has libraries, but they aren't needed and they're
# bogus: they goof up name resolution if used.
# 4. On some SVR4 systems, can't use -lsocket without -lnsl too.
# To get around this problem, check for both libraries together
# if -lsocket doesn't work by itself.
#--------------------------------------------------------------------
Looking at the configure for guile it attempts to find connect after
gethostbyname, etc. Comparing the two configure files, there have been
some small changes to those functions as well. It looks like guile's
configure was made with Autoconf 2.57 and Tcl's configure was made with
Autoconf 2.59. Is it possible that this has already been hashed out and
resolved? What is the best way to recreate configure? Should I just
manually change configure and send in the diff?
> I see libtool AC_CHECK_LIBM knows to do this on *-ncr-sysv4.3*. We
> should either use that, or do something similar. Does a program using
> say "cos" fail to link if -lm is used but not -lmw too?
>
I know I have had problems with this in the past but am currently unable
to remember with what.
Kevin
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-31 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 0:26 Guile 6.4 on NCR MPRAS Kevin Pendleton
2004-03-27 21:33 ` Kevin Ryde
2004-03-29 23:00 ` Kevin Pendleton
2004-03-30 22:05 ` Kevin Ryde
2004-03-31 0:30 ` Kevin Pendleton [this message]
2004-03-31 0:44 ` Kevin Ryde
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 20:45 Kevin Pendleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1080693044.17135.847.camel@s11 \
--to=kevin@electron-pc.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).