Citat Tovar <[EMAIL PROTECTED]>: > Alas, you still have to have just the right kernel and/or other > packages > installed to run the pre-compiled binaries under a (custom) Debian 2.4.1
I'd never expect any success in running pre-compiled binaries made for other distributions. Dependencies are usually not as strictly managed in RPM's and even when thy are they obviously depend on libraries, not the package names used in Debian. So even for newbees it is easier to compile from source than convert RPM's - especially if there's a source deb available with source dependencies. > As noted, alas, it even seems to care about 2.4.x kernels as well > somehow?? I came to the same conclusion after messing around with it a few days ago :-( My suspicion that only the network driver, sheep-net - required kernel version dependency turned out to be wrong. removing sheep-net build from the Makefile made it not require a kernel source (or kernel-headers package) available, but the resulting binary still refused to run when booting from another 2.4.x kernel. > Getting the most recent source to compile was non-trivial. I had to > install > several packages to do so (i think they were libelf-dev, libgd1g-dev and > > binutils-dev, and there might be more, since i'd already gotten enough > to > try to generate boot floppies). There were no hints to what packages > were > needed in BUILDING and the errors manifested mostly as missing > 'include' > files. A few things had to changed by hand, such as the location of > the > current kernel (or of XMON), to get it to compile > [mol-0.9.57/Rules.make > and also, respectively, added a -I to mol-0.9.57/debugger/mon/Makefile]. Strange - it was pretty trivial to me (and I don't consider myself that great a hacker). I had to add libelf-dev (guessing from a missing include file) but didn't touch the Makefiles at all (until a few days ago when I tried making it not depend on a specific kernel version). I use Debian unstable - which system do you have installed? > I didn't get finished trying to get the networking working, nor getting > audio out of it (other than the start-up sound). But i was surprised > and > delighted to have the three AppleShare icons from my i686 Debian box > appear Hmm - how did they appear if network didn't work properly? Ah - maybe you accessed through AppleShare, and TCP/IP didn't work? It seems that DHCP is not reliable when used from both Linux and Mac - try adding your IP manually in either system. > disappointed that 'startmol' from the i686 produced a screen on a > virtual > terminal rather than my non-local X screen, but hey, you can't have > every- > thing... It's amazing it works as well it does!! As I understand it, fullscreen means using framebuffer, not X. Try changing your molrc to make it run from a windows. Or try looking into VNC - I haven't played with it, but it seems there's a special VNC mode of MOL... > it seem like a tremendous program which should be VERY useful to me once > > i can address its reliability issues. Someone (sorry, forgot your name) is working on a deb this weekend. Even if it menas rebuilding with each installed kernel, a .deb is still making it a lot easier :-) Until then, I have .debs and source (without build-dependencies, unfortunately) here: http://debian.jones.dk/debian/local/auryn/pool/jones/mol/ - Jonas ------------------------------------------------- This mail sent through IMP: home.jones.dk
