Commits

ben  committed d96db26

[xemacs-hg @ 2005-02-04 03:04:04 by ben]
Remove out-of-date doc files

* BUGS, README.packages: Delete, incorporate into FAQ.
README: Incorporate into FAQ. Delete everything but text
pointing to FAQ.

  • Participants
  • Parent commits 6bee993

Comments (0)

Files changed (5)

File BUGS

-If you think you may have found a bug in XEmacs, please
-read the Bugs section of the XEmacs manual for advice on
-(1) how to tell when to report a bug, and
-(2) how to write a useful bug report and what information
-it needs to have.
-
-There are three ways to read the Bugs section.
-
-(1) In a printed copy of the XEmacs manual.
-
-(2) With Info.  Start XEmacs, do C-h i to enter Info,
-then m XEmacs RET to get to the Emacs manual, then m Bugs RET
-to get to the section on bugs.  Or use standalone Info in
-a like manner.  (Standalone Info is part of the Texinfo distribution,
-not part of the XEmacs distribution.)
-
-(3) By hand.  Do
-    cat info/xemacs* | more "+/^File: xemacs.info,  Node: Bugs,"
-
-
-Part II of the XEmacs FAQ, available in a manner similar to the above,
-or via the world wide web, contains extensive information on how to
-track down and report bugs.
-
-	http://www.xemacs.org/faq/
+2005-02-03  Ben Wing  <ben@xemacs.org>
+
+	* BUGS, README.packages: Delete, incorporate into FAQ.
+	* README: Incorporate into FAQ.  Delete everything but text
+	pointing to FAQ.
+
 2005-02-03  Jerry James  <james@xemacs.org>
 
 	* configure.in: g++ 3.4.2 doesn't like -Wmissing-prototypes or
 This directory tree holds version 21.5 of XEmacs.
 
+The information in this file has been superseded by the XEmacs FAQ.
 
-*** What is XEmacs?
+The easiest way to read the FAQ is to go to
 
-XEmacs is a powerful, highly customizable open source text editor and
-application development system, with full GUI support.  It is protected
-under the GNU Public License and related to other versions of Emacs, in
-particular GNU Emacs.  Its emphasis is on modern graphical user
-interface support and an open software development model, similar to
-Linux.  XEmacs has an active development community numbering in the
-hundreds (and thousands of active beta testers on top of this), and runs
-on all versions of MS Windows, on Linux, and on nearly every other
-version of Unix in existence.  Support for XEmacs has been supplied by
-Sun Microsystems, University of Illinois, Lucid, ETL/Electrotechnical
-Laboratory, Amdahl Corporation, BeOpen, and others, as well as the
-unpaid time of a great number of individual developers.
+http://www.xemacs.org/Documentation/21.5/html/xemacs-faq_1.html
 
+You can also the local copy of the FAQ inside XEmacs by using
+use Help->XEmacs FAQ from the menu, or `C-h F'.
 
+If you don't have XEmacs running and can't access the web,
+look directly at `man/xemacs-faq.texi' or `info/xemacs-faq.info'.
 
-*** What platforms does it run on?
 
-  -- MS Windows (It has been tested on NT, 2000, 95, 98, and ME; you
-                 can also compile Cygwin and MinGW versions.)
-  -- Unix (It is regularly tested on Linux, Solaris, SunOS, HP/UX,
-           FreeBSD, OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5,
-           and probably others.  It should work on all versions of Unix
-           created in the last 10 years or so, perhaps with a bit of
-           work on more obscure platforms to correct bit-rot.  It uses
-           a sophisticated configuration system to auto-detect zillions
-           of features that are implemented differently in different
-           versions of Unix, so it will probably work on your vendor's
-           version, possibly with a bit of tweaking, even if we've
-           never heard of it.)
-  -- MacOS/X (As an X Windows application.  Unfortunately there is no
-              support currently for MacOS-specific features.)
-
-  There is also a port of XEmacs 19.14 (an older version, circa 1996)
-  for all versions of MacOS, with extensive support for MacOS-specific
-  features.  See the FAQ for more details.
-
-  There are rumors of an in-progress port to OS/2.  See the FAQ.
-
-  XEmacs will probably never work on MS/DOS or Windows 3.1, and we're
-  not particularly interested in patches for these platforms, as they
-  would introduce huge amounts of code clutter due to the woefully
-  underfeatured nature of these systems. (See GNU Emacs for a port to
-  MS/DOS.)
-
-
-
-*** Where's the FAQ?
-
-Look at `man/xemacs-faq.texi'.
-
-For the very latest version, see
-http://cvs.xemacs.org/cgi-bin/cvswebxe/xemacs/man/xemacs-faq.texi.
-
-
-
-*** Where's the latest version?
-
-For up-to-date information on XEmacs, see http://www.xemacs.org.
-
-To download XEmacs, see http://ftp.xemacs.org/ or
-ftp://ftp.xemacs.org/pub/xemacs/.
-
-For the latest experimental sources, see http://cvs.xemacs.org/, which
-gives instructions on how to get started with CVS access.
-
-There are numerous mailing lists for discussion of XEmacs.  The
-current description of these lists can be found at
-http://www.xemacs.org/Lists/, or see `etc/MAILINGLISTS'.  General
-discussion of bugs, new features, etc. takes place on
-xemacs-beta@xemacs.org.
-
-
-
-*** How do I build and install XEmacs?
-
-See the file `etc/NEWS' for information on new features and other
-user-visible changes since the last version of XEmacs.
-
-The file `INSTALL' in this directory says how to bring up XEmacs on
-Unix and Cygwin, once you have loaded the entire subtree of this
-directory.
-
-See the file `nt/README' for instructions on building XEmacs for
-Microsoft Windows.
-
-The file 'README.packages' will guide you in the installation of
-(essential) add on packages.
-
-
-
-*** How do I deal with bugs or with problems building, installing, or running?
-
-The file `PROBLEMS' contains information on many common problems that
-occur in building, installing and running XEmacs.
-
-Reports of bugs in XEmacs should be sent to xemacs-beta@xemacs.org.
-You can also post to the newsgroup comp.emacs.xemacs (or equivalentlt,
-send to the mailing list xemacs@xemacs.org), but it is less likely
-that the developers will see it in a timely fashion.  See the "Bugs"
-section of the XEmacs manual for more information on how to report
-bugs.  (The file `BUGS' in this directory explains how you can find
-and read that section using the Info files that come with XEmacs.)
-See `etc/MAILINGLISTS' for more information on mailing lists relating
-to XEmacs.
-
-
-*** How do I get started developing XEmacs?
-
-First, get yourself set up under CVS so that you can access the CVS
-repositories containing the XEmacs sources and the XEmacs packages.
-
-Next, set up your layout.  This is important, as a good layout will
-facilitate getting things done efficiently, while a bad layout will could
-lead to disaster, as you can't figure out which code is the most recent,
-which can be thrown away, etc.  We suggest the following layout: (feel free
-to make changes)
-
--- Everything goes under /src/xemacs (use a different directory if you
-   want).  From now, instead of saying /src/xemacs, we use <xsrc-top>, to
-   make it easier in case someone picked a different directory.
-
--- Package source is in <xsrc-top>/package-src.
-
--- Installed packages go under <xsrc-top>/xemacs-packages, and
-   <xsrc-top>/mule-packages.
-
--- A "workspace" is a complete copy of the sources, in which you do work of
-   a particular kind.  Workspaces can be differentiated by which branch of
-   the source tree they extend off of -- usually either the stable or
-   experimental, unless other branches have been created (for example, Ben
-   created a branch for his Mule work because (1) the project was long-term
-   and involved an enormous number of changes, (2) people wanted to be able
-   to look at what his work in progress, and (3) he wanted to be able to
-   check things in and in general use source-code control, since it was a
-   long-term project).  Workspaces are also differentiated in what their
-   purpose is -- general working workspace, workspace for particular
-   projects, workspace keeping the latest copy of the code in one of the
-   branches without mods, etc.
-
--- Various workspaces are subdirectories under <xsrc-top>, e.g.:
-
-   -- <xsrc-top>/working (the workspace you're actively working on,
-      periodically synched up with the latest trunk)
-
-   -- <xsrc-top>/stable (for making changes to the stable version of
-      XEmacs, which sits on a branch)
-
-   -- <xsrc-top>/unsigned-removal (a workspace for a specific, difficult
-      task that's going to affect lots of source and take a long time, and
-      so best done in its own workspace without the interference of other
-      work you're doing.  Also, you can commit just this one large change,
-      separate from all the other changes).
-
-   -- <xsrc-top>/latest (a copy of the latest sources on the trunk,
-      i.e. the experimental version of XEmacs, with no patches in it;
-      either update it periodically, by hand, or set up a cron job to do it
-      automatically).  Set it up so it can be built, and build it so you
-      have a working XEmacs. (Building it might also go into the cron job.)
-
-      This workspace serves a number of purposes:
-      -- 1. You always have a recent version of XEmacs you can compare
-            against when something you're working on breaks.  It's true
-            that you can do this with cvs diff, but when you need to do
-            some serious investigation, this method just fails.
-      -- 2. You (almost) always have a working, up-to-date executable that
-            can be used when your executable is crashing and you need to
-            keep developing it, or when you need an `xemacs' to build
-            packages, etc.
-      -- 3. When creating new workspaces, you can just copy the `latest'
-            workspace using GNU cp -a.  You have all the .elc's built,
-            everything else probably configured, any spare files in place
-            (e.g. some annoying xpm.dll under Windows, etc.).
-
-   -- <xsrc-top>/latest-stable/ (equivalent to <xsrc-top>/latest/, but
-      for the Stable branch of XEmacs, rather than the Experimental branch
-      of XEmacs).  This may or may not be necessary depending on how much
-      development you do of the stable branch.
-
--- <xsrc-top>/xemacsweb is a workspace for working on the XEmacs web site.
-
--- <xsrc-top>/in-patches for patches received from email and saved to files.
-
--- <xsrc-top>/out-patches for locally-generated patches to be sent to
-   xemacs-patches@xemacs.org.  Less useful now that the patcher util has been
-   developed.
-
--- <xsrc-top>/build, for build trees when compiling and testing XEmacs with
-   various configuration options turned off and on.  The scripts in
-   xemacs-builds/ben (see below) can be used to automate building XEmacs
-   workspaces with many different configuration options and automatically
-   filtering out the normal output so that you see only the abnormal
-   output.
-
--- <xsrc-top>/xemacs-builds, for the xemacs-builds module, which you need
-   to check out separately in CVS.  This contains scripts used for building
-   XEmacs, automating and simplifying using CVS, etc.  Under various
-   people's directories are their own build and other scripts.  The
-   currently most-maintained scripts are under ben/, where there are easily
-   configurable scripts that can be used to easily build any workspace
-   (esp. if you've more or less followed the layout presented above)
-   unattended, with one or more configuration states (there's a
-   pre-determined list of the most useful, but it's easy to change).  The
-   output is filtered and split up in various ways so that you can identify
-   which output came from where, and you can see the output either full or
-   with all "normal" output except occasional status messages filtered so
-   that you only see the abnormal ones.
-
-*** What's the basic layout of the code?
-
-The file `configure' is a shell script to acclimate XEmacs to the
-oddities of your processor and operating system.  It will create a
-file named `Makefile' (a script for the `make' program), which helps
-automate the process of building and installing emacs.  See INSTALL
-for more detailed information.
-
-The file `configure.in' is the input used by the autoconf program to
-construct the `configure' script.  Since XEmacs has configuration
-requirements that autoconf can't meet, `configure.in' uses an unholy
-marriage of custom-baked configuration code and autoconf macros; it
-may be wise to avoid rebuilding `configure' from `configure.in' when
-possible.
-
-The file `Makefile.in' is a template used by `configure' to create
-`Makefile'.
-
-There are several subdirectories:
-
-`src' holds the C code for XEmacs (the XEmacs Lisp interpreter and its
-    primitives, the redisplay code, and some basic editing functions).
-`lisp' holds the XEmacs Lisp code for XEmacs (most everything else).
-`lib-src' holds the source code for some utility programs for use by
-    or with XEmacs, like movemail and etags.
-`etc' holds miscellaneous architecture-independent data files
-    XEmacs uses, like the tutorial text and the Zippy the Pinhead quote
-    database.  The contents of the `lisp', `info' and `man'
-    subdirectories are architecture-independent too.
-`lwlib' holds the C code for the X toolkit objects used by XEmacs.
-`info' holds the Info documentation tree for XEmacs.
-`man' holds the source code for the XEmacs online documentation.
-`nt' holds files used compiling XEmacs under Microsoft Windows.

File README.packages

-                                                            -*- Outline -*-
-This file is in Outline mode.  It is best viewed under XEmacs.
-
-Press C-c C-o (Ctrl+c Ctrl+o) now to see a list of headings.
-  To expand a heading:  Put the cursor on the heading and press C-c C-s
-To collapse a heading:  Press C-c C-d
-
-For general XEmacs navigation tips: Press C-h t
-
-The XEmacs Packages Quick Start Guide
--------------------------------------
-
-This text is intended to help you get started installing a new XEmacs and
-its packages.  For more details see the 'Startup Paths' and 'Packages'
-sections of the XEmacs info manual.
-
-* Real Real Quickstart FAQ
---------------------------
-
-Q. Do I need to have the packages to compile XEmacs?
-
-A. Theoretically, no -- XEmacs will build and install just fine without any
-   packages installed.  However, only the most basic editing functions will
-   be available with no packages installed, so installing packages is an
-   essential part of making your installed XEmacs _useful_.
-
-Q. I really liked the old way that packages were bundled and do not
-   want to mess with packages at all.
-
-A. You can grab all the packages at once like you used to with old
-   XEmacs versions, skip to the 'Sumo Tarball' section below.
-
-Q. How do I tell XEmacs where to find the packages?
-
-A. Normally, you put the packages under $prefix/lib/xemacs, where
-   $prefix is specified using the `--prefix' parameter to `configure'.
-   (See `Package hierarchies' below).  However, if you have the packages
-   somewhere else (e.g. you're a developer and are compiling the packages
-   yourself, and want your own private copy of everything), use the
-   `--package-prefix' parameter to `configure' to specify the directory prefix
-   under which you have placed the `xemacs-packages' and (if MULE support
-   exists) `mule-packages' directories.
-
-Q. After installing, I want XEmacs to do `foo', but when I invoke it
-   (or click the toolbar button or select the menu item), nothing (or
-   an error) happens, and it used to work.
-
-A. See the first FAQ; you may be missing a package that is essential to
-   you.  You can either track it down and install it, or install the
-   `Sumo Tarball' (see the second FAQ).
-
-* A note of caution
--------------------
-
-The XEmacs package system is still in its infancy. Please expect a few
-minor hurdles on the way. Also neither the interface nor the structure is
-set in stone. The XEmacs maintainers reserve the right to sacrifice
-backwards compatibility as quirks are worked out over the coming
-releases.
-
-* Some package theory
----------------------
-
-In order to reduce the size and increase the maintainability of XEmacs,
-the majority of the Elisp packages that came with previous releases
-have been unbundled. They have been replaced by the package system.
-Each elisp add-on (or groups of them when they are small) now comes
-in its own tarball that contains a small search hierarchy.
-
-You select just the ones you need. Install them by untarring them into
-the right place. On startup XEmacs will find them, set up the load
-path correctly, install autoloads, etc, etc.
-
-* Package hierarchies
----------------------
-
-On Startup XEmacs looks for packages in so-called package hierarchies.
-Normally, there are three system wide hierarchies, like this:
-
-$prefix/lib/xemacs/xemacs-packages/
-     Normal packages go here.
-
-$prefix/lib/xemacs/mule-packages/
-     Mule packages go here and are only searched by MULE-enabled XEmacsen.
-
-$prefix/lib/xemacs/site-packages/
-     Local and 3rd party packages go here.
-
-This is what you get when you untar the SUMO tarballs under
-$prefix/lib/xemacs.
-
-$prefix is specified using the `--prefix' parameter to `configure', and
-defaults to `usr/local'.
-
-If your packages are located in the above directories, XEmacs will
-automatically find them at startup; however, if you have your packages
-somewhere else (e.g. you're a developer and are compiling the packages
-yourself, and want your own private copy of everything), you can tell
-XEmacs specifically where to look for the packages by using the
-`--package-prefix' parameter to 'configure' to specify the directory prefix
-under which you have placed the `xemacs-packages' and (if MULE support
-exists) `mule-packages' directories.
-
-See `configure.usage' for more info about the format of this parameter.
-
-* Where to get the packages
----------------------------
-
-Packages are available from ftp://ftp.xemacs.org/pub/xemacs/packages
-and its mirrors.
-
-* How to install the packages
------------------------------
-There are a few different ways to install packages:
-
-	1. Automatically, using the package tools from XEmacs.
-	2. Manually, using individual package tarballs.
-	3. Manually, all at once, using the 'Sumo Tarball'.
-
-** Automatically, using the package tools from XEmacs
------------------------------------------------------
-
-XEmacs comes with some tools to make the periodic updating and
-installing easier. It will notice if new packages or versions are
-available and will fetch them from the FTP site.
-
-Unfortunately this requires that a few packages are already in place.
-You will have to install them by hand as above or use a SUMO tarball.
-This requirement will hopefully go away in the future. The packages
-you need are:
-
-   efs          - To fetch the files from the FTP site or mirrors.
-   xemacs-base  - Needed by efs.
-
-and optionally:
-
-   mailcrypt    - For PGP verification of the package-index file.
-
-After installing these by hand, fire up XEmacs and follow these
-steps.
-
-  (1) Choose a download site.
-      - via menu: Tools -> Packages -> Set Download Site 
-      - via keyb: M-x customize-variable RET package-get-remote RET
-        (put in the details of remote host and directory)
-
-      If the package tarballs _AND_ the package-index file are in a
-      local directory, you can: M-x pui-set-local-package-get-directory RET
-
-  (2) Obtain a list of packages and display the list in a buffer named
-      "*Packages*".
-      - menu: Tools -> Packages -> List & Install
-      - keyb: M-x pui-list-packages RET
-
-      XEmacs will now connect to the remote site and download the
-      latest package-index file.
-
-      The resulting buffer, "*Packages*" has brief instructions at the
-      end of the buffer.
-
-  (3) Choose the packages you wish to install.
-      - mouse: Click button 2 on the package name.
-      -  keyb: RET on the package name
-
-  (4) Make sure you have everything you need.
-      - menu: Packages -> Add Required
-      - keyb: r
-
-      XEmacs will now search for packages that are required by the
-      ones that you have chosen to install and offer to select
-      those packages also.
-
-      For novices and gurus alike, this step can save your bacon.
-      It's easy to forget to install a critical package.
-
-  (5) Download and install the packages.
-      - menu: Packages -> Install/Remove Selected
-      - keyb: x
-
-** Manually, using individual package tarballs
-----------------------------------------------
-
-Fetch the packages from the FTP site, CD-ROM whatever. The filenames
-have the form name-<version>-pkg.tar.gz and are gzipped tar files. For
-a fresh install it is sufficient to untar the file at the top of the
-package hierarchy. 
-
-Note: If you are upgrading packages already installed, it's best to
-remove the old package first (see 'Upgrading/Removing Packages' below).
-
-For example if we are installing the 'xemacs-base'
-package (version 1.48):
-
-   mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
-   cd $prefix/lib/xemacs/xemacs-packages RET
-   gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
-
-Or if you have GNU tar, the last step can be:
-
-   tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
-
-For MULE related packages, it is best to untar into the mule-packages
-hierarchy, i.e. for the mule-base package, version 1.37:
-
-   mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
-   cd $prefix/lib/xemacs/mule-packages RET
-   gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
-
-Or if you have GNU tar, the last step can be:
-
-   tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
-
-
-** Manually, all at once, using the 'Sumo Tarball'
---------------------------------------------------
-
-Those with little time, cheap connections and plenty of disk space can
-install all the packages at once using the sumo tarballs.
-Download the file:
-
-   xemacs-sumo.tar.gz
-
-For an XEmacs compiled with Mule you also need:
-
-   xemacs-mule-sumo.tar.gz
-
-N.B. They are called 'Sumo Tarballs' for good reason. They are
-currently about 19MB and 4.5MB (gzipped) respectively.
-
-Install them by:
-
-   cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xvf - RET
-
-Or, if you have GNU tar:
-
-   cd $prefix/lib/xemacs ; tar zxvf /path/to/<tarballname> RET
-
-As the Sumo tarballs are not regenerated as often as the individual
-packages, it is recommended that you use the automatic package tools
-afterwards to pick up any recent updates.
-
-* After Installation
---------------------
-
-Updated packages can only be used by XEmacs after a restart.
-
-* Which Packages to install?
-----------------------------
-
-This is difficult to say. When in doubt install a package. If you
-administrate a big site it might be a good idea to just install
-everything. A good minimal set of packages for XEmacs-latin1 would be
-
-xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
-edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
-text-modes, time, mailcrypt
-
-If you are using the XEmacs package tools, don't forget to do:
-
-	Packages -> Add Required
-
-To make sure you have everything that the packages you have chosen to
-install need.
-
-See also '.../etc/PACKAGES' for further descriptions of the individual
-packages.
-
-* Upgrading/Removing Packages
------------------------------
-
-As the exact files and their locations contained in a package may
-change it is recommended to remove a package first before installing a
-new version. In order to facilitate removal each package contains an
-pgkinfo/MANIFEST.pkgname file which list all the files belong to the
-package. M-x package-admin-delete-binary-package RET can be used to
-remove a package using this file.
-
-Note that the interactive package tools included with XEmacs already do
-this for you.
-
-* User Package directories
---------------------------
-
-In addition to the system wide packages, each user can have his own
-packages installed under "~/.xemacs/". If you want to install packages
-there using the interactive tools, you need to set
-'package-get-install-to-user-init-directory' to 't'
-
-* Site lisp/Site start
-----------------------
-
-The site-packages hierarchy replaces the old 'site-lisp' directory.
-XEmacs no longer looks into a 'site-lisp' directly by default.
-A good place to put 'site-start.el' would be in
-$prefix/lib/xemacs/site-packages/lisp/
-
-* Finding the right packages
-----------------------------
-
-If you want to find out which package contains the functionality you
-are looking for, use M-x package-get-package-provider, and give it a
-symbol that is likely to be in that package.  
-
-For example, if some code you want to use has a (require 'thingatpt)
-in it:
-
-	M-x package-get-package-provider RET thingatpt RET
-
-which will return something like: (fsf-compat "1.08").
 #line 4854 "configure"
 #include "confdefs.h"
 #include <stdio.h>
-int main()
+main()
 {
   FILE *f=fopen("conftestval", "w");
-  if (!f) return(1);
+  if (!f) exit(1);
   fprintf(f, "%d\n", sizeof(short));
-  return(0);
+  exit(0);
 }
 EOF
 if { (eval echo configure:4865: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit $?) 2>&5
 #line 4896 "configure"
 #include "confdefs.h"
 #include <stdio.h>
-int main()
+main()
 {
   FILE *f=fopen("conftestval", "w");
-  if (!f) return(1);
+  if (!f) exit(1);
   fprintf(f, "%d\n", sizeof(int));
-  return(0);
+  exit(0);
 }
 EOF
 if { (eval echo configure:4907: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit $?) 2>&5
 #line 4932 "configure"
 #include "confdefs.h"
 #include <stdio.h>
-int main()
+main()
 {
   FILE *f=fopen("conftestval", "w");
-  if (!f) return(1);
+  if (!f) exit(1);
   fprintf(f, "%d\n", sizeof(long));
-  return(0);
+  exit(0);
 }
 EOF
 if { (eval echo configure:4943: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit $?) 2>&5
 #line 4968 "configure"
 #include "confdefs.h"
 #include <stdio.h>
-int main()
+main()
 {
   FILE *f=fopen("conftestval", "w");
-  if (!f) return(1);
+  if (!f) exit(1);
   fprintf(f, "%d\n", sizeof(long long));
-  return(0);
+  exit(0);
 }
 EOF
 if { (eval echo configure:4979: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit $?) 2>&5
 #line 5004 "configure"
 #include "confdefs.h"
 #include <stdio.h>
-int main()
+main()
 {
   FILE *f=fopen("conftestval", "w");
-  if (!f) return(1);
+  if (!f) exit(1);
   fprintf(f, "%d\n", sizeof(void *));
-  return(0);
+  exit(0);
 }
 EOF
 if { (eval echo configure:5015: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit $?) 2>&5
 #line 5040 "configure"
 #include "confdefs.h"
 #include <stdio.h>
-int main()
+main()
 {
   FILE *f=fopen("conftestval", "w");
-  if (!f) return(1);
+  if (!f) exit(1);
   fprintf(f, "%d\n", sizeof(double));
-  return(0);
+  exit(0);
 }
 EOF
 if { (eval echo configure:5051: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit $?) 2>&5