Closed Bug 265978 Opened 21 years ago Closed 17 years ago

mozilla patches for building on IRIX

Categories

(SeaMonkey :: Build Config, defect)

Other
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: o.flebbe, Unassigned)

Details

Attachments

(3 files, 1 obsolete file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040915 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040915 There are some small of issues to compile mozilla on IRIX with gcc-3.3.x and up. Reproducible: Always Steps to Reproduce: 1. 2. 3.
The -mips2 is way too old for modern IRIX (thats o32)
Assignee: general → nobody
Component: Browser-General → Build Config
QA Contact: general → core.build-config
Olaf: looks like there are patches to three different modules here: directory, nspr, and security. Can you split this into three patches and attach each to this bug separately?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached patch nspr patchSplinter Review
Attached patch directory patchSplinter Review
Attached patch security patchSplinter Review
Attachment #163317 - Attachment is obsolete: true
(In reply to comment #3) > Olaf: looks like there are patches to three different modules here: directory, > nspr, and security. Can you split this into three patches and attach each to > this bug separately? Done.
So can you be a little more specific about how what versions of Irix this works with and doesn't? Presumably just switching mips2 to mips3 is going to break some older versions of Irix. Isn't the right thing to do actually to add configure.in tests here?
a configure test for, are you kidding? Let me explain it in more detail: I know of hundreds of IRIX machines all on IRIX 6.5 and only one IRIX 6.2 (6.3 and 6.4 were interim versions for specific machines) machine, which is kept alive only for historic reasons. IRIX 6.5 was introduced 6 years ago. I would assume that anyone has upgraded to this OS, since there is absolutly no support for anything else before that. It should work with any variant of IRIX 6.5 (and with the now unsupported IRIX 6.2, introduced 8 years ago), if you manage to get it on a stable Maintainance Level ;-) The point about -mips2: SGI (the manufactorer of IRIX) changed the ABI a lot. Somewhere at IRIX 6.x (8-9 years ago) they introduced the n32 ABI. Additionaly they had several Processor cababilities. The n32 ABI was the first to require -mips3. The o32 ABI is considered obsolete since 6.x but is still working, somehow. Somewhere in the past gcc only supported o32 (2.95.3 I think). The recent gcc 3.x compiler now are supporting the n32 ELF ABI (for years). IMHO nobody changed that because the gcc 3.x were not stable enough to compile mozilla on IRIX (I tried that some years ago). IMHO The -mips2 was only added on the command line to get the SGI "as" to produce -o32 objects needed for the old gcc's (and not -n32 the default). -mips2 was an alias to -o32. Asking to support o32 is asking to support machines which are a lot more older then 8 years. Considering the RAM and processor speed needed for mozilla I cannot beleave that anyone can work with mozilla on such an old machine, sorry. On a 3 year old high-end octane one can work with mozilla, but it is no fun. BTW: The SGI CC Compiler support in mozilla, works for -n32 -mips3 only, too. The bottom line: It works and is tested on IRIX 6.5. It has the some portability as the SGI CC code in mozilla. The change is neccesary to compile it with gcc 3.x. Unfortunatly mozilla-1.7.3 is not rock solid on IRIX (Both compiles: with IRIX CC and with gcc). It becomes unstable when working several hours with it. My Beta-Testers are not too happy with it. I have still to investigate it further.
Product: Browser → Seamonkey
IRIX is EOLed, so Is the Mozilla 1.7. Closing this bug as WONTFIX. If you have a new patch for the current SeaMonkey codebase please open a new bug. Thanks.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: