[M3devel] CM3 Next Problem (cm3 start msg)

[Jay K]

I never use any of the .sh files. I find .sh to be not a worthwhile language to use for much.

I only use the .py files, or the occasional very small .sh file that just runs a litte .py.


I very much recommend the .py files.


When I wrote upgrade.py, based on upgrade.sh, I slightly misunderstood.

So upgrade-full.sh is a close approximation (and look how trivial it is -- just calls others).


  - Jay


________________________________
From: M3devel <m3devel-bounces at elegosoft.com> on behalf of Rodney M. Bates <rodney_bates at lcwb.coop>
Sent: Thursday, October 6, 2016 3:03 PM
To: Wolfgang Keller; rodney.m.bates at acm.org; m3devel
Subject: Re: [M3devel] CM3 Next Problem (cm3 start msg)



On 10/06/2016 05:08 AM, Wolfgang Keller wrote:
> Under "scripts" I find a "upgrade.sh" script and also "make-src-update.sh", "make-src-files-update.sh". Which ones should I apply?
>

upgrade.sh

Jay, what do the other two do?

> Are you saying the update script is using 5.8.6 cm3 to compile everything needed for the next version?
>

yes.

> - Wolfgang
>
>
> Am 04.10.2016 um 20:55 schrieb Rodney M. Bates:
>>
>>
>> On 10/04/2016 06:53 AM, Wolfgang Keller wrote:
>>> This is a bit of a philosophical problem how to compile a compiler. I noticed several elements of the compiler package are written in M3, so this poses the question with what compiler to compile a compiler,when the compiler is needed to compile it? Also there is the question what are the elemental libraries the compiler is referring to (runtime libraries) - without compiling them - and probably the 5.8.6 compiler refers to 5.8.6 runtime packages and linking them into the result, while the target system CM3 is located inside the latest Git system. This may cause confusion in references. So how to solve this?
>>>
>>
>> Yes, almost all of the entire cm3 distribution, including the compiler and the
>> libraries it uses, is written in Modula3.  We work at keeping the latest version
>> bootstrappable by the release compiler/libraries.  In order to make some improvements,
>> we've had to introduce compiler/library interdependencies that require nontrivial
>> bootstrap process.  The update.sh script takes care of this, if you want to
>> compile the git version of everything.  Don't be bothered by the amount of work
>> it does.  I recompiles some things two or three times, and takes quite a bit of
>> time.
>>
>> We are really overdue to package up a new release.
>>
>>> - Wolfgang
>>>
>>>
>>> Am 01.10.2016 um 03:50 schrieb Wolfgang Keller:
>>>>
>>>> Hello Rodney
>>>>
>>>> Coming back to the "next problem" series, I pick the following:
>>>>
>>>>     constant error reaction of "cm3" compiler program
>>>>
>>>> 1) I am working with and referring to the pre-release which I downloaded from GitHub
>>>>
>>>> d5.9.0 AMD64_LINUX as of Aug 19 2014; <https://github.com/modula3/cm3/releases/tag/verification-release-x86_64>I run Linux 4.4.0-36 in Ubuntu 14.04.
[https://avatars3.githubusercontent.com/u/7759860?v=3&s=400]<https://github.com/modula3/cm3/releases/tag/verification-release-x86_64>

modula3/cm3<https://github.com/modula3/cm3/releases/tag/verification-release-x86_64>
github.com
cm3 - Critical Mass Modula-3



>>>>
>>>> 2) Problem: If "cm3" is started with unspecific or without parameter, the constant reaction is a fundamental error message:
>>>>
>>>> ***
>>>> *** runtime error:
>>>> ***    Exception "PathnamePosix.CheckedRuntimeError" not in RAISES list
>>>> ***    file "../src/os/POSIX/PathnamePosix.m3", line 98
>>>> ***
>>>>
>>>> This error does not appear to refer to any source-text input.
>>>>
>>>>
>>>> Regards
>>>>
>>>> - Wolfgang
>>>>
>>>>
>>>
>>
>
>

--
Rodney Bates
rodney.m.bates at acm.org
_______________________________________________
M3devel mailing list
M3devel at elegosoft.com
https://m3lists.elegosoft.com/mailman/listinfo/m3devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20161008/3cab798b/attachment.html>