From: Kevin Pendleton <kevin@electron-pc.com>
Cc: guile-user@gnu.org
Subject: Re: Guile 6.4 on NCR MPRAS
Date: 29 Mar 2004 16:00:14 -0700 [thread overview]
Message-ID: <1080601214.26165.709.camel@s11> (raw)
In-Reply-To: <87ptay9drc.fsf@zip.com.au>
On Sat, 2004-03-27 at 14:33, Kevin Ryde wrote:
> Kevin Pendleton <kevin@electron-pc.com> writes:
> >
> > I then set LIBS="-lm -lmw -lnsl"
>
> configure is supposed to grab -lnsl when needed, by looking for
> gethostbyname. You can check if that's happened. It ought to get
> into libguile.la as a dependency.
>
Looking at it all again, I have found that there are just the two LIBS
that are needed. I did not need to add "-lm". "-lnsl" does not get
added appropriately. When checking for gethostbyname, it fails both
times, (undefined reference to `gethostbyname'), with and without
-lnsl. Here's the synopsis from the man page for gethostbyname for
MPRAS:
#include <sys/types.h>
#include <sys/socket.h>
#include <netdb.h>
struct hostent *gethostent()
struct hostent *gethostbyaddr(addr, len, type)
char *addr;
int len, type;
struct hostent *gethostbyname(name)
char *name;
sethostent(stayopen)
int stayopen
endhostent()
> What's -lmw and what's it needed for?
The way I understand it, for NCR MP-RAS systems, the system needs to
explicitly link against -lmw to pull in some symbols such as
_mwoflocheckl and others. This was discovered during the configuration
of perl for MPRAS. For more details on the perl hints file see:
http://search.cpan.org/src/JHI/perl-5.8.1/ext/POSIX/hints/svr4.pl
If I include -lnsl and not -lmw I get the following two errors:
./.libs/libguile.so: undefined reference to `_mwvalidcheckl'
./.libs/libguile.so: undefined reference to `_mwoflocheckl'
>
> > FAIL: srfi-19.test: SRFI date/time library: #<procedure time-utc->date
> > (time . tz-offset)> respects local DST if no TZ-OFFSET given
>
> Might be the way TZ is changed only with putenv (in the tests). I
> think configure decides a LOCALTIME_CACHE for when tzset needs to be
> called (and it's then called by `localtime' etc). You might have to
> investigate further.
I'll have to continue to look into this part.
Thanks,
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-29 23:00 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 [this message]
2004-03-30 22:05 ` Kevin Ryde
2004-03-31 0:30 ` Kevin Pendleton
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=1080601214.26165.709.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).