Jump to content

Uncle Slacky

  • Content count

  • Joined

  • Last visited

  • Days Won


Uncle Slacky last won the day on November 19 2012

Uncle Slacky had the most liked content!

Community Reputation

13 Good

About Uncle Slacky

  • Rank
  1. Moksha on Debian

    OK, thanks!
  2. Moksha on Debian

    I have now - I think it only needed libeet. Having said that, I seem to have successfully performed all the installation steps up to and including "sudo make install" with lots of warnings but (as far as I can tell) no serious errors, but there's no sign of Moksha installed anywhere (how do I check?). I've already got E17 installed - do I need to remove it before Moksha can be built and installed?
  3. Moksha on Debian

    I do now (i think). I've run autogen.sh successfully but I've just encountered the "usr/bin/eet" error mentioned earlier in the thread. Off to build the EFL, I guess (though I thought I'd already installed them from the Debian repos...).
  4. Moksha on Debian

    Hi - I'm trying to build Moksha on Antix 15 (Sid), and I get the following $ ./autogen.sh libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' configure.ac:57: error: possibly undefined macro: AC_DEFINE_UNQUOTED If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:63: error: possibly undefined macro: AC_SUBST configure.ac:102: error: possibly undefined macro: AC_MSG_ERROR configure.ac:238: error: possibly undefined macro: AC_MSG_RESULT configure.ac:383: error: possibly undefined macro: AC_MSG_NOTICE configure.ac:511: error: possibly undefined macro: AC_MSG_WARN autoreconf: /usr/bin/autoconf failed with exit status: 1 Any ideas about these "possibly undefined macros"? Edit: Fixed by installing "pkg-config" - apparently it's a common problem on 32-bit installs.
  5. Ecomorph

    If you hold down ALT and click anywhere on the window in question, you should then be able to drag it around the screen so that you can see the inaccessible parts. I've had to do this a lot, as I've only got a 7" screen... You can resize the options box a little, but I still can't see it all. I have to click one of the last options on the screen and guess how many times I have to hit tab before I highlight the 'apply' button and can close the window... Kinda annoying when you're toying with the options.
  6. Problem loading module: comp

    I had this as well the other day - I just figured Moksha was no longer going to include compositing, and that you'd need to install ecomorph instead if you still want it. Maybe Jeff could clarify?
  7. Installing Moksha on Bodhi

    Yep, that did the trick - don't know why I didn't think of it at the time!
  8. Installing Moksha on Bodhi

    Not a great success on my Asus eeePC 701 4G - booted to the Enlightenment "coloured boxes" screen, then a brief flash of my wallpaper followed by a black screen with a mouse pointer, with nothing to click on and no menus etc. Eventually managed to boot using the kernel "rescue mode" in Grub, but the desktop resolution was wrong. I was at least then able to reinstall Enlightenment and all seems well again. It might relate to the fact that the install was originally from one of the beta 32-bit E17 Legacy versions created during Jeff's absence, though.
  9. You could also try out OpenIndiana while you're waiting - it's a descendant of OpenSolaris & Illumos. I'm not sure how close it is to current Solaris but it might help to ease you into it. From the Distrowatch description:
  10. [RESURRECTED]My eeepc is dying

    Maybe they've changed a bit since the versions I installed! AntiX is sort-of negative, it was created by someone going by the name of "anticapitalista" and each version has a code name that reflects that attitude (the current one is "Luddite"). By enabling the extended usage of old PCs, I suppose that helps to undermine capitalism (or at least obsolesence & need to buy new hardware) in a way. It's essentially just Debian with a "Mepis" kernel and a choice of low-resource-usage desktops (jwm, icewm etc.).
  11. [RESURRECTED]My eeepc is dying

    If you're looking for other smallish-but-functional distros, there's also Slitaz, AntiX, and (at the upper end of the range) MX-14 and SolydX. I've run them all on a 701 4G eeePC or worse hardware.
  12. E17 vs E19 - Which are you using and why?

    I'm using E17, as E19 was just too sluggish on my eeePC 701 4G - I even switched to MX-14 with XFCE when it looked as if E19 was going to be all there was (around the time Jeff left). I came back when the legacy version was introduced. I really don't see any advantage to E19 over E17, at least not for my use cases (older and less powerful machines). The combination of E17 and a near bare-bones set of applications on installation make it really attractive proposition for those of us trying to keep older machines running and for converting former XP users.
  13. Bodhi 3 won't run on Eee PC

    Try installing the Legacy version of Bodhi 3.0 - you can always upgrade the kernel to something more modern afterwards, and E17 will be much faster on your EEE than E19 in any case - it certainly is on my 701 4G (running the latest 3.16 Ubuntu kernel, too).
  14. upgrade from legacy rc

    Thanks very much! I appreciate how busy you are, there's no hurry.
  15. upgrade from legacy rc

    All I know is that when I updated a few days ago, most E packages were updated and engage was removed as part of the upgrade. It's still in the repo (version 2014-10-20-0) and I get the following when I try to install it alone: $ sudo apt-get install engage Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: engage : Depends: ecore but it is not installable Depends: edje but it is not installable Depends: eet but it is not installable Depends: efreet but it is not installable Depends: eina but it is not installable Depends: evas but it is not installable E: Unable to correct problems, you have held broken packages.