[Williams Mark L DLPC <WilliamsML@ncsc.navy.mil>] BUILD FAILURE, GUILE 1.6.1 ON SOLARIS 8, SPARC

[Williams Mark L DLPC <WilliamsML@ncsc.navy.mil>] BUILD FAILURE, GUILE 1.6.1 ON SOLARIS 8, SPARC

[Mikael Djurfeldt]

[-- 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