unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Pendleton <kevin@electron-pc.com>
Subject: Re: Guile 6.4 on NCR MPRAS
Date: 26 Mar 2004 17:26:31 -0700	[thread overview]
Message-ID: <1080347191.26226.418.camel@s11> (raw)

I took a look at the code and realized that it just didn't realize what
my machine type was.  I changed line 380 in the file
./guile-1.6.4/libguile/gc_os_dep.c to this:

# ifndef mach_type_known
#    define I386
#    define SYSV
#    define mach_type_known
# endif

And then I got these errors:

gcc -g -O2 -Wall -Wmissing-prototypes -o .libs/guile .libs/guileS.o guile.o -Wl,--export-dynamic
 ./.libs/libguile.so /usr/local/src/guile164/libguile-ltdl/.libs/libguile-ltdl.so -ldl -lcrypt -lm -Wl,--rpath -Wl,/usr/gnu/lib
./.libs/libguile.so: undefined reference to `recv'
./.libs/libguile.so: undefined reference to `connect'
./.libs/libguile.so: undefined reference to `_mwvalidcheckl'
./.libs/libguile.so: undefined reference to `recvfrom'
./.libs/libguile.so: undefined reference to `gethostbyaddr'
./.libs/libguile.so: undefined reference to `socket'
./.libs/libguile.so: undefined reference to `send'
./.libs/libguile.so: undefined reference to `accept'
./.libs/libguile.so: undefined reference to `h_errno'
./.libs/libguile.so: undefined reference to `bind'
./.libs/libguile.so: undefined reference to `setsockopt'
./.libs/libguile.so: undefined reference to `sendto'
./.libs/libguile.so: undefined reference to `listen'
./.libs/libguile.so: undefined reference to `inet_ntoa'
./.libs/libguile.so: undefined reference to `shutdown'
./.libs/libguile.so: undefined reference to `gethostbyname'
./.libs/libguile.so: undefined reference to `getpeername'
./.libs/libguile.so: undefined reference to `_mwoflocheckl'
./.libs/libguile.so: undefined reference to `getsockopt'
./.libs/libguile.so: undefined reference to `getsockname'
collect2: ld returned 1 exit status
make[2]: *** [guile] Error 1
make[2]: Leaving directory `/usr/local/src/guile164/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/guile164'
make: *** [all] Error 2


I then set LIBS="-lm -lmw -lnsl" and re-configured and it was able to
compile fine.  When I run a make check I get the following results:

Running alist.test
Running bit-operations.test
Running c-api.test
Running chars.test
Running common-list.test
Running environments.test
Running eval.test
Running exceptions.test
Running format.test
Running gc.test
Running getopt-long.test
Running goops.test
Running guardians.test
Running hooks.test
Running import.test
Running interp.test
Running list.test
Running load.test
Running numbers.test
Running optargs.test
Running ports.test
Running r4rs.test
Running reader.test
Running regexp.test
Running srfi-10.test
Running srfi-13.test
Running srfi-14.test
Running srfi-19.test
FAIL: srfi-19.test: SRFI date/time library: #<procedure time-utc->date
(time . tz-offset)> respects local DST if no TZ-OFFSET given
FAIL: srfi-19.test: SRFI date/time library: #<procedure time-tai->date
(time . tz-offset)> respects local DST if no TZ-OFFSET given
FAIL: srfi-19.test: SRFI date/time library: #<procedure
time-monotonic->date (time . tz-offset)>
respects local DST if no TZ-OFFSET given
FAIL: srfi-19.test: SRFI date/time library: #<procedure julian-day->date
(jdn . tz-offset)> respects local DST if no TZ-OFFSET given
FAIL: srfi-19.test: SRFI date/time library: #<procedure
modified-julian-day->date (jdn . tz-offset)> respects local DST if no
TZ-OFFSET given
FAIL: srfi-19.test: SRFI date/time library: string->date respects local
DST if no time zone is read
Running srfi-4.test
Running srfi-9.test
Running strings.test
Running symbols.test
Running syncase.test
Running syntax.test
Running time.test
Running version.test
Running weaks.test

Totals for this test run:
passes:                 2227
failures:               6
unexpected passes:      0
expected failures:      18
unresolved test cases:  0
untested test cases:    0
unsupported test cases: 9
errors:                 0

FAIL: check-guile
===================
1 of 1 tests failed
===================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/usr/local/src/guile164'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/usr/local/src/guile164'
make: *** [check-recursive] Error 1

Are these failures important and are they just system-specific?  I can
provide my check-guile.log if needed.

Thanks for any help,

Kevin



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2004-03-27  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-27  0:26 Kevin Pendleton [this message]
2004-03-27 21:33 ` Guile 6.4 on NCR MPRAS 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
  -- 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=1080347191.26226.418.camel@s11 \
    --to=kevin@electron-pc.com \
    /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).