[M3devel] cm3 is broken: More info

[Rodney M. Bates]

OK, I got a working compiler from 5.8.6, and it is now statically linked to
all modula-3 libs.

rodney at allegheny:~/proj/m3/exp/trytemp/src$ cm3 -version
Critical Mass Modula-3 version d5.10.0
   last updated: 2015-05-21
   compiled: 2015-08-25 19:02:01
   configuration: /usr/local/cm3/bin/cm3.cfg
   host: AMD64_LINUX
   target: AMD64_LINUX


rodney at allegheny:~/proj/m3/exp/trytemp/src$ ldd /usr/local/cm3/bin/cm3
	linux-vdso.so.1 =>  (0x00007fff54bfe000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f8cca5b8000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f8cca39a000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8cc9fd2000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f8cca8de000)




I did a fresh pull of modula3-cm3, and  removed and re-checked out a couple of locally
edited git-tracked files, so my working is as github.  git diff HEAD shows only a prompt.
Then I make a full backup of my 5.8.6 installation directory, switched to it (the original),
went to scripts/python, and did ./upgrade-full.sh 2>&1 | tee upgrade-full.sh.log.  I did not
do anything to disable rebuilding of m3cc.  I had some changes in the last pull, and lots
since 5.8.6.

Eventually the rebuild of everything failed in cvsup, which is probably entirely irrelevant.

There are many clean steps that look like:

== package /home/rodney/proj/m3/git/cm3/m3-libs/m3core ==

  +++ rm -rf AMD64_LINUX +++
  ==> [<function _RealCleanFunction at 0x7fa1568ed050>] returned 0

Are they cleaning or failing to clean?  In selected cases, they are
followed by build and ship steps that do nothing:

== package /home/rodney/proj/m3/git/cm3/m3-libs/m3core ==

  +++ /usr/local/cm3/bin/cm3    -build -DROOT=/home/rodney/proj/m3/git/cm3 +++
  ==> /home/rodney/proj/m3/git/cm3/m3-libs/m3core done

  +++ /usr/local/cm3/bin/cm3  -ship -DROOT=/home/rodney/proj/m3/git/cm3 +++
  ==> /home/rodney/proj/m3/git/cm3/m3-libs/m3core done

So I must have had some non-bootstrappable intermediate version of something?


 > On 08/25/2015 04:56 AM, Jay K wrote:
> I should have said you are close, it makes mostly sense, but not entirely. Anyway..
>
>
> upgrade-full.sh, which is upgrade.py followed by rebuilding everything (in some cases, a third, unnecessary time), just brought me again from:
>
>
>
> % cm3 -version
> Critical Mass Modula-3 version 5.8.6
>    last updated: 2010-04-11
>    compiled: 2010-07-12 20:10:34
>    configuration: /home/jkrell/cm3/bin/cm3.cfg
>    host: AMD64_LINUX
>    target: AMD64_LINUX
>
>
> to
>
>
> % cm3 -version
> Critical Mass Modula-3 version d5.10.0
>    last updated: 2015-05-21
>    compiled: 2015-08-25 09:33:26
>    configuration: /home/jkrell/cm3/bin/cm3.cfg
>    host: AMD64_LINUX
>    target: AMD64_LINUX
>
>
> in "one" step (automating many steps)
>
> Here is from scripts/python/capture-boot.py:
>    https://modula3.elegosoft.com/cm3/uploaded-archives/cm3-boot-AMD64_LINUX-1.tar.gz
>
>
> Do you have any local edits?
>
>
> Removed stuff or reordered in pkginfo.txt?
>
>
> (I edited one line in 5.8.6's config, to stop looking for m3cc).
>
>   - Jay
>
>
>
>-- 
Rodney Bates
rodney.m.bates at acm.org