unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: 'Emacs Pretesters' <emacs-pretesters@gnu.org>,
	'Emacs Developers' <emacs-devel@gnu.org>
Subject: Re: Anyone built Emacs with gcc-3.3?
Date: Tue, 08 Jul 2003 23:30:49 +0100	[thread overview]
Message-ID: <rzqel10tzvq.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: FC3DA3DC8D4AD311AB910020352A8FDC10755463@eagle.midas-kapiti.com

"Marshall, Simon" <simon.marshall@misys.com> writes:

> I've tried to build emacs-21.3 and 21.1.90 with gcc-3.3 on solaris-2.8
> but without success.  Emacs builds but coredumps on exit, see bug #11386
> at GCC Bugzilla via http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11386.

That suggests it is dependent on data size.  I've seen similar
behaviour on Tru64 which was related to the use of mmap if I remember
correctly and never got resolved.  Also if I remember correctly, handa
had a similar problem on Solaris and resolved it on the basis of what
I said about the Tru64 problem, but I don't recall how.

For what it's worth, Emacs 21.3 appears to work on sparc64 with the
gcc pre-3.3.1 in Debian testing.

unexec problems are likely with a new gcc on ELF platforms.  To
investigate, I would run objdump or elfdump (?) on temacs versions
that work and don't work, looking for unexpected sections.  (You want
whatever option lists all the section headers.)  That might suggest
other things that need to be copied, for instance.  [In case that
turns out to be the case, let me say again that undumping should be
dumped.]

At one time, building Emacs was part of the regression testing for
gcc.  If that's been dropped, it seems like a backward move.

  parent reply	other threads:[~2003-07-08 22:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04  8:33 Anyone built Emacs with gcc-3.3? Marshall, Simon
2003-07-04  8:41 ` Dhruva Krishnamurthy
2003-07-04 16:17 ` puneet
2003-07-08 22:41   ` Dave Love
2003-07-09 12:31     ` Puneet Goel
2003-07-15 22:31       ` Dave Love
2003-07-05 22:25 ` Richard Stallman
2003-07-11  9:55   ` Paul Eggert
2003-07-11 22:52     ` Paul Eggert
2003-07-13 14:56       ` Simon Leinen
2003-07-14  5:52         ` Paul Eggert
2003-07-12  5:32     ` Richard Stallman
2003-07-08 22:30 ` Dave Love [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-04 12:36 Nelson H. F. Beebe
2003-07-07  8:26 Marshall, Simon
2003-07-08 14:28 ` Richard Stallman
2003-07-08 14:39   ` Jason Rumney
2003-07-09  5:34     ` Dhruva Krishnamurthy
2003-07-09  7:36       ` Pascal Obry
2003-07-09  7:59       ` Jason Rumney
2003-07-08 15:18 Marshall, Simon
2003-07-09 15:49 ` Richard Stallman
2003-07-11  9:57 ` Paul Eggert
2003-07-14 11:19 Marshall, Simon
     [not found] ` <3F12B8E7.2C387FE7@yk.rim.or.jp>
2003-07-14 14:41   ` Eric Botcazou
2003-07-14 17:47 ` Paul Eggert
2003-07-14 19:40   ` Eric Botcazou

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/emacs/

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

  git send-email \
    --in-reply-to=rzqel10tzvq.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretesters@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 public inbox

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

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).