We have upgraded from using VADSWorks 3.0.0 to using VADSWorks 3.1.
The script file we use to generate a ROMable image is now
producing multiple defines and one undefined reference 
(script file stops). Rational says in their 3.1 documentation that
either VxWorks 5.1.1 (what we have now) or VxWorks 5.2 will work.
I'm trying to avoid upgrading to VxWorks 5.2 for schedule reasons,
but I will if it fixes these problems. Any suggestions?

Paul McDonald
mcdonald@awcg.com

Example follows:

ld68k -o tmp.1 -X -r dataSegPad.o sysALib.o sysLib.o tyCoDrv.o if_ips.o if_cs220.o 
ncr5390Lib.o cs220_util.o  /opt/rom31/hello.o tj_utl_c.obj tj_utl_d.obj \
usrConfig_st.o version.o /lor/VADS040/vxworks/lib/libMC68040gnudrv.a  
/lor/VADS040/vxworks/lib/libMC68040gnuvx.a 

windALib.o(.data+4): multiple definition of `STACK_LIMIT (.data)'
v_i_mutex..NLPSa_strings..NLPS(.bss+128): first seen here
windlib..NLPB(.text+a0c): multiple definition of `INT_IMAGE (.text)'
more_memory..NLPBex_info..NLPB(.text+2c70): first seen here
...
windlib..NLPB(.bss+c): multiple definition of `_STOP (.bss)'
v_i_mutex..NLPSa_strings..NLPS(.bss+12c): first seen here

cp -p tmp.1 tmp.o
true tmp.o
VX_CPU_FAMILY=68k VX_HOST_TYPE=sun4 /lor/VADS040/vxworks/bin/sun4/makeSymTbl tmp.o >symTbl.c
sed -f editsymTbl symTbl.c > tmp.2
mv tmp.2 symTbl.c
chmod g+w symTbl.c
cc68k -c -O -fvolatile -fno-builtin -m68040 -m68040-only -Wall -I/h  -I./src/drv/   
-I. -I/lor/VADS040/vxworks/config/all/ -I/lor/VADS040/vxworks/h -I/lor/VADS040/vxworks/h/  
-I/lor/VADS040/vxworks/config/romtest  -I/lor/VADS040/vxworks/config/romtest/h  
-I/lor/VADS040/vxworks/src/config/  -I/lor/VADS040/vxworks/src/drv/  
-I/lor/VADS040/vxworks/config/romtest/src/drv/ -ansi -pedantic -pipe -nostdinc  
-DCPU=MC68040   -DVADSWORKS  symTbl.c

ld68k -o tmp.2 -X -N -M  -e _sysInit \
    -Ttext 00050000 tmp.1 symTbl.o
ts_term..NLPBwindlib..NLPB(.text+c142): undefined reference to `_pTaskLastFpTcb'