zsh-users
 help / color / mirror / code / Atom feed
From: Vidiot <brown@ftms.COM>
To: zsh-users@math.gatech.edu (ZSH Mailing List)
Subject: INSTALL minor error
Date: Thu, 30 Jan 1997 16:11:13 -0600 (CST)	[thread overview]
Message-ID: <199701302211.QAA03992@ftms.ftms.com> (raw)

The INSTALL file contains the following:

    Compiler Options or Using a Different Compiler
    ----------------------------------------------
    By default, configure will use the "gcc" compiler if found.  You can use a
    different compiler, or add unusual options for compiling or linking that
    the "configure" script does not know about, by either editing the user
    configuration section of the top level Makefile (after running configure)
    or giving "configure" initial values for these variables by setting them
    in the environment.  Using a Bourne-compatible shell (such as sh,ksh,zsh),

    you can do that on the command line like this:
        CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

    Or on systems that have the "env" program, you can do it like this:
        env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure


The line that caught me is "or add unusual options for compiling" and the
example "CFLAGS=-O2."  The statement is incorrect, the option isn't added,
it REPLACES the option.  Because I have the Sun Ultra 140 computer, there
is a GCC CFLAG that is available (-mv8) to optimize code for the UltraSPARC.
If one does a "CFLAGS=-mv8" before running the configure, the default
CFLAGS for the GCC compiler are replaced with the -mv8 flag.

If this is really supposed to be a ADD, then the configure script is
broken.  If this is really a replace (as it currently works), then the
INSTALL instructions are in error.

Personally, I think the configure script should be changed to make it work
as an add.  The reason is that the user might not know what the default
CFLAGS are in order to place them on the line a well.  The current GCC
default CFLAGS is rather terse and quite forgettable.

To get around the problem, I just edited Makefile after configure was done.

Just thought that I would mention this.

MB
-- 
System Administrator - Finnigan FT/MS - Madison WI. <URL:http://www.ftms.com/>
e-mail: brown@ftms.com
phone: (608) 273-8262 ext: 612  fax: (608) 273-8719
Visit - <URL:http://www.cdsnet.net/vidiot/>  (Your link to Star Trek and UPN)


             reply	other threads:[~1997-01-30 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-30 22:11 Vidiot [this message]
1997-01-30 23:09 ` Zefram

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

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

  git send-email \
    --in-reply-to=199701302211.QAA03992@ftms.ftms.com \
    --to=brown@ftms.com \
    --cc=zsh-users@math.gatech.edu \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).