On Thursday, June 28, 2012 at 2:28 PM, Gregg Levine wrote: > On Thu, Jun 28, 2012 at 5:19 PM, Mark Pizzolato - Info Comm > <[email protected]> wrote: > > On Thursday, June 28, 2012 at 2:00 PM, Gregg C Levine wrote: > >> Hello! > >> Since this release of Simh was based on good support from everyone I > >> decided to try it here. Naturally it decided to break during the > >> build of a simulator that I am currently not using. Here: > > [...] > >> gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after- > >> reload -fpredictive-commoning -fipa-cp-clone > >> -fno-unsafe-loop-optimizations -fno-strict-overflow -flto > >> -fwhole-program -Wno-unused-result -I . > >> -D_GNU_SOURCE -DUSE_READER_THREAD -DHAVE_DLOPEN=so > >> swtp6800/common/mp- a.c swtp6800/common/m6800.c > >> swtp6800/common/m6810.c swtp6800/common/bootrom.c > >> swtp6800/common/dc-4.c swtp6800/common/mp-s.c swtp6800/swtp6800/mp- > >> a_sys.c swtp6800/common/mp-b2.c swtp6800/common/mp-8m.c scp.c > >> sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c > sim_ether.c > >> sim_tape.c -I > >> swtp6800/swtp6800 -o BIN/swtp6800mp-a -lm -lrt -lpthread -ldl -lpcap > > >> - flto -fwhole-program > >> swtp6800/common/m6800.c:123:29: warning: type of 'sim_brk_dflt' does > >> not match original declaration > >> scp.c:379:8: note: previously declared here > >> swtp6800/common/m6800.c:123:43: warning: type of 'sim_brk_summ' does > >> not match original declaration > >> scp.c:377:8: note: previously declared here > >> swtp6800/common/m6800.c:123:14: warning: type of 'sim_brk_types' > does > >> not match original declaration > >> scp.c:378:8: note: previously declared here gcc -std=c99 > >> -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after- reload > >> -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations > >> -fno-strict-overflow -flto -fwhole-program -Wno-unused-result -I . > >> -D_GNU_SOURCE -DUSE_READER_THREAD -DHAVE_DLOPEN=so > >> swtp6800/common/mp- a2.c swtp6800/common/m6800.c > >> swtp6800/common/m6810.c swtp6800/common/bootrom.c > >> swtp6800/common/dc-4.c swtp6800/common/mp-s.c swtp6800/swtp6800/mp- > >> a2_sys.c swtp6800/common/mp-b2.c swtp6800/common/mp-8m.c > >> swtp6800/common/i2716.c scp.c sim_console.c sim_fio.c sim_timer.c > >> sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c -I swtp6800/swtp6800 -o > >> BIN/swtp6800mp-a2 -lm -lrt -lpthread -ldl -lpcap -flto > >> -fwhole-program > >> swtp6800/common/m6800.c:123:29: warning: type of 'sim_brk_dflt' does > >> not match original declaration > >> scp.c:379:8: note: previously declared here > >> swtp6800/common/m6800.c:123:43: warning: type of 'sim_brk_summ' does > >> not match original declaration > >> scp.c:377:8: note: previously declared here > >> swtp6800/common/m6800.c:123:14: warning: type of 'sim_brk_types' > does > >> not match original declaration > >> scp.c:378:8: note: previously declared here > >> root@rsl_spock:/usr/local/src/simhv39-0# > >> > >> Obviously that one breaking made it not possible to continue. I only > >> need the VAX and PDP11 ones, now. > > > > This is a known issue with the v3.9-0 release. > > > > Since you only are interested in the vax and pdp11, you can build > individual simulators: > > > > make vax > > make pdp11 > > > > Good Luck. > > > > - Mark Pizzolato > > > > Hello! > I should also mention that I need them but built with networking > support. Especially the vax one. But now that I see the comment from > Dennis Boone, (Thank you!), I see the ones I need.... Good catch.
With the current release, you don't need to do anything special to build with networking support. If your build environment has the required libpcap components installed, then a simple make will build a network capable binary. The first few lines of the build output will describe what capabilities and/or host features are available to enable functionality in the simulator(s) being built. In your case, you invoked make with USE_NETWORK=1. This will produce binaries which have static networking built in. These binaries will require that libpcap be available on the system you run it on, but they won't run at all if libpcap components aren't on the executing system. If you build without the USE_NETWORK=1, then the binaries produced will also produce useful networking if the running system has libpcap installed, and if it isn't installed, then the binaries will run, but networking won't be available. - Mark Pizzolato _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
