SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Thu, 11 Apr 2002 16:54:45 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	Michael Iwaki <iwaki@gte.net > , SCOUG Help <scoug-help@scoug.com >
Subject:	SCOUG-Help: Re: Watcom installation & conflict with VisualAge C++ 3.0

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Michael,

I am forwarding your letter to the SCOUG help desk for more experienced
help than mine. Todate I only use the Watcom compiler. However, it does
appear as though you have a conflict with the VisualAge 3.0
environmental variables. My suggestion is use a runtime batch file to
reset the INCLUDE and LIB variables to the values you need for Watcom,
only. Use the batch file, just before using the Watcom products. Then,
at the end of your Watcom session, use another batch file to reset the
INCLUDE and LIB variables to the values used in your CONFIG.SYS. That
probably will work.

I don't use the commandline (any more) to link and compile. Instead, I
use the Watcom Integrated Development Environment (IDE). I suggest you
try that. It's much easier than trying to remember all the necessary
commandline arguments.

HCMotinn
______________________________________________________________________________

Michael Iwaki wrote:
>
> Hello Harry,
>
> I installed Watcom with the environment variables in my Config.sys as
> you stated in your presentation. I ran the hello.c program using :
>
> wcl386 hello.c
>
> from the command line. It came back with a Watcom trademark stuff and a
> hello.err file containing :
>
> G:\IBMCPP\INCLUDE\stdio.h(169): Error! E1127: Type required in parameter
> list
>
> (It repeated the same line two more times with 170 & 171 instead of 169)
>
> I have VisualAge 3.0 on my drive G in the IBMCPP folder. It also has an
> INCLUDE folder with many headers like the watcom INCLUDE folder. It
> seems to me that there is some kind of conflict of the INCLUDE
> environment variable. It might also be so for the LIB variable as well.
>
> I read somewhere that I have to use a separate CMD file to take care of
> this. Do you know how to do this?
>
> Thanks for any help.
>
> Michael Iwaki
>
> By the way, maybe it should be clarified how to compile a program. I
> use wcl386 from the command line, but I understand there are other
> things like
> "wcc386", "wpp386", "wcc", "wpp" for watcom's c compiler(wcc) and c++
> compiler(wpp). The 32-bit version has the 386 after it. I don't know
> what "wcl" means, I took it off another watcom document.

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 11 | April | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.