Differences between revisions 17 and 18
Revision 17 as of 2011-04-12 16:59:37
Size: 1667
Editor: ?SteveLangasek
Comment:
Revision 18 as of 2011-04-13 13:13:31
Size: 1980
Editor: ?MatthiasKlose
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 1. Upload gnat-4.4 for full multiarch. (Must be uploaded before uploading gcc-4.4 because gnat-4.4 self-build-depends, and needs the symlinks from gcc-4.4-base to be functional)  1. Upload gnat-4.4 for full multiarch. (Must be uploaded before uploading gcc-4.4 because gnat-4.4 self-build-depends, and needs the symlinks from gcc-4.4-base to be functional). The new gnat-4.4 will not be usable until gcc-4.4 is updated.
 1. Upload gcc-4.6 (providing the runtime libraries). Keep symlinks for the original locations of the runtime libraries? Would be better to have not yet updated gcc-4.5 and gcc-4.4 packages working, or do live with shorten brokeness of the default compiler.
Line 19: Line 20:
 1. Upload gcc-4.5 and gcc-4.4 for full multiarch.
Line 20: Line 22:
 1. Upload gcc-4.5, gcc-4.6 and gcc-4.4 for full multiarch.
1. Upload gcj-4.5, gcj-4.4, and any other gcc frontends that don't self-build-depend, for full multiarch.
 1. Upload gcj-4.6, gcj-4.4, and any other gcc frontends that don't self-build-depend, for full multiarch.

Bootstrapping the archive for multiarch

This page documents the order in which certain steps need to happen when converting the Debian archive over to multiarch. The information is based on the experience with bootstrapping multiarch in Ubuntu natty.

  1. (./) Upload dpkg support for DEB_HOST_MULTIARCH (dpkg 1.16.0)

  2. Upload multiarch-aware versions of build tools:
  3. Upload a "stage1" multiarch build of gcc-4.5, the default compiler *on i386* (not needed on other archs, where dpkg 1.16.0 does not change the multiarch path; so no additional upload is needed of other versions of gcc that are the default on other architectures)
  4. Upload multiarch-enabled eglibc.
  5. Upload gnat-4.4 for full multiarch. (Must be uploaded before uploading gcc-4.4 because gnat-4.4 self-build-depends, and needs the symlinks from gcc-4.4-base to be functional). The new gnat-4.4 will not be usable until gcc-4.4 is updated.
  6. Upload gcc-4.6 (providing the runtime libraries). Keep symlinks for the original locations of the runtime libraries? Would be better to have not yet updated gcc-4.5 and gcc-4.4 packages working, or do live with shorten brokeness of the default compiler.
  7. Upload ecj for multiarch. (Must also be uploaded before gcc-4.4/gcj-4.4 because of a similar self-build-depends on those archs that use ecj1.)
  8. Upload gcc-4.5 and gcc-4.4 for full multiarch.
  9. Rebuild asis with the new gnat-4.4
  10. Upload gcj-4.6, gcj-4.4, and any other gcc frontends that don't self-build-depend, for full multiarch.
  11. Upload everything else :-)