From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: WilliamsML@ncsc.navy.mil
Subject: [Williams Mark L DLPC <WilliamsML@ncsc.navy.mil>] BUILD FAILURE, GUILE 1.6.1 ON SOLARIS 8, SPARC
Date: Wed, 22 Jan 2003 14:25:40 +0100 [thread overview]
Message-ID: <xy7u1g12u5n.fsf@nada.kth.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
I think it is a bad idea to run Guile on the docfiles while
suppressing the output as the first thing after it's built.
While developing for Guile it happens to me all the time that build
gets stuck at this place without any explanation.
What about running the test-suite at this point instead, and make sure
that also primary error messages (not relating to the tests) gets to
standard output so that one can see what is wrong?
[-- Attachment #2: Type: message/rfc822, Size: 4259 bytes --]
From: Williams Mark L DLPC <WilliamsML@ncsc.navy.mil>
To: guile-user@gnu.org
Subject: BUILD FAILURE, GUILE 1.6.1 ON SOLARIS 8, SPARC
Date: Wed, 22 Jan 2003 06:46:44 -0600
Message-ID: <F42966A0479AD4118AE6009027D08CEB0555FF31@dlpcexch02.ncsc.navy.mil>
I'm getting a segmentation fault at the snarf-check-and-output-texi stage in
the build. This is reported with a "gmake[2]: *** [guile.texi] Error 1"
message (gmake is Gnu make vs. Solaris make). As I read it, a bunch of .doc
files from <buildDir>/libguile are cat'd into the script, which should
generate a guile.texi file (and then other stuff). The cat works ok; the
script bombs. I don't know Scheme (yet?), so I can't poke around in the
script to figure out the problem. Any suggestions?
Thanks in advance...
Mark L. Williams
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-01-22 13:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xy7u1g12u5n.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--cc=WilliamsML@ncsc.navy.mil \
/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).