From: Paul Emsley <emsley@ysbl.york.ac.uk>
Cc: guile-user@gnu.org
Subject: Re: compiling 1.8.0
Date: Mon, 07 Aug 2006 13:40:30 +0100 [thread overview]
Message-ID: <1154954430.3543.68.camel@localhost.localdomain> (raw)
In-Reply-To: <44D45FF0.3050206@student.liu.se>
On Sat, 2006-08-05 at 11:08 +0200, Claes Wallin wrote:
> Paul Emsley wrote:
> > Dear Guile users,
> >
> > I have a problem compiling/running 1.8.0:
> >
> > $ ./configure --prefix=$pfx
> > $ make
> > $ make install
> > $ cd $pfx/bin
> > �$ ./guile
> > Backtrace:
> > In unknown file:
> > ...
> > ?: 123 [list apply ...
> > ?: 124* [list lambda (syntmp-dummy-3 syntmp-name-4 syntmp-rules-5) ...
> > ?: 125* [syntmp-chi-151 #(syntax-object # #) (# # # # ...) ...
> > ?: 126* [syntmp-make-binding-wrap-132 (# # #) ("i" "i" "i") (())]
> > ?: 127 (if (null? syntmp-ids-949) syntmp-w-951 ...)
> > ?: 128 [cons () ...
> > ?: 129* [cons ...
> > ?: 130* (let* ((syntmp-labelvec-952 #)) (let* (#) (let # #)))
> > ?: 131 (let* ((syntmp-n-953 #)) (let (# #) (begin # #)))
> > ...
> > ?: 132 (begin # #)
> > ?: 133* [syntmp-f-956 (# # #) 0]
> > ?: 134 (if (not #) (call-with-values # #))
> > ...
> > ?: 135 [call-with-values #<procedure #f ()> #<procedure #f #>]
> > ?: 136 (@call-with-values (producer consumer))
> > ?: 137* [#<procedure #f ()>]
> > ?: 138* [syntmp-id-sym-name&marks-116 #(syntax-object dummy #) (())]
> > ?: 139 (if (syntmp-syntax-object?-101 syntmp-x-980) (values # #) ...)
> > ?: 140* [syntmp-syntax-object?-101 #(syntax-object dummy (# # # shift .. .))]
> > ?: 141 (and (vector? syntmp-x-1008) (= (vector-length syntmp-x-1008) 3) ...)
> > ?: 142* (vector? syntmp-x-1008)
> >
> > <unnamed port>: In expression (vector? syntmp-x-1008):
> > <unnamed port>: Stack overflow
> >
> > This happens on all the computers I've tried to compile 1.8.0 on.
> > Can you help?
>
> Like someone pointed out to me a couple of weeks ago on another list,
> compiling with optimizations is necessary for guile to work correctly. So:
>
> $ ./configure --prefix=$pfx CFLAGS=-O2
>
> That should do it.
>
> Is this documented somewhere? If not, shouldn't it be? And if it is,
> shouldn't it be documented more prominently, like in INSTALL? Or, since
> it's a requirement for guile working correctly, could it even be a
> standard CFLAGS in configure?
Hi Claes,
Yes indeed - that was the fix. Thanks!
For the record it was compiling with default flags (including -g) that
was the problem. -O and -O2 works.
I echo your comments about documentation.
Cheers,
Paul.
now off to play with threads...
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2006-08-07 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 17:56 compiling 1.8.0 Paul Emsley
2006-08-05 9:08 ` Claes Wallin
2006-08-07 12:40 ` Paul Emsley [this message]
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=1154954430.3543.68.camel@localhost.localdomain \
--to=emsley@ysbl.york.ac.uk \
--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).