Closed
Bug 559699
Opened 15 years ago
Closed 12 years ago
Update 'Mac_OS_X_Build_Prerequisites' page for dropped MacOSX 10.4 support in mozilla-central
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: michael.graubart7, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.10pre) Gecko/20100412 SeaMonkey/2.0.5pre
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.10pre) Gecko/20100412 SeaMonkey/2.0.5pre
The latest seamonkey-2.1a1pre.en-US.mac cannot be started in my Mac G4 (PPC), OS X 10.4.11.
Reproducible: Always
Steps to Reproduce:
1. Download seamonkey-2.1a1pre.en-US.mac.dmg
2. Open it and drag SeaMonkey app. to the Applications folder.
3. Double-click on its icon.
Actual Results:
seamonkey-2.1a1pre.en-US.mac will not start up.
Expected Results:
seamonkey-2.1a1pre.en-US.mac shouldstyart up, since the Read Me file indicates that it should run in the above computer and system.
Mac G4, PPC, OS X 10.4.11.
Comment 1•15 years ago
|
||
I believe that OS X10.4 is dropped on the Gecko trunk
- http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/7d3a647586bab993?pli=1
Comment 2•15 years ago
|
||
I'm not sure what the current status actually is:
see also
https://developer.mozilla.org/en/Mac_OS_X_Build_Prerequisites
"Operating System: Mac OS X 10.4.11 or later."
How does FF 3.7 (or TB 3.2) behave on your computer?
Severity: critical → blocker
Version: unspecified → Trunk
Reporter | ||
Comment 3•15 years ago
|
||
If you can give me a link from which to download FF 3.7 or TB 3.2, I will try.
Comment 4•15 years ago
|
||
Firefox 3.7 will not work on a PPC 10.4.11. See the long thread in mozilla.dev.planning newsgroup for information about support for 10.4.
Comment 5•15 years ago
|
||
(In reply to comment #3)
I assume they should be available wherever you get SM 2.1.
If they're not, here is an example:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
(In reply to comment #4)
> Firefox 3.7 will not work on a PPC 10.4.11.
Thanks. Then I wouldn't expect SM 2.1 or TB 3.2 to work either.
> See the long thread in
> mozilla.dev.planning newsgroup for information about support for 10.4.
Hum, could
https://developer.mozilla.org/en/Mac_OS_X_Build_Prerequisites
be made more explicit about that?
(Or is it documented elsewhere?)
Is there any way/plan for the build to, for example, display an "unsupported OS" dialog?
Reporter | ||
Comment 6•15 years ago
|
||
I downloaded firefox-3.7a5pre.en-US.mac64.dmg. The app. called itself something other than Firefox (I can't any more remember what it did call itself), but at any rate it did not run on my G4 (PPC) with OS X 10.4.11.
Comment 7•15 years ago
|
||
Sorry, Tiger is not supported by Mozilla platform 1.9.3, which forms the base for SeaMonkey 2.1 - this is nothing the SeaMonkey team can change, so the bug is WONTFIX.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Component: General → Build Config
QA Contact: general → build-config
Resolution: --- → WONTFIX
Reporter | ||
Comment 8•15 years ago
|
||
OK, but then the Read Me that comes with SM 2.1 should not say that it will work in Tiger.
Comment 9•15 years ago
|
||
I fileed bug 559891 for the README.
Updated•15 years ago
|
Severity: blocker → major
Status: RESOLVED → UNCONFIRMED
Product: SeaMonkey → Core
QA Contact: build-config → build-config
Resolution: WONTFIX → ---
Summary: seamonkey-2.1a1pre.en-US.mac will not start in G4 PPC, OS X 10.4.11 → Update 'Mac_OS_X_Build_Prerequisites' page for dropped MacOSX 10.4 support in mozilla-central
Comment 10•12 years ago
|
||
https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Mac_OS_X_Prerequisites
now lists 10.5.8 or later under software requirements, and specifically calls out the requirement for Mozilla 1.9.3.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago → 12 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•