From: Andy Wingo <wingo@pobox.com>
Cc: mvo@gnu.org, guile-devel@gnu.org
Subject: Re: compile fixen
Date: Tue, 11 Oct 2005 13:20:29 +0200 [thread overview]
Message-ID: <1129029629.19772.42.camel@localhost.localdomain> (raw)
In-Reply-To: <87k6gmxtdl.fsf@zip.com.au>
On Mon, 2005-10-10 at 07:39 +1000, Kevin Ryde wrote:
> Andy Wingo <wingo@pobox.com> writes:
> >
> > Also the build stopped when building the texinfo files, because I had no
> > version.texi. I had to make stamp-vti in the doc/ref and doc/tut dirs to
> > make the version.texi files,
>
> That shouldn't be necessary, they're ordinary makefile targets
> (generated by automake). Maybe automake needed a re-run for changes
> in the texi files?
Not sure what happened exactly; running autogen.sh should have run
automake and thus created the files.
I have made a fresh checkout here at work, on a different machine (SMP
x86-64) and guile just doesn't build. At first building with CFLAGS=-g
-O2 I got some kind of deadlock in guile after a memoization error, and
now building with CFLAGS=-g I get a segfault making
guile-procedures.texi, in gc-mark.c:411.
So guile doesn't build at all on this 64-bit box. Any idea why?
Regards,
--
Andy Wingo
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-11 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 19:41 compile fixen Andy Wingo
2005-10-09 21:39 ` Kevin Ryde
2005-10-11 11:20 ` Andy Wingo [this message]
2005-12-06 22:38 ` Marius Vollmer
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=1129029629.19772.42.camel@localhost.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mvo@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).