Closed Bug 285940 Opened 20 years ago Closed 20 years ago

gccsetup page for OS/2 needs update

Categories

(Developer Documentation Graveyard :: General, defect)

x86
OS/2
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mkaply)

References

()

Details

Attachments

(4 files)

Since that page was last updated several things happened: winico changed on Hobbes, GCC 3.2.2 CSD 1 was released, .mozconfig use was changed to select compile target. Also, 'SET PROGRAMS=' was never added to setmozenv.cmd which might cause problems for eCS users where this variable is set in Config.sys and causes some Makefile to not work correctly.
This adds the new stuff and changes the wrong links.
Do we want to also put up alternate instructions for GCC 3.3.5? Mostly it would be a link to GCC 3.3.5 and an updated setmozenv. I have been using 3.3.5 since it started building and they seem to be stable builds. The only reason I use 3.2.2 now is either to make sure it isn't a compiler issue (hasn't been yet) or the latter static builds so that people didn't have to get the libc for 3.3.5. Andy
I forgot... GCC 3.3.5 needs an updated glibidl too.
Fix checked in. I think we'll wait on the new GCC stuff until it is official.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
The different steps involved in building should be layed out a bit nicer (start new lines). In the earlier patch the instructions for the GCC CSD package and the checkout step (that now requires the .mozconfig before the pull) were not accurate. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I took the last diff from Peter and added one more information. Could someone please check if this diff is ok, as this is my first attempt to create a diff for the website. The diff was created against the current version of the website.
Attached file The original file
Here's the original file. Please make the diffs against it. The new ones aren't applying. Thanks
I just looked at the GCC setup page and it seems to contain all the changes that were in my diff file. Did somebody else apply them already?!
You can look at the changes to the webpages using the "Document History" link at the bottom. And yes, from that it seems that Mike's checkin did work, despite the messages he got. So I am resolving this as fixed again, the stuff that other people in the newsgroups found out should probably go into a new bug.
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: