[M3devel] two questions on bootstrapping the compiler

[Coleburn, Randy]

Ok, I thought I understood this, but now I'm not sure.

I had trouble rebuilding everything due to the recent changes.  So, I ran Jay's upgrade.py to see what it does.

I find that upgrade.py does some housekeeping with the CFGs, then builds and ships the following 11 packages:
                package C:\cm3\Sandbox\m3-win\import-libs
                package C:\cm3\Sandbox\m3-libs\sysutils
                package C:\cm3\Sandbox\m3-sys\m3middle
                package C:\cm3\Sandbox\m3-sys\m3objfile
                package C:\cm3\Sandbox\m3-sys\m3linker
                package C:\cm3\Sandbox\m3-sys\m3back
                package C:\cm3\Sandbox\m3-sys\m3staloneback
                package C:\cm3\Sandbox\m3-sys\m3front
                package C:\cm3\Sandbox\m3-sys\m3quake
                package C:\cm3\Sandbox\m3-sys\cm3
                package C:\cm3\Sandbox\m3-tools\m3bundle

Note that "m3staloneback" and "m3bundle" are not listed as being part of the "front" group in pkginfo.txt.

Next, upgrade.py does some more housekeeping, then builds and ships the following 14 packages:
                package C:\cm3\Sandbox\m3-win\import-libs
                package C:\cm3\Sandbox\m3-libs\m3core
                package C:\cm3\Sandbox\m3-libs\libm3
                package C:\cm3\Sandbox\m3-libs\sysutils
                package C:\cm3\Sandbox\m3-sys\m3middle
                package C:\cm3\Sandbox\m3-sys\m3objfile
                package C:\cm3\Sandbox\m3-sys\m3linker
                package C:\cm3\Sandbox\m3-sys\m3back
                package C:\cm3\Sandbox\m3-sys\m3staloneback
                package C:\cm3\Sandbox\m3-sys\m3front
                package C:\cm3\Sandbox\m3-sys\m3quake
                package C:\cm3\Sandbox\m3-sys\cm3
                package C:\cm3\Sandbox\m3-tools\m3bundle
                package C:\cm3\Sandbox\m3-sys\mklib

The difference here is that "m3core" and "libm3" (which are in the "front" group) are added back to the list.

Q1:  So, am I to infer that in the process of "bootstrapping" a new compiler using an old one, that you have to leave out "m3core" and "libm3" on the first pass, or is there some other logic going on here?

Q2:  Next, if "m3staloneback" and "m3bundle" are needed, shouldn't they be listed as part of the "front" group in pkginfo.txt?

Regards,
Randy Coleburn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100112/44324723/attachment-0001.html>