I have investigated further about me failing to get the vax 780 emulator to<br>work properly on Linux.<br><br>My main system runs CentOS 5.5. I have built the vax780 executable from the<br>simh 3.8-1 source code, simply by typing "make vax780".<br>
<br>I am consistently failing to get the 780 emulator to work with VMS 4.6, although<br>I did manage to install VMS 7.3 from the Compaq CD a few days ago. I have been<br>happily using the microVAX 3900 emulator with VMS 5.5-2 and 7.3 for months.<br>
<br>I have tried other versions of Linux and I have got the 780 emulator to run<br>VMS 4.6 on Fedora Core 14. Also, I have managed to run the version of the<br>emulator that I built on Fedora Core 14, on CentOS by copying the files to that<br>
system. I feel this is pointing towards some incompatibility with the version <br>of gcc that is on CentOS 5.5.<br><br>I have recorded what I beleve to be relevant information about the two systems<br>below.<br><br>---------------------------------------------------------<br>
Centos 5.5<br><br>Kernel version<br> 2.6.18-194.26.1.el5<br><br>gcc -v gives:<br><br>Using built-in specs.<br>Target: x86_64-redhat-linux<br>Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/u<br>
sr/share/info --enable-shared --enable-threads=posix --enable-checking=release -<br>-with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-<br>libgcj-multifile --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable<br>
-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-<br>1.4.2-gcj-1.4.2.0/jre --with-cpu=generic --host=x86_64-redhat-linux<br>Thread model: posix<br>gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)<br>
<br>glibc version<br> glibc-2.5-49.el5_5.7<br><br>ldd vax780 gives:<br> librt.so.1 => /lib64/librt.so.1 (0x0000003357200000)<br> libm.so.6 => /lib64/libm.so.6 (0x0000003356200000)<br> libc.so.6 => /lib64/libc.so.6 (0x0000003355e00000)<br>
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003356a00000)<br> /lib64/ld-linux-x86-64.so.2 (0x0000003355a00000)<br>---------------------------------------------------------<br>Fedora Core 14<br><br>Kernel version<br>
2.6.35.6-48.fc14.x86_6<br><br>gcc -v gives <br><br>Using built-in specs.<br>COLLECT_GCC=/usr/bin/gcc<br>COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.5.1/lto-wrapper<br>Target: x86_64-redhat-linux<br>Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/u<br>
sr/share/info --with-bugurl=<a href="http://bugzilla.redhat.com/bugzilla">http://bugzilla.redhat.com/bugzilla</a> --enable-bootstr<br>ap --enable-shared --enable-threads=posix --enable-checking=release --with-syste<br>m-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-<br>
object --enable-linker-build-id --enable-languages=c,c++,objc,obj-c++,java,fortr<br>an,ada,lto --enable-plugin --enable-java-awt=gtk --disable-dssi --with-java-home<br>=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java<br>
-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjav<br>a-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --bui<br>ld=x86_64-redhat-linux<br>Thread model: posix<br>gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC)<br>
<br>glibc version<br> glibc-2.12.90-19.i686<br><br>ldd vax780 gives:<br> linux-vdso.so.1 => (0x00007fff513ff000)<br> librt.so.1 => /lib64/librt.so.1 (0x0000003a7b000000)<br> libm.so.6 => /lib64/libm.so.6 (0x0000003a79c00000)<br>
libc.so.6 => /lib64/libc.so.6 (0x0000003a79800000)<br> libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003a7a000000)<br> /lib64/ld-linux-x86-64.so.2 (0x0000003a79000000)<br>---------------------------------------------------------<br>
<br>One further piece of information (not sure if it is relevant); even when the<br>emulated 780 boots, sometimes it hangs shortly after it boots, but booting with<br><br>>>> boot rq0/r5:1<br>and typing CONT in SYSBOOT gets it going<br>
<br>So, I am able to run the 780 emulator on Linux and get it to install VMS 4.6,<br>if only by the devious means of building it on one system and running it on<br>another. However, it feels awfully fragile.<br><br>I will give it a try with -O0<br>
<br>Peter Allan<br>