I tried to run the 4.0.2 SunOS version of verifyta on a Solaris server (sparc III with 24GB memory and 8 CPUS) but got the following message:
ld.so.1: verifyta: fatal: libm.so.2: open failed: No such file or directory
As I understand it, the libm.so.2 library is not where the executable thinks it is.
Which version of Solaris do you use? UPPAAL was compile on and for Solaris 10. I no longer have access to Solaris 9 machines and can therefore not produce a binary for Solaris 9.
Comparing version 4.0.1 and 4.0.2, I noticed that version 4.0.1 was linked against an older version of libm. I will see if there is anything I can do in 4.0.3 to resolve this problem. Still, I would like to know which version of Solaris you use.
The system characteristics are:
- Sun Fire 880 workstation
- System SunOS
- Version 5.9
- KernelID Generic_118558-24
So I guess this means Solaris 9.
The problem is that on Solaris 8 and Solaris 9 libm.so.1 (an older version of the libm library) is used, whereas applications build on Solaris 10 link with libm.so.2.
As a workaround, I suggest the following procedure:
ln -sf /lib/libm.so.1 libm.so.2
Then define the LD_LIBRARY_PATH environment variable to the path of the bin-SunOS directory. This can be done in the Uppaal startup script by adding the following line before the if-expression:
where the appropriate path is filled in.
I hope we can link to libm.so.1 in UPPAAL 4.0.3.
Fixed on the trunk as of rev. 2646. Still needs to be fixed on the 4.0 branch.
Fixed on the 4.0 branch from rev. 2682.