[Coco] Building lwtools and HG NitrOS-9 or NOT was ack

Bill Pierce ooogalapasooo at aol.com
Wed Jun 5 18:17:24 EDT 2013


Tormod,
Is there any way you could post a list of most of the hg cmd set?
Being a "repo" newbie, I would greatly appreciate it. I am now just beginning to grasp the concept but lack info and the info I've found is sparse.
One thing I would like to know is how to upload an initial source set to a new repo. I have a repo I'm starting but cannot figure out how to get the 1st sources up there.
Also, how do you obtain an SSH key to automate your password?
No, I have no commit access to the nitros9 repo and do not want it, this is for my own repo.

 It seems everyone is getting a lot of errors trying to build Nitros9. Other than Level 3, Pac09, and a strange error in MSF (none of these will build for now and never have that I know of, except maybe msf), most can be eliminated with one or two changes.

 In Level 1 Boisy added "fdebug.asm" to "krnp2.asm" but never put the "fdebug.asm" source into "level1/modules/kernel" and krnp2.asm looks for it there. It's in "level2/modules/kernel" but needs to be in the first for krnp2 to assemble in level 1.
 Also, he included "reboot" into the makefile for level 1 cmds, but never moved the source over as well. You can move the source over, but "reboot" has a build error in that I think it uses a level 2 system call and errors out since the syscall isn't in the level 1 defs, stopping and causing the rest of the cmds to not build therefore causing errors anywhere these cmds are referenced which is in every system build. The easy way out is to delete "reboot" from the cmds list in the makefile in "level1/cmds" and all cmds build again. According to Boisy's note in "krnp2.asm", he added "fdebug.asm" system call to allow rebooting, but to me level 1 boot is already too big and that just makes it bigger. This boot needs to be trimmed down in size before a C compiler will run properly from within NitrOS-9 Level 1 (I've tried, no go). Maybe a conditional could be added to avoid it in Level1.

The problem I am having now is cygwin runs out of resources while making the disks. It seems to do this while setting attributes on huge file lists. Then when copy (CP) is called I get "Error 218" (no permission) as read n write have not bee set, then later in finalizing the actual disks, the files don't exsist since they were never copied and I get a bunch of "Error 216"s (file not found). I have no clue how to fix this
. Any ideas?

Thanks

Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com




-----Original Message-----
From: Tormod Volden <lists.tormod at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Wed, Jun 5, 2013 5:23 pm
Subject: Re: [Coco] Building lwtools and HG NitrOS-9 or NOT was ack


1. Make sure you're pulling from the latest repo location:
 hg pull
should return "pulling from http://hg.code.sf.net/p/nitros9/code"
Otherwise edit .hg/hgrc .

2. Make sure you're on the lwtools-port branch (for now):
 hg branch
should return "lwtools-port". Otherwise run "hg update lwtools-port"
to switch branch.

3. Make sure you have pulled the latest stuff:
 hg tip
should return (as of writing) "changeset:   2829:ed9a4cb85fb3" (Fixed
makefiles and defsfile for level 3).
Otherwise run "hg pull" and "hg update" again.

Hope this helps,
Tormod

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco

 



More information about the Coco mailing list