There is too little information here to even try to help you.

Mustangyhz,

  AMS is telling you that there are no connect modules. How are you
defining them?

                                                         Best Regards,

                                                            Sheldon

Mustangyhz -
This is the third separate place you have asked the very same question!!

I think SST2 is a specific output format; perhaps you can look at your settings and choose a different one (PSF?).

You said that you found /usr/ius/tools/lib/libdcapi.so is a symbolic link (->); you should check that the file it points to actually exists.

mustangyhz wrote on Nov 16^th, 2010, 5:27am:


Well, there's a possible problem: the 32bit libdcapi points to the 64bit one under simvision.  I would have expected
rwxrwxrwx  1 root root 34 Nov 16 19:35 ./libdcapi.so -> ../simvision/lib/libdcapi.so

Also, be sure to try
ls -l ../simvision/lib/libdcapi.so
ls -l ../simvision/lib/64bit/libdcapi.so

to see if the file the link points to is actually there!

Geoffrey_Coram
Thank you!
##########
http://fixunix.com/mandriva/123550-problem-libraries.html
[jim@jb ~]$ locate libc.so.6
/lib/libc.so.6
/lib64/libc.so.6
[jim@jb ~]$ ls -l /lib/libc.so.6 /lib64/libc.so.6
lrwxrwxrwx 1 root root 11 May 9 12:37 /lib64/libc.so.6 -> libc-2.4.so
lrwxrwxrwx 1 root root 11 May 9 12:37 /lib/libc.so.6 -> libc-2.4.so
[jim@jb ~]$ ls -l /lib64/libc-2.4.so /lib/libc-2.4.so
-rwxr-xr-x 1 root root 1288656 Mar 7 2007 /lib64/libc-2.4.so
-rwxr-xr-x 1 root root 1232576 Mar 7 2007 /lib/libc-2.4.so

Check to see if you have the two libc-2.4.so libraries, and
if the symbolic links are correct.

You may need to link existing libc-2.4.so files to the needed
pathnames, using ln -s /existing/path/file /new/path/file
############
some one has solved this kind of problem like above.
I don't have the /usr/ius/tools/simvision/lib/libdcapi.so

[root@mml lib]# ls -l ./64bit/libdcapi.so
lrwxrwxrwx  1 root root 37 Nov 16 19:33 ./64bit/libdcapi.so -> ../../simvision/lib/64bit/libdcapi.so
[root@mml lib]# ls -l ../../simvision/lib/64bit/libdcapi.so
ls: ../../simvision/lib/64bit/libdcapi.so: No such file or directory
[root@mml lib]# ls -l ../simvision/lib/libdcapi.so
ls: ../simvision/lib/libdcapi.so: No such file or directory
############
I DON'T know what to do, so I just
copy /usr/ius/tools/simvision/lib/64bit/libdcapi.so   to    /usr/ius/tools/simvision/lib/libdcapi.so
and delete ls -l ./64bit/libdcapi.so
then [root@mml lib]# ln -s ../simvision/lib/libdcapi.so ./libdcapi.so
############
However, I don't solve my problem. I know it is wrong to copy /usr/ius/tools/simvision/lib/64bit/libdcapi.so   to    /usr/ius/tools/simvision/lib/libdcapi.so.
but, what should I do without  /usr/ius/tools/simvision/lib/libdcapi.so？
how can I use "ln -s /existing/path/file /new/path/file" without "/existing/path/file"?

help!!!