From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Guile 6.4 on NCR MPRAS
Date: Wed, 31 Mar 2004 10:44:36 +1000 [thread overview]
Message-ID: <87brmddevf.fsf@zip.com.au> (raw)
In-Reply-To: <1080693044.17135.847.camel@s11> (Kevin Pendleton's message of "30 Mar 2004 17:30:44 -0700")
Kevin Pendleton <kevin@electron-pc.com> writes:
>
> # 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.
AC_SEARCH_LIBS probably covers this. Probe libraries, add them if
they're needed, don't add them if they're not.
> # 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.
Or I presume just ensure -lnsl is probed first.
> Is it possible that this has already been hashed out and resolved?
Probably not.
> What is the best way to recreate configure?
You can try going from the guile cvs, either the head or the
branch_release-1-6, and have a look at autogen.sh.
Modest fixes can get into the 1.6 branch, major surgery will have to
wait for the head and the next major release.
> Should I just manually change configure and send in the diff?
No, not configure, but you can advise what's needed for configure.in.
_______________________________________________
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:44 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
2004-03-31 0:44 ` Kevin Ryde [this message]
-- 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=87brmddevf.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).