No version of mozilla to date has run on my machine, a Cyrix 166+ running Slackware 3.6. I installed the requisite libraries and attempted to complile, but that didn't happen either. With M5, here is my result: amerige:~/tarballs/package$ run-mozilla.sh MOZILLA_FIVE_HOME=/home/lars/tarballs/package LD_LIBRARY_PATH=/home/lars/tarballs/package:/usr/local/rvplayer5.0 MOZ_PROGRAM=viewer moz_debug=0 moz_debugger= viewer: error in loading shared libraries /home/lars/tarballs/package/libraptorhtmlpars.so: undefined symbol: __vt_8iostream.3ios
It has been a long time since I ran Slackware (last version I used was 3.4), but I thought I might suggest something: Try a different distribution. I know there are things to be said for Slackware, but what makes quite a big difference between it and other Linux distributions is that, even with the latest 4.0 that is going to come out soon, it is **STILL** using libc5... Hard to believe it, but it still hasn't made the transition to glibc2/libc6. And as I understand it, Mozilla **requires** libc6. (Correct me if I'm wrong about that part.) If you still want to try getting it to run under Slackware, then I'm afraid you'll have to try switching it over to glibc2/libc6 yourself, which is **NOT** recommended, since building and installing something like a C library is a very delicate process, and can leave your entire system in an unusable state if something goes wrong. I've added a cc for myself, as this problem does interest me; I'd like to know if it gets solved, simply because I also remember my Slackware days. (I use Red Hat 6.0 now.)
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE
Wow!! Hold on guys.... Guys, this is the same bug as #5175. Check it out!!! There you get additional clues, too!! *** This bug has been marked as a duplicate of 5175 ***
Marking Verified as a dup
Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.
You need to log in before you can comment on or make changes to this bug.