[M3devel] Fwd: Re: unicode in libm3 or separate package

[Jay K]

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