Closed
Bug 271562
Opened 20 years ago
Closed 19 years ago
Firefox 1.0 fails to build on SuSE SLES 8 running on IBM zSeries (s390x)
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: Dirk.Schwartzkopff, Assigned: bryner)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.0/source/firefox-1.0-source.tar.bz2 It fails while building a jar archive because somehow a contents.rdf is missing (see below). Reproducible: Always Steps to Reproduce: 1.configure 2.make Actual Results: /mnt/mozilla/netwerk/resources> make /usr/bin/gmake export gmake[1]: Wechsel in das Verzeichnis »/mnt/mozilla/netwerk/resources« gmake[1]: Für das Target »export« gibt es nichts zu tun. gmake[1]: Verlassen des Verzeichnisses »/mnt/mozilla/netwerk/resources« /usr/bin/gmake libs gmake[1]: Wechsel in das Verzeichnis »/mnt/mozilla/netwerk/resources« +++ making chrome /mnt/mozilla/netwerk/resources => ../../dist/bin/chrome/comm.jar +++ updating chrome ../../dist/bin/chrome/installed-chrome.txt +++ content,install,url,jar:resource:/chrome/comm.jar!/content/necko/ +++ overriding content/necko/contents.rdf updating: content/necko/contents.rdf (stored 0%) +++ making chrome /mnt/mozilla/netwerk/resources => ../../dist/bin/chrome/en-US.jar error: file '../../toolkit/locales/en-US/chrome/necko/contents.rdf' doesn't exist at ../../config/make-jars.pl line 418. gmake[1]: *** [libs] Fehler 2 gmake[1]: Verlassen des Verzeichnisses »/mnt/mozilla/netwerk/resources« make: *** [all] Fehler 2 Expected Results: dist/bin/chrome/comm.jar contains content/necko/contents.rdf , but there is no ../../toolkit/locales/en-US/chrome/necko/contents.rdf file as expected by make-jars.pl. Looks like that firefox 0.10 an PC Linux has the same problem. See Bug 266270
Updated•20 years ago
|
Assignee: firefox → bryner
Component: General → Build Config
QA Contact: firefox.general → asa
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•6 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•