These are the changes i propose for the unic build instructions at: http://www.mozilla.org/build/unix.html I propose making 2 pages. The first one is small, not intimidating and fits in one screen full. There should be no technicalities in this page. There should be links to pages where thse techincalities are explained, though. The second page can have whatever technicalities and complications that are needed for whatever reason in whatever order, i dont care about this. Notes: + The redhat linux page is not really needed. The gtk rpm thing can go in the requirements section in page two. + Change LD_LIBRARY_PATH and MOZILLA_FIVE_HOME references to using ./mozilla-apprunner.sh. This is what we will ship and how the app should (and will be) run. + Take out anything that references NSPR rpms. This is not our problem anymore now that nspr can be built and used in the tree. + autoconf and m4 are not needed. Except if you are an autoconf hacker. I guess you need to divide the requirements section into 2, one for build requirements for mortals, and one for hackers. + The glibc2.07 patch reference is completely useless. No one in their right mind will rebuild glibc after applying this patch. If you must reference this bug, provide a link to the rpms on mozilla.org. The idea im trying to get across is that we need to use hyperlink technology to unclutter the main page. thanks. --one.html----------------------------------------------------------------- 1. Introduction LEAVE AS IS 2. Get the code LEAVE AS IS 3. Requirements Before proceeding, please see (two.html#requirements) for a list of requirements (stuff needed to build mozilla) 4. Automated build (client.mk) For a list of mozilla requirements, see (two.html#requirements) o cvs co mozilla/client.mk o cd mozilla o gmake -f client.mk To rebuild without pulling the tree: o gmake -f client.mk build_all To just pull the tree: o gmake -f client.mk pull_all There is a build configurator tools that allows you to configure your build using a web browser. See (LINK TO BUILD CONFIGURATOR) for more information. 5. Manual build o mkdir mozilla o cd mozilla o ./configure o gmake For configure options, run "./configure --help" Once you have configured, you only have to run configure if you add or remove Makefile.in files (cvs update can do this. Beware!). The list of makefiles is in mozilla/allmakefiles.sh. Please see (two.html#details) for build system details and power user features. 6. After the build o cd dist/bin o ./mozilla-apprunner.sh o ./mozilla-viewer.sh For more information on the mozilla build system, platform specific hacks, please see (two.html#details). --one.html---------------------------------------------------------

Leaf, I made this suggestion to you yesterday, but I thought I would add it here. The "build documentation", http://www.mozilla.org/build/ should list all the new unix pages you create, * Build Unix (easy) + Build Unix (All the gory details for tweakers) Also add the list of build pages directly onto the "source code" page, http://www.mozilla.org/source.html 3. Build Look at the build instructions to find out how to compile this beast. On Unix (easy) On Unix (detailed) On Win32 On MacPPC etc.

I've made a bit of progress; i need to clean up the links to these pages, and fix the unix-details.html page still.

The build page looks a lot better. It also does not need the table of contents at the top, or the "Getting the Code" section.

I went ahead and applied the patch. I hope that is ok.

thanks, slamm.

this is fixed and i can close this, can't i?

The "Detailed Unix Build Instructions" still need updating.

can we get this closed? leaf: what needs to happen in order to resolve this bug?

fitst thing on m6 last on m5

I've checked in some of the suggested fixes, but there's still more. I'll keep working on it, but this doesn't hold up M6

moving to m8, wip boy

What's the point of having this bug continuously open? Is there a specific checkin that needs to happen?

They look ok to me. Marking fixed.