unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: guile-1.8.1 - problems on AMD64
Date: Thu, 12 Oct 2006 14:58:58 +0200	[thread overview]
Message-ID: <87r6xdher1.fsf@laas.fr> (raw)
In-Reply-To: <20061011110153.GA12594@basalt.office.altlinux.org> (Stanislav Ievlev's message of "Wed, 11 Oct 2006 15:01:53 +0400")

Hi,

Stanislav Ievlev <inger@altlinux.org> writes:

> On Tue, Oct 10, 2006 at 10:23:31AM +0200, Ludovic Court?s wrote:
>> Hi,
>> 
>> Stanislav Ievlev <inger@altlinux.org> writes:
>> 
>> > <unnamed port>: In expression (vector-length syntmp-x-1008):
>> > <unnamed port>: Stack overflow
>> 
>> Did you compile with `-O0'?  If so, make sure you compile at least with
>> `-O1'.
> You have problems with optimization disabled?

Personally, no.  ;-)  But Guile eats up a lot of stack space when
compiled with `-O0', to the point that you can't get to the REPL (with
the default stack limit), hence my suggestion to use `-O1'.

> However, guile does not build with glibc >=2.4 when -D_FORTIFY_SOURCE=2 is
> added to CFLAGS:

I was unaware of that flag.  Is it documented somewhere?

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2006-10-12 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  6:34 guile-1.8.1 - problems on AMD64 Stanislav Ievlev
2006-10-10  8:23 ` Ludovic Courtès
2006-10-11 11:01   ` Stanislav Ievlev
2006-10-11 20:08     ` Kevin Ryde
2006-10-12 12:58     ` Ludovic Courtès [this message]
2006-10-13  6:26       ` Stanislav Ievlev
2006-10-13  7:38         ` Ludovic Courtès
2006-10-14 13:13           ` Neil Jerram
2006-10-16  6:25             ` Stanislav Ievlev
2006-10-16  8:04               ` Ludovic Courtès
2006-10-19 18:46                 ` Neil Jerram
2006-10-21 13:12                   ` Ludovic Courtès

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=87r6xdher1.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@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).