[HECnet] Sunlink DNA

Sent from Mail for Windows 10 From: Ray Jewhurst Sent: Friday, September 21, 2018 10:30 AM To: hecnet at update.uu.se Subject: Re: [HECnet] Sunlink DNA Still having problems.? It's not seeing any devices.? Here's what I get: ./MY-SUN2:8: tme/machine/sun2: No such file or directory ./MY-SUN2:9: mainbus0: No such file or directory ./MY-SUN2:10: mainbus0: No such file or directory ./MY-SUN2:11: mainbus0: No such file or directory ./MY-SUN2:12: obmem0: No such file or directory ./MY-SUN2:13: obmem0: No such file or directory ./MY-SUN2:14: obmem0: No such file or directory ./MY-SUN2:18: obio0: No such file or directory ./MY-SUN2:19: obio0: No such file or directory ./MY-SUN2:20: obio0: No such file or directory ./MY-SUN2:24: mainbus0: No such file or directory ./MY-SUN2:25: tme/generic/bus: No such file or directory ./MY-SUN2:26: mbmem0: No such file or directory ./MY-SUN2:30: mbmem0: No such file or directory ./MY-SUN2:31: sc0: No such file or directory ./MY-SUN2:63: obmem0: No such file or directory ./MY-SUN2:64: obmem0: No such file or directory ./MY-SUN2:65: zs1: No such file or directory ./MY-SUN2:66: zs1: No such file or directory ./MY-SUN2:67: tme/host/gtk/display: No such file or directory ./MY-SUN2:68: bwtwo0: No such file or directory ./MY-SUN2:69: kbd0: No such file or directory ./MY-SUN2:70: ms0: No such file or directory ./MY-SUN2:87: scsibus0: No such file or directory ./MY-SUN2:88: sd0: No such file or directory ./MY-SUN2:95: scsibus0: No such file or directory ./MY-SUN2:96: st0: No such file or directory tmesh> I copied everything into /usr/local so I don't get what's going wrong. Thanks Ray On Thu, Sep 20, 2018 at 8:57 PM, Mark Abene <phiber at phiber.com> wrote: Like I suspected, the autoconfig creates the ic/Makefile with the wrong install order. QUICK FIX: Before you 'make install', edit $HOME/tme/tme-0.8/ic/Makefile and change lines 371 and 372 so that SUBDIRS and DIST_SUBDIRS say "ieee754 m68k sparc stp22xx" (without the quotes), so that "ieee754" appears first, not second. Then a 'make install' should just work without errors. -Mark On Thu, Sep 20, 2018 at 5:33 PM, Mark Abene <phiber at phiber.com> wrote: Excellent! I'll probably go look in the main Makefile and correct the ieee754 library install to happen earlier on, to avoid this error. Have fun, Mark On Thu, Sep 20, 2018 at 5:26 PM, Ray Jewhurst <raywjewhurst at gmail.com> wrote: Mark, It worked like a charm.? Thanks.? Now the fun begins! Thanks again, Ray On Thu, Sep 20, 2018 at 8:19 PM, Mark Abene <phiber at phiber.com> wrote: Oddly enough, I did have that happen on one install but not another. Try this: cd $HOME/tme/tme-0.8/ic/ieee754 make install ...and if that works, try 'make install' again from the main tme-0.8 directory. I suspect some things in the install might be occurring out of order. -Mark On Thu, Sep 20, 2018 at 5:13 PM, Ray Jewhurst <raywjewhurst at gmail.com> wrote: Mark, I followed your instructions to a "T" and it built fine but I got the following errors on the install. /usr/bin/x86_64-linux-gnu-ld: cannot find -ltme-ieee754 collect2: error: ld returned 1 exit status libtool: install: error: relink `tme_ic_m68k.la' with the above command before installing it Makefile:312: recipe for target 'install-pkglibLTLIBRARIES' failed make[4]: *** [install-pkglibLTLIBRARIES] Error 1 make[4]: Leaving directory '/home/ray/tme-0.8/ic/m68k' Makefile:470: recipe for target 'install-am' failed make[3]: *** [install-am] Error 2 make[3]: Leaving directory '/home/ray/tme-0.8/ic/m68k' Makefile:464: recipe for target 'install' failed make[2]: *** [install] Error 2 make[2]: Leaving directory '/home/ray/tme-0.8/ic/m68k' Makefile:612: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/ray/tme-0.8/ic' Makefile:315: recipe for target 'install-recursive' failed make: *** [install-recursive] Error 1 I also am also running Ubuntu 18.04. Thanks in advance, Ray On Thu, Sep 20, 2018 at 5:02 PM, Mark Abene <phiber at phiber.com> wrote: I posted this message yesterday, but for some reason people are telling me it never went to the list. I removed the photos I originally attached and am sending it again. -Mark ---------- Forwarded message ---------- From: Mark Abene <phiber at phiber.com> Date: Wed, Sep 19, 2018 at 2:58 PM Subject: Re: [HECnet] Sunlink DNA To: hecnet at update.uu.se To everyone who asked, I built TME last night on Ubuntu 18.04 on two different systems, and installed NetBSD 1.6.2 on a sun3/160 instance. It's working very nicely, minus networking; bear in mind that TME was originally written to run on a NetBSD host (it's in the pkg collection), and makes use of BPF to implement networking (I seem to remember it also working on FreeBSD). Linux does have a bpf compatibility interface, so I'll see if it can be made to work and follow up with you all. That said, grab TME here:?https://people.csail.mit.edu/fredette/tme/tme-0.8.tar.gz That's the home site, there's lots of info on the emulator?https://people.csail.mit.edu/fredette/tme/ There's also this site, specifically about installing SunOS 4.1.1:?http://www.abiyo.net/retrocomputing/installingsunos411tosun3emulated… DON'T follow those build instructions, they're incredibly old and will get you nowhere fast.? :) Here are my steps: Make sure you have the gtk-2.0 and glib2.0 dev packages installed. Then... mkdir $HOME/tme cd $HOME/tme tar -zxvf your_download_dir/tme-0.8.tar.gz cd tme-0.8 vi libtme/module.c (comment out line 93 "LTDL_SET_PRELOADED_SYMBOLS();", it's no longer needed) and save. ./configure --prefix=$HOME/tme --disable-warnings 'LIBS=-lglib-2.0 -lgtk-x11-2.0 -lX11' export LTDL_LIBRARY_PATH=$HOME/tme/lib (or "setenv LTDL_LIBRARY_PATH $HOME/tme/lib" for csh/tcsh) make make install If everything built and installed without errors, you'll have the install tree in $HOME/tme. From here you can follow the various instructions on the original site above for installing NetBSD, etc. If you ran into any errors either building, installing, or running, just drop me a note, I'd be happy to help! P.S.: I've attached some photos of it booting up! P.P.S: You'll notice it seg fault when you exit tmesh. The original does this too. The author even comments about how there's no "quit" command. Regards, Mark On Tue, Sep 18, 2018 at 6:35 PM, Dave McGuire <mcguire at neurotica.com> wrote: ? Thanks Mark! ? ? ? ?-Dave On 09/18/2018 08:59 PM, Mark Abene wrote: -- Dave McGuire, AK4HZ New Kensington, PA