unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: 1.8 status and 64-bit data corruption
Date: Tue, 28 Mar 2006 21:56:55 +0100	[thread overview]
Message-ID: <87fyl2i8yw.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87d5g98ibo.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sun, 26 Mar 2006 14:08:11 +0100")

Neil Jerram <neil@ossau.uklinux.net> writes:

> I believe the only important 1.8 bug still outstanding is the one
> which causes Scheme data corruption on 64-bit platforms - and which is
> usually enough to cause the build to fail in
> snarf-check-and-output-texi.

Someone has been kind enough to loan me an account on a 64-bit
machine:

neil@we:~/guile-core-1.8-20060328$ uname -a
Linux we 2.6.8-11-amd64-k8-smp #1 SMP Wed Jun 1 00:01:27 CEST 2005 x86_64 GNU/Linux

But using the latest 1.8 snapshot, guile-core-1.8-20060328.tar.gz, I
can't reproduce the problem, either with straight `./configure; make'
or with `env CC="gcc -m64" ./configure; make'.

Is this because something got fixed in 1.8 CVS, or because I'm missing
some important ingredient of the builds which were reported as failed?

The gcc on this machine is:

neil@we:~/guile-core-1.8-20060328$ gcc --version
gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Any input much appreciated.

Regards,
    Neil



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


  reply	other threads:[~2006-03-28 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 13:08 1.8 status and 64-bit data corruption Neil Jerram
2006-03-28 20:56 ` Neil Jerram [this message]
2006-03-29 10:07   ` Andy Wingo
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29 15:12 Bill Schottstaedt
2006-03-29 15:40 ` Jay Cotton
2006-04-15 12:45 Bill Schottstaedt

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=87fyl2i8yw.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    /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).