unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Steve Juranich <sjuranic@gmail.com>
Subject: Re: x86_64 / gcc4 problems
Date: Fri, 24 Feb 2006 22:49:47 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060224T234747-131@post.gmane.org> (raw)
In-Reply-To: 20060219223052.2A67A1331D@firefly.is-a-geek.org

hyperdivision <hyperdivision <at> firefly.is-a-geek.org> writes:


> i'm still having no luck building guile-cvs under 64-bit mode
> on my amd64.
> it builds fine using "gcc -m32", but 64 doesn't build.
> and since it is runtime problems, not compiling,
> i'm not quite sure what to do to track it down.
> if someone could give me a hand i would appreciate it.

> if i use -O or -ON it dies during the make of guile.texi,
> otherwise, without or with -g i get a stack overflow in ice-9
> during the command:
> ../pre-inst-guile -s ./compile-psyntax.scm \
>   ./psyntax.ss ./psyntax.pp

I'm getting the same problems here, build process is dying in the same spot
(system is AMD Opteron, Fedora Core 4).  Haven't trying playing around with the
flags, though.

I also reported this on guile-user, I didn't notice that bug reports should go
to a separate place.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


      reply	other threads:[~2006-02-24 22:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 22:30 x86_64 / gcc4 problems hyperdivision
2006-02-24 22:49 ` Steve Juranich [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=loom.20060224T234747-131@post.gmane.org \
    --to=sjuranic@gmail.com \
    /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).