From xemacs-m  Sun Jan  5 19:25:39 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id TAA17938 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 19:25:38 -0600 (CST)
Received: (from steve@localhost)
          by altair.xemacs.org (8.8.4/8.8.4)
	  id RAA15452; Sun, 5 Jan 1997 17:35:50 -0800
Sender: steve@xemacs.org
To: xemacs-beta@xemacs.org
Subject: Re: All warnings from a full compile of 20.0-b34
References: <yviad8vjtz9x.fsf@atreides.mindspring.com>
X-Url: http://www.miranova.com/%7Esteve/
Mail-Copies-To: never
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: Sudish Joseph's message of 05 Jan 1997 19:36:58 -0500
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
Date: 05 Jan 1997 17:35:48 -0800
Message-ID: <m2afqntwjv.fsf@altair.xemacs.org>
Lines: 77
X-Mailer: Red Gnus v0.72/XEmacs 20.0

>>>>> "Sudish" == Sudish Joseph <sudish@mindspring.com> writes:

Sudish> This is with the configure options in my last message. 

Sudish> .../lib-src/etags.c: In function `etags_getcwd':
Sudish> .../lib-src/etags.c:4354: warning: comparison between pointer
Sudish> and integer

Now is as good a time as any to nail these down.

/* Does the same work as the system V getcwd, but does not need to
   guess the buffer size in advance. */
char *
etags_getcwd ()
{
#ifdef HAVE_GETCWD
  int bufsize = 200;
  char *path = xnew (bufsize, char);

  while (getcwd (path, bufsize) == NULL)   <======================
    {
      if (errno != ERANGE)
	pfatal ("getcwd");
      bufsize *= 2;
      path = xnew (bufsize, char);
    }

Needs a system function prototype.  Would an ansi C wizard
(Mr. Preprocessor?) please suggest a proper sequence?

Sudish> .../lib-src/etags.c: In function `etags_getcwd':
Sudish> .../lib-src/etags.c:4354: warning: comparison between pointer
Sudish> and integer

Same as above.

Sudish> .../src/sysdep.c: In function `sys_execvp':
Sudish> .../src/sysdep.c:3248: warning: assignment of read-only location

This is in some wierd mule stuff, and it looks like it's a consequence of
using the `--const-is-losing=no' option.

Sudish> .../src/sysdep.c:3248: warning: assignment discards `const'
Sudish>         from pointer target type

Yup.

Sudish> Loading loadup.el...
Sudish> Loading auto-autoloads... (file auto-autoloads.el is newer) (68212)

:-(  So much to learn, so little time.

Peter Pezaris was asking about why a 19.16 might be needed.  19.15 in
all likelihood is going to be my first ever XEmacs release to the
world.  I am nowhere near egotistical enough to imagine I'm going to
get everything exactly right the first time.

This is a brain/distribution glitch, and in this case meaningless.
The gory details in case anyone cares:
After collecting all the beta34 source, I first did a `make all-elc'
and then a `make autoloads', to make sure everything was up to date.
After building the autoloads I did a cvs diff on the loaddefs.el and
auto-autolods.el files to see if there were any changes.  When there
weren't any I stopped there, neglecting to check whether the
auto-autoloads file had been touched.  Sorry about that.

The autoload generation should definitely not touch the autoloads file
if no changes were made, but I'm not going to worry too much, since
otherwise they work much better than before.  But it is things like
this which violate the principle of least surprise that make me loathe
to change things like `require-final-newline' which may change file
timestamps without notice.
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
"That Bill Clinton.  He probably doesn't know how to log on to the
Internet."  -- Rush Limbaugh, noted Computer Expert

