Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!wuarchive!bcm!dimacs.rutgers.edu!rutgers!cbmvax!bj
From: bj@cbmvax.commodore.com (Brian Jackson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help!  Scanf() problems in Manx 5.0D!
Keywords: scanf manx aztec bugs
Message-ID: <15334@cbmvax.commodore.com>
Date: 23 Oct 90 00:56:18 GMT
References: <7851@ucdavis.ucdavis.edu>
Reply-To: bj@cbmvax.commodore.com (Brian Jackson)
Organization: Commodore, West Chester, PA
Lines: 35

In article <7851@ucdavis.ucdavis.edu> zerkle@iris.ucdavis.edu (Dan Zerkle) writes:
>Using A3000 with 2.0 KS36.141 WB36.68
>Manx's Aztec C version 5.0d (the newest).
>
>I just installed Aztec C 5.0d and I am having MAJOR difficulties.
>
>1. Less serious problem:  I can't tell the compiler or linker where
>   the Aztec directories are.  When compiling, I have to throw in an
>   option like "-i a:Aztec/Include" for it to find the include files.
>   When linking, I have to type "-la:Aztec/Lib/m8" instead of just a
>   simple "-lm8".
>

Try the MSET command that comes with the new Manx. It uses the Amiga
ENV: variables.  My own Manx 5d startup script:


path wb2:manx5b/bin add
mset include=wb2:manx5_includes!wb2:manx5_includes/asm!wb2:headers
mset CLIB=wb2:manx5b/libs
mset CCTEMP=ram:

>2. Critical problem:  I STILL can't get scanf() to work properly.

Sorry, I never use scanf()    :)

>             Dan Zerkle  zerkle@iris.ucdavis.edu  (916) 754-0240

 -----------------------------------------------------------------------
 | Brian Jackson  Software Engineer, Commodore-Amiga Inc.  GEmie: B.J. |
 | bj@cbmvax.cbm.commodore.com    or  ...{uunet|rutgers}!cbmvax!bj     |
 |---------------------------------------------------------------------|
 | It requires a very unusual mind to undertake the analysis of        |
 | the obvious."                                                       |
 -----------------------------------------------------------------------