<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br> > Currently, the release searches all over much of the known universe for a cm3cg/m3cgc1<BR> <BR> <BR>I agree that was probably a mistake and I think I downgraded it to only do that for cross builds.<BR>Though cross builds should probably use, like, /usr/local/bin/cm3/<target>/cm3cg.<BR> <BR> <BR>- Jay<br> <BR><div><div id="SkyDrivePlaceholder"></div>> Date: Thu, 9 May 2013 20:02:45 +0000<br>> To: m3commit@elegosoft.com<br>> From: rodney@elego.de<br>> Subject: [M3commit] CVS Update: cm3<br>> <br>> CVSROOT: /usr/cvs<br>> Changes by: rodney@birch. 13/05/09 20:02:45<br>> <br>> Modified files:<br>> cm3/m3-sys/cminstall/src/config-no-install/: Tag: <br>> release_branch_cm3_5_8 <br>> cm3cfg.common <br>> <br>> Log message:<br>> Since dinosaurs roamed freely, the cm3 executable is not shipped,<br>> even if you specify ship or buildship, unless you also set environment<br>> variable INSTALL_CM3_IN_BIN="yes". This avoids:<br>> <br>> 1) Undermining an executing executable, which won't work on some OSs, and<br>> <br>> 2) Changing compilers in the middle of group of builds. Everything can be<br>> built with the same, prexisting compiler, including the compiler. This<br>> is sometimes essential to avoid bootstrapping barriers, etc.<br>> <br>> A built but not shipped compiler can be installed later, using<br>> scripts/install-cm3-compiler.sh.<br>> <br>> Item 2) above is also relevant to cm3cg as well. We currently have an apparent<br>> bootstrap barrier where both cm3 and cm3cg need to be updated to the head<br>> atomically. As is, a new cm3cg is built and installed in /usr/local/cm3/bin,<br>> while the old cm3 remains. If that is the release cm3, every following M3<br>> compilation suffers:<br>> <br>> m3cgc1: fatal error: *** illegal type: 0x17, at m3cg_lineno 4<br>> <br>> The change to m3-sys/m3cc/src/m3makefile in the *HEAD* is one part of the fix.<br>> It makes installing of cm3cg work like cm3.<br>> <br>> The change to m3-sys/cminstall/src/config-no-install/cm3cfgt.common in the<br>> *RELEASE* is the other part. Currently, the release searches all over much<br>> of the known universe for a cm3cg/m3cgc1, and will pick up even an uninstalled<br>> one in preference to the installed version, creating the same problem. This<br>> seems very difficult to fix without changing the release branch.<br>> <br></div> </div></body>
</html>