Closed Bug 6829 Opened 26 years ago Closed 25 years ago

.//run-mozilla.sh: ./apprunner: No such file or directory

Categories

(SeaMonkey :: Build Config, enhancement, P3)

All
Linux
enhancement

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: martin, Assigned: granrosebugs)

Details

Attachments

(2 files)

Trying to install build M5 on GNU/Linux running on a 586 - following the M5 Release Notes at http://www.mozilla.org/projects/seamonkey/release-notes/m5.html The following is the log: martin@localhost:/home/martin > mkdir mozilla martin@localhost:/home/martin > mv mozilla*.tar.gz mozilla martin@localhost:/home/martin > cd mozilla martin@localhost:/home/martin/mozilla > gzip -dc mozilla-i686-pc-linux-gnu-M5.tar.gz | tar -xvf - <SNIPPED tar details> martin@localhost:/home/martin/mozilla > mv mozilla*.tar.gz ../ martin@localhost:/home/martin/mozilla > cd package martin@localhost:/home/martin/mozilla/package > ./mozilla-apprunner.sh MOZILLA_FIVE_HOME=/home/martin/mozilla/package LD_LIBRARY_PATH=/home/martin/mozilla/package:/opt/kde/lib:/usr/local/rvplayer5.0 MOZ_PROGRAM=./apprunner moz_debug=0 moz_debugger= .//run-mozilla.sh: ./apprunner: No such file or directory martin@localhost:/home/martin/mozilla/package > ls PrimitiveTest libmimetype.so libremoturl.so SimpleTypeLib libmork.so libsecfree.so apprunner libmozdbm.so libsockstuburl.so bsdecho libmozjs.so libstubsj.so chrome libmozutil.so libwidgetgtk.so components libmsgbaseutil.so libxmltok.so flash-registry.rdf libnetcache.so libxp.so libabouturl.so libnetcnvts.so libxpcom.so libappcores.so libnetlib.so libxpt.so libcaps.so libnetwork.so libxptcall.so libeditguimgr.so libnsappshell.so libxptcmd.so libemitterutil.so libnspr3.so libxptinfo.so libexpat.so libplc3.so localstore.rdf libfdm.so libplds3.so mozilla-apprunner.sh libfileurl.so libpref.so mozilla-viewer.sh libftpurl.so libprstrms3.so nsinstall libgfxgtk.so libpwcac.so regExport libgfxps.so libraptorbase.so res libgmbasegtk.so libraptorgfx.so run-mozilla.sh libgophurl.so libraptorhtml.so viewer libhttpurl.so libraptorhtmlpars.so vreg libimg.so libraptorplugin.so xpidl libjar50.so libraptorview.so xpt_dump libjsdom.so libraptorwebwidget.so xpt_link libjsurl.so libreg.so The mozilla-apprunner.sh script is failing on the last line: $dist_bin/run-mozilla.sh $script_args ./apprunner ${1+"$@"} There appears to be some faulty assumptions being made in the code: dist_bin="" # Running from dist/bin if [ -d components -a -d res ] then dist_bin="./" I'm not running this under dist/bin, and even if I were, there isn't a script called run-mozilla.sh available anywhere in the M5 download. I'm obviously missing something - but I don't know what it is, I don't know how to get it, and the download and release notes web pages on www.mozilla.org make no mention of anything else being required to run M5. I've managed to successfully install M5 on Windows.
This was fixed about a week (or two?) ago. M6 will do the right thing. As will a current build you do yourself, of course.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Downloaded the latest build of M6: mozilla-i686-pc-linux-gnu.tar.gz 6386 Kb Wed May 19 this time instead of creating a package directory a bin directiry is created - BUT it still fails: martin@localhost:/home/martin > mkdir mozilla martin@localhost:/home/martin > mv mozilla*.tar.gz mozilla martin@localhost:/home/martin > cd mozilla martin@localhost:/home/martin/mozilla > gzip -dc mozilla-i686-pc-linux-gnu.tar.gz | tar -xvf - martin@localhost:/home/martin/mozilla > mv mozilla*.tar.gz ../ martin@localhost:/home/martin/mozilla > l total 5 drwxr-xr-x 3 martin users 1024 May 25 21:58 ./ drwxr-xr-x 16 martin users 2048 May 25 21:58 ../ drwxr-xr-x 5 martin users 2048 May 18 17:11 bin/ martin@localhost:/home/martin/mozilla > cd bin martin@localhost:/home/martin/mozilla/bin > ./mozilla-apprunner.sh MOZILLA_FIVE_HOME=/home/martin/mozilla/bin LD_LIBRARY_PATH=/home/martin/mozilla/bin:/opt/kde/lib:/usr/local/rvplayer5.0 MOZ_PROGRAM=./apprunner moz_debug=0 moz_debugger= .//run-mozilla.sh: ./apprunner: No such file or directory martin@localhost:/home/martin/mozilla/bin >
Assignee: briano → donm
Status: REOPENED → NEW
M6 does not fix this bug - Martin
Resolution: FIXED → ---
Clearing Fixed resolution. Please set the milestone.
Assignee: donm → briano
Target Milestone: M8
reassigning to briano since donm doesn't work here anymore. martin, please download m7 when it becomes available and see if you still have this problem.
Status: NEW → ASSIGNED
I just checked in a version of run-mozilla.sh that should not die with the error reported in the Summary. This seems to happen only for some new shell versions (maybe bash only?), but I have no way to test it (i.e., it works for me on several different platforms).
Attached file shell script fix 1/2 (deleted) —
Attached file shell script fix 2/2 (deleted) —
------- Additional Comments From bingalls@panix.com 25.6.1999 --------- There's no way the shell scripts for the M7 binary distrib should work! I attached some patched up shell scripts. It took me longer to navigate bugzilla with a crashing mozilla 7 browser, that it did to fix. Hopefully, you will learn from my changes how to simplify your scripts. If you can run mozilla 7 from another directory (before my fix), then remove Makefile, and check your environment vars. What platforms are you testing on? This is a Linux problem. Frankly, the shell should not make a difference, but I am running zsh, which is free on all Unix variants and MS win32. You should not be shipping a shellscript launcher for binaries that looks for Makefiles. I am leaving this bug assigned, until the script is cleaned, or split up into a development version.
I know the scripts work *somewhere* because they work for me (without the makefiles it checks for) The script is meant to work for 1.) developers and 2.) endusers, in that order. I don't anticipate that we're going to spend a ton of time putting in the build machinery to deliver two different runscripts depending on the type of build (development or release).
Target Milestone: M8 → M9
pushing to M9. not going to hold M8 for this.
Whiteboard: BETA BLOCKER
Target Milestone: M9 → M11
setting target to M11. Not critical for the development releases. However, at beta time we are going to want a script that works in as many places as possible.
Severity: normal → enhancement
It works for me, either in or out of my build tree. But I agree it will need to be enhanced for other platforms when we actually have consistent builds on other platforms....
mass reassigning briano's open bugs to me while he's on sabbatical.
accept bug.
not going to make M11.
run-mozilla.sh is now mozilla pointing to mozilla-bin. I don't see this problem. is this still an issue with the M11 or nightly linux builds? Will close worksforme if no response.
Hardware: PC → All
Target Milestone: M12 → M13
I have this, or similar problem when I use the shell script run-mozilla.sh. I get the following... + MOZ_DIST_BIN= + MOZ_PROGRAM= + moz_debug=0 + moz_debugger= + [ 0 -gt 0 ] + [ 0 -gt 0 ] + [ -z ] + moz_test_binary viewer + binary=viewer + [ -f viewer ] + return 0 + [ 0 -eq 1 ] + moz_test_binary apprunner + binary=apprunner + [ -f apprunner ] + return 0 + [ 0 -eq 1 ] + [ -f Makefile.in ] + [ -d components -a -d res ] ++ pwd + MOZ_DIST_BIN=/u/chofmann/seamonkey/netscape-19991123/package + [ -z /u/chofmann/seamonkey/netscape-19991123/package ] + [ ! -d /u/chofmann/seamonkey/netscape-19991123/package ] + [ ! -x ] + moz_bail Cannot execute . + message=Cannot execute . + echo + echo run-mozilla.sh: Cannot execute . run-mozilla.sh: Cannot execute . + echo + exit 1 -------------- The only way for me to start the build is to run the binary directly. Stop by and see my system or run on intrepid:/u/chofmann/seamonkey/netscape-19991123/package ... or more recent builds. not a dogfood blocker moving to m13. getting good talkback data for linux and solaris and getting those goodies in the c-build are higher pri...
Target Milestone: M13 → M14
mass migration to M14
pushed to M16. removed "BETA BLOCKER" from status whiteboard.
Whiteboard: BETA BLOCKER
Target Milestone: M14 → M16
upon closer inspection, not only can I not get this error to occur, the mozilla script has changed so much the supplied attachments are not much help. resolving worksforme. if anyone runs into this problem in the future, do not reopen this bug, file a new one.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago25 years ago
Resolution: --- → WORKSFORME
Verified Redhat 6.1 2000092808
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: