The default bug view has changed. See this FAQ.

[META] AMD64 (x86-64) 64-bit tracking

RESOLVED FIXED

Status

Core Graveyard
Tracking
RESOLVED FIXED
13 years ago
8 months ago

People

(Reporter: Oleg Sidletskiy, Assigned: chris hofmann)

Tracking

(Depends on: 2 bugs, {64bit, meta})

Trunk
x86_64
All
64bit, meta
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
This tracking bug should include bugs concerning any OS that runs on AMD
Opteron/Athlon 64 including Linux, Windows (64-bit *and* 32-bit), etc.

Updated

13 years ago
Depends on: 239499

Updated

13 years ago
Depends on: 239562

Updated

13 years ago
Depends on: 242926
(Assignee)

Updated

13 years ago
Depends on: 243233

Updated

13 years ago
Depends on: 244577

Comment 1

13 years ago
Should bug 236792 also be added to depends on list?
(Reporter)

Updated

13 years ago
Depends on: 236792, 249478

Updated

13 years ago
Depends on: 256169

Updated

13 years ago
Depends on: 260986

Updated

13 years ago
Depends on: 266812

Updated

12 years ago
Depends on: 275365
Depends on: 281879

Updated

12 years ago
Depends on: 281519

Updated

12 years ago
Depends on: 312003

Updated

11 years ago
Depends on: 327124

Updated

11 years ago
Depends on: 328547

Updated

11 years ago
Depends on: 338440

Updated

11 years ago
Depends on: 344439

Comment 2

11 years ago
Can someone please elaborate on the general status of mozilla on the x86-64 platform? That is, does it build and run normally or are the '64-bit-safe code' bugs prevent it from building?

Comment 3

11 years ago
(In reply to comment #2)
> Can someone please elaborate on the general status of mozilla on the x86-64
> platform? That is, does it build and run normally or are the '64-bit-safe code'
> bugs prevent it from building?

I built 1.5.0.5 last night on x64 using VS2005 and it seems to work though I'm going to do some more testing on it during the day. I have 2.0 on my list of things to try one of these days. I've been away from Mozilla stuff for several months though.

Comment 4

11 years ago
At least, you cannot compile current CVS tree for Firefox 1.5 / 2.0.
Although I don't discuss with Michael, I think I want to resolve x64 build issue until 3.0.

Updated

11 years ago
Depends on: 345866

Comment 5

11 years ago
I apply a whole bunch of patches on top of Makoto's patches to get 1.5.0.* x64 builds to work.

I did do a trunk build early in 2006 which worked but haven't tried a 2.0 build. I may give that a shot in the future.

Comment 6

11 years ago
(In reply to comment #5)
> I apply a whole bunch of patches on top of Makoto's patches to get 1.5.0.* x64
> builds to work.
> 
> I did do a trunk build early in 2006 which worked but haven't tried a 2.0
> build. I may give that a shot in the future.
> 

Was that a Firefox trunk, or Seamonkey? Maybe try Seamonkey as well?

Comment 7

11 years ago
(In reply to comment #6)
> (In reply to comment #5)
> > I apply a whole bunch of patches on top of Makoto's patches to get 1.5.0.* x64
> > builds to work.
> > 
> > I did do a trunk build early in 2006 which worked but haven't tried a 2.0
> > build. I may give that a shot in the future.
> > 
> 
> Was that a Firefox trunk, or Seamonkey? Maybe try Seamonkey as well?

It was a Firefox trunk and it was in conjunction with testing code for either
the hash or Javascript stuff that I have two bugs open on.

I really don't have time to do SeaMonkey and I'd guess that building SeaMonkey wouldn't be a trivial task. The x64 builds of Thunderbird uses up to 1.5 GB of memory to build and I would guess that SeaMonkey would require even more.

Updated

11 years ago
Depends on: 345695

Updated

9 years ago
Depends on: 440964
set platform to x86_64
Hardware: x86 → x86_64
Should we mark this as closed per bug #558448 creation ?
nvm, wrong copy/paste

Updated

5 years ago
Depends on: 691752

Comment 11

5 years ago
(In reply to Worcester12345 from comment #6)
> (In reply to comment #5)
> > I apply a whole bunch of patches on top of Makoto's patches to get 1.5.0.* x64
> > builds to work.
> > 
> > I did do a trunk build early in 2006 which worked but haven't tried a 2.0
> > build. I may give that a shot in the future.
> > 
> 
> Was that a Firefox trunk, or Seamonkey? Maybe try Seamonkey as well?

(In reply to Michael Moy from comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > I apply a whole bunch of patches on top of Makoto's patches to get 1.5.0.* x64
> > > builds to work.
> > > 
> > > I did do a trunk build early in 2006 which worked but haven't tried a 2.0
> > > build. I may give that a shot in the future.
> > > 
> > 
> > Was that a Firefox trunk, or Seamonkey? Maybe try Seamonkey as well?
> 
> It was a Firefox trunk and it was in conjunction with testing code for either
> the hash or Javascript stuff that I have two bugs open on.
> 
> I really don't have time to do SeaMonkey and I'd guess that building
> SeaMonkey wouldn't be a trivial task. The x64 builds of Thunderbird uses up
> to 1.5 GB of memory to build and I would guess that SeaMonkey would require
> even more.

I would LOVE to see MMOY pick this up again! This was some great work done many moons ago, and would only be better now! Thanks.
I think this bug has outlived its usefulness.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.