<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'>1) That isn't supposed to work. Sometimes it does, but there is no guarantee.<BR>2) yeah, we should fix that, make it be two steps and the second step optional<BR>Either via buildlocal + optional ship or buildship into a new location and then optionally copy.<BR> <BR> - Jay<br> <BR><div>> Date: Tue, 10 Dec 2013 11:59:54 -0600<br>> From: rodney_bates@lcwb.coop<br>> To: m3devel@elegosoft.com<br>> Subject: [M3devel] Fwd: Re: unicode in libm3 or separate package<br>> <br>> 4th try repost:<br>> <br>> <br>> -------- Original Message --------<br>> Subject: Re: [M3devel] unicode in libm3 or separate package<br>> Date: Wed, 04 Dec 2013 20:36:25 -0600<br>> From: Rodney M. Bates <rodney_bates@lcwb.coop><br>> To: m3devel@elegosoft.com<br>> <br>> Different meanings and procedures for bootstrapping. I am trying to ensure somebody<br>> without a previous M3 distribution can check one out, then build it with a binary<br>> only of the release compiler (e.g., via cminstall). I have not been using upgrade.sh,<br>> because it alters your /usr/local/cm3 in place, overlaying the original. This is not<br>> very handy for repeated experiments, when I have to keep recreating it. It will build<br>> though, with the dependencies in question.<br>> <br>> Instead, I have been using do-pkg.sh and do-cm3-*.sh. These, by default, use -override,<br>> which builds everything in the cvs checkout and leaves /usr/local/cm3 alone. In this case,<br>> trying to build a compiler first has no m3core or libm3 available, while building a<br>> library that depends on the newer compiler also fails. The separation I did allows this<br>> by getting code that an older compiler won't build into a separate package, where it can<br>> be done later. Unfortunately, it also means you can't just ship later, after all goes<br>> well.<br>> <br>> On 12/03/2013 06:56 PM, Jay K wrote:<br>> > Huh? No they aren't.<br>> ><br>> ><br>> ><br>> > bootstrapping uses old compiler to build everything /after /m3core/libm3 (up to cm3)<br>> > bootstrapping uses old compiler to m3front/m3back/m3quake/m3linker/cm3/sysutils, but not m3core/libm3.<br>> > Then bootstrapping uses new compiler to build everything.<br>> ><br>> ><br>> > m3core/libm3 can depend on new compiler.<br>> > m3front/m3back/m3quake/m3linker/cm3/sysutils cannot (except by more than one step, then they can -- "flexibility via multiple changes")<br>> ><br>> ><br>> > see<br>> > http://dcvs.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/scripts/upgrade.sh?rev=1.37;content-type=text%2Fplain <https://dcvs.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/scripts/upgrade.sh?rev=1.37;content-type=text%2Fplain><br>> > notice where m3core/libm3 appear.<br>> ><br>> ><br>> > which I don't use but is possibly clearer to people and what I use was based on it (I missed that upgrade.sh actually builds everything and mine stops at cm3).<br>> ><br>> ><br>> > - Jay<br>> ><br>> ><br>> > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>> --<br>> > Subject: Re: [M3devel] unicode in libm3 or separate package<br>> > From: hosking@purdue.edu<br>> > Date: Tue, 3 Dec 2013 19:13:46 -0500<br>> > CC: m3devel@elegosoft.com; rodney.bates@wichita.edu<br>> > To: jay.krell@cornell.edu<br>> ><br>> > Huh? They are when bootstrapping.<br>> ><br>> > Sent from my iPhone<br>> ><br>> > On 3 Dec 2013, at 4:54 pm, Jay K <jay.krell@cornell.edu <mailto:jay.krell@cornell.edu>> wrote:<br>> ><br>> > This is not necessary, but it is ok.<br>> ><br>> > m3core and libm3 are never built with an older compiler and can depend on a newer compiler.<br>> ><br>> ><br>> > - Jay<br>> ><br>> ><br>> > > Date: Tue, 3 Dec 2013 22:13:38 +0000<br>> > > To: m3commit@elegosoft.com <mailto:m3commit@elegosoft.com><br>> > > From: rodney@elego.de <mailto:rodney@elego.de><br>> > > Subject: [M3commit] CVS Update: cm3<br>> > ><br>> > > CVSROOT: /usr/cvs<br>> > > Changes by: rodney@birch. 13/12/03 22:13:38<br>> > ><br>> > > Modified files:<br>> > > cm3/m3-libs/libm3/src/rw/: Tag: devel_unicode m3makefile<br>> > ><br>> > > Log message:<br>> > > Move Unicode codec stuff to its own package. This allows for<br>> > > bootstrapping the unicode branch with release and head compilers.<br>> > > This code depends on being compiled with Unicode-sized WIDECHAR,<br>> > > which is not initially available when first compiling libm3 and<br>> > > the compiler, using an earlier compiler. New package libunicode<br>> > > can now be compiled later, after a new compiler is installed.<br>> > ><br>> > > script do-cm3-unicode.sh does everything do-cm3-front.sh does,<br>> > > plus libunicode.<br>> > ><br>> ><br>> <br>> <br>> <br></div> </div></body>
</html>