all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@MIT.EDU>
Cc: Chip Coldwell <coldwell@redhat.com>, emacs-devel@gnu.org
Subject: Re: 22.0.99 emacs dumper (?) problem
Date: Mon, 21 May 2007 03:49:04 -0400	[thread overview]
Message-ID: <bhy7ji39cf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <unusl9q3lhl.fsf@all-night-tool.mit.edu> (Chong Yidong's message of "20 May 2007 23:26:46 -0400")

Chong Yidong wrote:

> This appears to be due to a change in the internal format of freed
> blocks introduced between glibc-2.5.90-21 and glibc-2.5.90-22.  As a
> result, Emacs binaries built using older versions of glibc may crash
> when run using newer versions of glibc.

I agree that adding a PROBLEMS entry, and trying to come up with a
proper fix for 22.2 (not 22.1), is the best course of action at this
stage.

I think rms usually does not read web-based bug reports, so he
probably has not looked at the long bugzilla entry, and may have
missed the important information that you state above. Namely, that
the problem is not that Emacs can't be built on FC7, but rather that
if the glibc version is changed Emacs needs to be rebuilt with the
stated workaround. Whilst it would be good to fix properyl, I hope
this can be treated as a non-showstopper right now.

  reply	other threads:[~2007-05-21  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 13:42 22.0.99 emacs dumper (?) problem Chip Coldwell
2007-05-18 14:16 ` Neal Becker
2007-05-18 16:19   ` Chip Coldwell
2007-05-18 23:00     ` Neal Becker
2007-05-19 22:32 ` Richard Stallman
2007-05-21  3:26 ` Chong Yidong
2007-05-21  7:49   ` Glenn Morris [this message]
2007-05-21 13:24   ` Richard Stallman
2007-05-21 14:45     ` Chip Coldwell
2007-05-21 14:47   ` Chip Coldwell
2007-05-21 15:27     ` Chong Yidong
2007-05-21 15:28       ` Chip Coldwell
2007-05-22 14:51       ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bhy7ji39cf.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=coldwell@redhat.com \
    --cc=cyd@MIT.EDU \
    --cc=emacs-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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.