🚀 go-pugleaf

In article <C2CG3n.JBA@austin.ibm.com>, moller@austin.ibm.com (Chris Moller) writes:
> In article <1lfd75$kj1@agate.berkeley.edu>, faustus@ygdrasil.CS.Berkeley.EDU (Wayne A. Christopher) writes:
> Gcc 2.2.3 compiled fine on my rs/6000 (running a pre-release version of
> AIX 3.2), but then, so did gcc 2.2.2.  If you'll mail me some of the error
> messages, I'll see if anything occurs to me.
> 
  The latest version of gcc is 2.3.3, I would suggest you use that instead. In
any case, the problem seems to be the broken IBM assembler. To my knowledge, IBM
has not shipped the "fixed" assembler as part of AIX, you still have to request
it.

  From ./gcc-2.3.3/README.RS6000:

    In either case, to order, execute
        lslpp -h bos.obj to determine your release level.  (Look on the
    ACTIVE line for something like 03.01.0005.0012.) Then call IBM Support
    at 800-237-5511.  Ask for emergency shipment of the rs6000 AIX fix for
    APAR IX26107.  They may ask you to verify that it's a fix for "Don't
    allow .csect name[BS] or [UC]"; say yes.  They may also ask you for
    your customer number.  If you do not know it, you will still be able
    to getthe fix, but you will have to be persistent.

  This works for both AIX-3.1 and AIX-3.2.

    Cheers,

    Tom McConnell
-- 
 Tom McConnell          |     Internet: tmcconne@sedona.intel.com
 Intel, Corp. C3-91     |     Phone: (602)-554-8229
 5000 W. Chandler Blvd. | The opinions expressed are my own. No one in 
 Chandler, AZ  85226    | their right mind would claim them.