From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: guile 1.8 and x86_64
Date: Tue, 11 Apr 2006 21:37:59 +0100 [thread overview]
Message-ID: <87zmirvoew.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <8656DB86D246C1D9ACD84549@tribes2.stanford.edu> (Quanah Gibson-Mount's message of "Mon, 10 Apr 2006 16:03:23 -0700")
Quanah Gibson-Mount <quanah@stanford.edu> writes:
> amd64-linux26:/afs/ir/src/pubsw/languages/guile-1.6.7> /usr/pubsw/bin/gcc -v
> Using built-in specs.
> Target: x86_64-unknown-linux-gnu
> Configured with: ../../gcc-4.0.2/configure --datadir=/lib
> --libexecdir=/lib --sharedstatedir=/lib --prefix=/usr/pubsw
> --enable-threads --with-gnu-as --with-as=/usr/pubsw/bin/as
> --with-gnu-ld --with-ld=/usr/pubsw/bin/ld
> --with-libintl-prefix=/usr/pubsw --with-libiconv-prefix=/usr/pubsw
> --disable-multilib --enable-libada
> --enable-languages=c,c++,f95,objc,ada
> Thread model: posix
> gcc version 4.0.2
[...]
Many thanks; we are working on this and hope to have a fix soonish.
If you are keen to have Guile 1.8 working on this box, we believe a
successful workaround is to compile with an older GCC. 3.3.5 seems
OK, for example.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-04-11 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 19:40 guile 1.8 and x86_64 Quanah Gibson-Mount
2006-04-10 8:14 ` Ludovic Courtès
2006-04-10 22:55 ` Neil Jerram
2006-04-10 23:03 ` Quanah Gibson-Mount
2006-04-11 20:37 ` Neil Jerram [this message]
2006-04-11 20:52 ` Quanah Gibson-Mount
2006-05-05 14:05 ` Miroslav Lichvar
2006-05-06 11:12 ` Miroslav Lichvar
2006-05-07 21:29 ` Marius Vollmer
2006-05-08 10:28 ` Andy Wingo
2006-05-08 21:52 ` Marius Vollmer
2006-05-09 6:49 ` Neil Jerram
2006-05-09 13:23 ` Andy Wingo
2006-05-09 22:31 ` Default stack limit Marius Vollmer
2006-05-10 14:31 ` Andy Wingo
2006-05-10 23:58 ` Kevin Ryde
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=87zmirvoew.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).