<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
just tried 124, I get problems here too, I used unzip -aa as mentioned<br><br>make vax<br>lib paths are: /lib/ /lib64/ /opt/kde3/lib/ /opt/kde3/lib64/ /usr/X11R6/lib/ /usr/X11R6/lib64/ /usr/lib/ /usr/lib/tls/ /usr/lib64/ /usr/lib64/graphviz/ /usr/lib64/graphviz/python/ /usr/lib64/smokegen/ /usr/lib64/tls/ /usr/lib64/wx-2.8-wxcontainer/<br>using libm: /usr/lib//libm.so<br>using librt: /usr/lib//librt.so<br>using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h<br>using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h<br>using libpcap: /usr/include/pcap.h<br>*** Simulator(s) being built with networking support using<br>*** Linux provided libpcap components<br>if test ! -e BIN; then mkdir BIN; fi<br>gcc -std=c99 -U__STRICT_ANSI__ -g -I . -D_GNU_SOURCE -DSIM_ASYNCH_IO -DUSE_READER_THREAD -DHAVE_DLOPEN=so sim_BuildROMs.c -o BIN/BuildROMs<br>BIN/BuildROMs<br>Error: ROM file 'VAX/ka655x.bin' has an unexpected size: 130550 vs 131072<br>This can happen if the file was transferred or unpacked incorrectly<br>and in the process tried to convert line endings rather than passing<br>the file's contents unmodified<br>Error: ROM file 'VAX/vmb.exe' has an unexpected size: 44452 vs 44544<br>This can happen if the file was transferred or unpacked incorrectly<br>and in the process tried to convert line endings rather than passing<br>the file's contents unmodified<br>make: *** [BIN/BuildROMs] Error 1<br><br><br><br><div><div id="SkyDrivePlaceholder"></div>> From: Mark@infocomm.com<br>> To: mike@umbricht.org; simh@trailing-edge.com<br>> Date: Sun, 26 Feb 2012 13:17:25 -0800<br>> CC: Mark@infocomm.com<br>> Subject: Re: [Simh] trouble selecting VAX ethernet on CentOS<br>> <br>> Hi Mike,<br>> <br>> I just fixed something in the BuildROMs code. I've added checks to verify that the files have been unpacked correctly. Can you try again.<br>> <br>> If the make fails again it should issue an error message explaining why instead of the segfault. This error message will indicate that the ROM image files have been mangled. This is likely due to something trying to do line ending conversions which isn't appropriate for the binary ROM files.<br>> <br>> My explicit instructions to download the zip file and then to unpack it with 'unzip -aa zipfilename.zip' have worked correctly for me on many platforms.<br>> <br>> Please let me know if you get any further.<br>> <br>> Thanks.<br>> <br>> - Mark<br>> <br>> > -----Original Message-----<br>> > From: Michael L. Umbricht [mailto:mike@umbricht.org]<br>> > Sent: Sunday, February 26, 2012 12:45 PM<br>> > To: Mark Pizzolato - Info Comm; simh@trailing-edge.com<br>> > Subject: RE: [Simh] trouble selecting VAX ethernet on CentOS<br>> > <br>> > Ok. I gave it a try, but it segfaults during make.<br>> > <br>> > -mikeu<br>> > <br>> > <br>> > $ make vax<br>> > lib paths are: /lib64/ /usr/lib64/ /usr/lib64/atlas/ /usr/lib64/mysql/<br>> > /usr/lib64/qt-3.3/lib/ /usr/lib64/xulrunner-2/<br>> > using libm: /usr/lib64//libm.so<br>> > using librt: /usr/lib64//librt.so<br>> > using libpthread: /usr/lib64//libpthread.so /usr/include/pthread.h<br>> > using libdl: /usr/lib64//libdl.so /usr/include/dlfcn.h<br>> > using libpcap: /usr/include/pcap.h<br>> > *** Simulator(s) being built with networking support using<br>> > *** Linux provided libpcap components<br>> > gcc -std=c99 -U__STRICT_ANSI__ -g -I . -D_GNU_SOURCE -DSIM_ASYNCH_IO<br>> > -DUSE_READER_THREAD -DHAVE_DLOPEN=so sim_BuildROMs.c -o BIN/BuildROMs<br>> > BIN/BuildROMs<br>> > make: *** [BIN/BuildROMs] Segmentation fault (core dumped)<br>> > make: *** Deleting file `BIN/BuildROMs'<br>> > <br>> > <br>> > > -------- Original Message --------<br>> > > Subject: RE: [Simh] trouble selecting VAX ethernet on CentOS<br>> > > From: Mark Pizzolato - Info Comm <Mark@infocomm.com><br>> > > Date: Sun, February 26, 2012 1:22 pm<br>> > > To: "Michael L. Umbricht" <mike@umbricht.org>, "simh@trailing-<br>> > edge.com"<br>> > > <simh@trailing-edge.com><br>> > ><br>> > ><br>> > > On Sunday, February 26, 2012 at 10:04 AM, Michael L. Umbricht wrote:<br>> > > > I'm having a little trouble choosing the ethernet interface for a<br>> > VAX<br>> > > > in SimH. My Dell Precision M6400 laptop has the following<br>> > interfaces:<br>> > > ><br>> > > > 0 eth0 ; on-board gig ethernet<br>> > > > 1 wlan0 ; on-board wireless<br>> > > > 2 virbr0 ; used by Virtual Box<br>> > > > 3 eth1 ; PCMCIA card w/ 10b2 or 10bT connectors<br>> > > ><br>> > > > I'd really like to use the eth1 ThinWire interface to connect SimH<br>> > with<br>> > > > a hardware VAX, while using eth0 for my internet connection. When I<br>> > try<br>> > > > to connect to eth0 or eth1 I get a segmentation fault. If I try<br>> > just<br>> > > > "eth" it works fine and connects to eth0. I can't get it to attach<br>> > to<br>> > > > eth1, though. Choosing from the "at xq ?" menu also leads to a core<br>> > > > dump. Is there anything that I am missing here?<br>> > ><br>> > > Hi Mike,<br>> > ><br>> > > There have been significant changes to the networking layer in the<br>> > upcoming release.<br>> > > Solving your issue makes the most sense using the latest code base.<br>> > > Please download the latest sources to work out this issue:<br>> > ><br>> > > 1 - Download https://github.com/markpizz/simh/zipball/master<br>> > Saving what that URL returns as a .zip file<br>> > > 2 - Unpack that zip file with the command: 'unzip -aa<br>> > zipfilename.zip'<br>> > > 3 - Build the vax simulator with: 'make vax'<br>> > ><br>> > > This will build a simulator with networking support and we can work<br>> > from there to troubleshoot your issue.<br>> > ><br>> > > Let me know if you still have issues.<br>> > ><br>> > > Good Luck.<br>> > ><br>> > > - Mark Pizzolato<br>> > <br>> > <br>> <br>> _______________________________________________<br>> Simh mailing list<br>> Simh@trailing-edge.com<br>> http://mailman.trailing-edge.com/mailman/listinfo/simh<br></div> </div></body>
</html>