From xemacs-m  Fri Jun  6 22:56:52 1997
Received: from neptune.corp.comsat.com (neptune.corp.comsat.com [134.133.161.183])
	by xemacs.org (8.8.5/8.8.5) with SMTP id WAA21309
	for <xemacs-beta@xemacs.org>; Fri, 6 Jun 1997 22:56:50 -0500 (CDT)
Received: from neal by neptune.corp.comsat.com with local (Exim 1.58 #2)
	id 0waCcL-0001bl-00; Fri, 6 Jun 1997 23:56:41 -0400
From: <neal@ctd.comsat.com>
To: xemacs-beta@xemacs.org
Subject: 20.3b4 linux success (more or less)
X-Face: "$ryF/ne$oms9n}#TY|W5Ttjbp-6/u4j'7c:%-aq2IAf'&DjuvII4wvr:eU{h=GMPcVTP,p
 XgCPnk{Qu:7P=jH00Q?B(*bZ\7#x_&KD=%hU1VhP'`hy'PF01*tU9DAoK7QXTGzL%fe!lIj,0Ds,P:
 GV_YPd*4GO?ClJAPRa=iB\PuIQmM=Q>qo87lJh-N2PQL-2QaM>}LdWI<}
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Message-Id: <E0waCcL-0001bl-00@neptune.corp.comsat.com>
Date: Fri, 6 Jun 1997 23:56:41 -0400

1.  WARNING - I tried patching up using patch-2.3, which I had just
    built using the usual optimization settings.  It seems to just
    patch one file and then exit!  I reinstalled patch-2.1 (which
    won't build out of the box because it defines basename, which
    conflicts with libc), then the patch went fine.  It looks to me
    that patch-2.3 fails to meet the minimum requirements of a program 
    that calls itself "patch".

2.  

./configure  '--verbose' '--with-gnu-make' '--prefix=/usr' '--cflags=-g -O4 -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -pipe' '--error-checking=none' '--debug=no' '--with-sound=native' '--with-xpm'


Configured for `i586-pc-linux'.

  Where should the build process find the source code?    /usr/local/src/xemacs-20.3-b4
  What installation prefix should install use?		  /usr
  What operating system and machine description files should XEmacs use?
        `s/linux.h' and `m/intel386.h'
  What compiler should XEmacs be built with?              gcc -g -O4 -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -pipe
  Should XEmacs use the GNU version of malloc?            yes
  Should XEmacs use the relocating allocator for buffers? yes
  What window system should XEmacs use?                   x11
  Where do we find X Windows header files?                /usr/X11R6/include
  Where do we find X Windows libraries?                   /usr/X11R6/lib
  Compiling in support for XAUTH.
  Compiling in support for GIF image conversion.
  Compiling in support for XPM images.
  Compiling in support for X-Face message headers.
  Compiling in support for JPEG image conversion.
  Compiling in support for PNG image conversion.
  Compiling in native sound support.
  Compiling in support for Berkeley DB.
  Compiling in support for GNU DBM.
  Compiling in support for ncurses.
  Using the Lucid menubar.
  Using the Lucid scrollbar.
  Using the Motif dialog boxes.

3. Warnings:

In file included from /usr/local/src/xemacs-20.3-b4/lib-src/profile.c:39:
../src/config.h:37: warning: `alloca' redefined
/usr/include/alloca.h:40: warning: this is the location of the previous definition

/usr/local/src/xemacs-20.3-b4/lib-src/etags.c: In function `etags_getcwd':
/usr/local/src/xemacs-20.3-b4/lib-src/etags.c:4604: warning: comparison between pointer and integer

strftime.c: In function `emacs_strftime':
strftime.c:367: warning: passing arg 2 of `add_str' discards `const' from pointer target type

/usr/local/src/xemacs-20.3-b4/src/buffer.c:2839: the `getwd' function is dangerous and should not be used.

Why are we using getwd if getcwd is available?  We should prefer the
latter.

4.  Don't ever try to make beta on a machine hooked to the net via a
    slow, busy link (28.8 loaded with ftp).  Every time xemacs starts
    up, it tries to access the nameserver.  If it's not local this can 
    cause startup to take a very long time.  This happens over and
    over as the .elcs are compiled.

