unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@twinsun.com>
Cc: emacs-pretesters@gnu.org, emacs-devel@gnu.org,
	ebotcazou@gcc.gnu.org, ishikawa@yk.rim.or.jp
Subject: Re: Anyone built Emacs with gcc-3.3?
Date: Mon, 14 Jul 2003 10:47:12 -0700 (PDT)	[thread overview]
Message-ID: <200307141747.h6EHlCu26117@green.twinsun.com> (raw)
In-Reply-To: <FC3DA3DC8D4AD311AB910020352A8FDC10755484@eagle.midas-kapiti.com> (simon.marshall@misys.com)

> From: "Marshall, Simon" <simon.marshall@misys.com>
> Date: Mon, 14 Jul 2003 12:19:12 +0100
> 
> alloc.c:398: warning: initialization makes pointer from integer without
> a cast

Yes, thanks: I fixed that by using the following instead in the
version that I checked into the Emacs trunk:

Lisp_Object *staticvec[NSTATICS] = {&Vpurify_flag};


> Date: Mon, 14 Jul 2003 23:06:31 +0900
> From: Ishikawa <ishikawa@yk.rim.or.jp>

> (Strangely, I didn't have to apply the patch Eric posted. I suspect
> that there may be a factor due to different version of Sun's ld. 

As I understand it, the bug does not always occur: it depends on the
layouts of the earlier segments.  So it's possible that Eric's patch
happened to fix the problem for his particular alignment, even though
it shouldn't fix the problem in general (and didn't work for me).

> I didn't notice the warning Simon caught because I was
> so ecstatic that "make" ended successfully.
> I should have scrolled up a little bit to see some warning messages.

Yes, that's what happened with me too.

  parent reply	other threads:[~2003-07-14 17:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 11:19 Anyone built Emacs with gcc-3.3? Marshall, Simon
     [not found] ` <3F12B8E7.2C387FE7@yk.rim.or.jp>
2003-07-14 14:41   ` Eric Botcazou
2003-07-14 17:47 ` Paul Eggert [this message]
2003-07-14 19:40   ` Eric Botcazou
  -- strict thread matches above, loose matches on Subject: below --
2003-07-08 15:18 Marshall, Simon
2003-07-09 15:49 ` Richard Stallman
2003-07-11  9:57 ` Paul Eggert
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-04 12:36 Nelson H. F. Beebe
2003-07-04  8:33 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

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=200307141747.h6EHlCu26117@green.twinsun.com \
    --to=eggert@twinsun.com \
    --cc=ebotcazou@gcc.gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretesters@gnu.org \
    --cc=ishikawa@yk.rim.or.jp \
    /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).