X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs-
Message-ID: <19980916185419.50409@cerebro.laendle>
Date: Wed, 16 Sep 1998 18:54:19 +0200
From: Marc Lehmann <pcg AT goof DOT com>
To: beastium-list AT Desk DOT nl
Subject: Re: gcc flags, was: RPM
Mail-Followup-To: beastium-list AT Desk DOT nl
References: <m0zJGwT-0000FVC AT chkw386 DOT ch DOT pwr DOT wroc DOT pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <m0zJGwT-0000FVC@chkw386.ch.pwr.wroc.pl>; from Krzysztof Strasburger on Wed, Sep 16, 1998 at 12:44:00PM +0000
X-Operating-System: Linux version 2.1.120 (root AT cerebro) (gcc version pgcc-2.91.57 19980901 (egcs-1.1 release)) 
Status: RO
Content-Length: 981
Lines: 21

On Wed, Sep 16, 1998 at 12:44:00PM +0000, Krzysztof Strasburger wrote:
> >(I'm getting so fed up of this I'm thinking making gcc a Perl wrapper
> >which calls the proper gcc driver after removing any -m486's and replacing
> >them with -mamdk6 -march=amdk6 and putting in a couple more flags.)
> Writing these flags into the specs file is much easier...
> Krzysztof

Think multiuser ;) I prefer:

CFLAGS="whatever"; export CFLAGS

But I admit putting them into the specs file is foolproof (but more
difficult to do, as you have to remove -m486 etc..)

      -----==-                                              |
      ----==-- _                                            |
      ---==---(_)__  __ ____  __       Marc Lehmann       +--
      --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com       |e|
      -=====/_/_//_/\_,_/ /_/\_\                          --+
    The choice of a GNU generation                        |
                                                          |