Conference hydra::axp-developer

3311.0. "4seasons" by HYDRA::NEWMAN (Chuck Newman, 508/467-5499 (DTN 297), MRO1-3/F26) Wed Mar 12 1997 11:54

    Company Name :  4seasons
    Contact Name :  marcella
    Phone        :  
    Fax          :  
    Email        :  [email protected]
    Date/Time in :  12-MAR-1997 11:52:45
    Entered by   :  Chuck Newman
    SPE center   :  MRO

    Category     :  VMS
    OS Version   :  V6.2
    System H/W   :  VAX


    Brief Description of Problem:
    -----------------------------

The vendor writes:

Customer# 912024
DS# 3590947
PIN# 120970


> We have purchased a time ago the following products from DEC, 
> for VAX/Open VMS:
> 
>   QA-095SAA-H8 VAX Operating System
>   QA-YL48A-H8  VAX Liered products and doc.
>   QL-015AA-9B  PAK for DEC C  Open VMS VAX.
> 
> > Tamar,
> > I have problems with POSIX on VAX.
> > To remind you: we run OPENVMS 6.2 and POSIX 2.0 on the VAX station.
> > The release notes for POSIX 2.0 states that it is intended for VMS
> > version 6.1
> > The problem is the following: when I try to link programs under POSIX
> > it fails, the following is a sample compiler output:
> > 
> > noway.c:
> > # include <stdio.h>
> > main() {
> > printf(stderr, "No way Jose\n");
> > }
> > 
> > compiler [cc -W vaxc -o noway noway.c]:
> > 
> > %LINK-W-MULDEF, symbol decc$main multiply defined
> >         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
> > %LINK-W-MULDEF, symbol DECC$MAIN multiply defined
> >         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
> > %LINK-W-MULDEF, symbol decc$main_args multiply defined
> >         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
> > %LINK-W-MULDEF, symbol DECC$MAIN_ARGS multiply defined
> >         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
> > %LINK-W-MULDEF, symbol CC$_GFLOAT multiply defined
> >         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
> > %LINK-W-NUDFSYMS, 1 undefined symbol:
> > %LINK-I-UDFSYM,         _IOTABLE 
> > %LINK-W-USEUNDEF, undefined symbol _IOTABLE referenced
> >         in psect $CODE offset %X00000029
> >         in module NOWAY file _VAX$DKA200:[000000.RD]_1_1CB_NOWAY.OBJ;1
> > 
> > Running the result 'noway' (there were only warnings) resulted in a
'access
> > violation'. I would say OF COURSE, _IOTABLE was undefined !
> > 
> > All the executables we create in the master are done under DCL, I know
> > that.  But during the port there are a few executables we need under
> > POSIX.  Like rahs, config and gunzip.
> > 
> > The VMS was installed by our hardware supplier for the VAX  station.
> > The Posix was installed from the cd-set that came from the USA. Which
> > by the way is from March 1996
> 
> > What is the problem here? can you help us?

Marcello --

Our charter is to assist you in migrating your application to Alpha.  Your
question, however, doesn't appear to be a migration issue, and we don't have
the expertise to answer this question.

Here are some thoughts, though:

Posix V2.0 is supported on OpenVMS VAX V5.5-2 through V6.2, so your
configuration is supported.

It looks like you're using the VAXC compiler, but the link is
referencing the DECC RTL.  You might want to try installing the DECC
compiler and using that.

If you can't get this to work, you'll need to go through normal support
channels.

If you have further questions on this issue, please reference problem
number 1997-3311 and my name.

								-- Chuck Newman

> We have purchased a time ago the following products from DEC, 
> for VAX/Open VMS:
> 
>   QA-095SAA-H8 VAX Operating System
>   QA-YL48A-H8  VAX Liered products and doc.
>   QL-015AA-9B  PAK for DEC C  Open VMS VAX.
> 
and
> > compiler [cc -W vaxc -o noway noway.c]:

I assume they have DEC C. -W vaxc says, place the compiler in VAXC mode, it's a
posix synonym for /standard=vaxc.
> > 
> > %LINK-W-MULDEF, symbol decc$main multiply defined
> >         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1

Again, this shows they have DEC C. Multiply defined symbols indicate a link
problem with objects or shareable images multiple included. A linker map would
be helpful and also a -v on the compiler command line would give some insight.

Hope this helps,
Hartmut
    

The suggestions did not help. We bought the C compiler for VAX, and we
were told that with this PAK, we can use POSIX. Now, we have still
problems.

I'm sending the following response:
--------------------------------------------------------------------------------
Marcella --

I've been told that the "-W vaxc" says to put the compiler in "VAX C"
mode -- I had assumed it meant to use the VAX C compiler.

Please do the following:

1)  Generate a source code listing for noway.c.  From the DCL environment
	you would compile with "/list/machine."  I don't know how to
	specify this from POSIX.
2)  Generate a link map for noway.  From the DCL environment you would
	link with "/map/cross/full."  Again, I don't know how to specify
	this from POSIX.
3) MAIL noway.lis and noway.map to me, and reference problem
number 1997-3311 and my name.

Again, let me remind you that this appears to be out of our charter of
migration of applications to the Alpha platforms, and that the most
appropriate channel for you would be to go through normal support
channels.

								-- Chuck Newman