| | Re: signals / legOS internals
|
|
(...) Now keep in mind that this is coming from someone who won't take Duke's OS class until next spring- is there any reason the current semaphore implementation couldn't be used for a large percentage of these tasks? I.E., thread A checks (or uses (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: legOS make newbe question
|
|
(...) Damn, I am too used to tcsh, and yet I still remembered the export. Make that: MAKE_MODE=UNIX; export MAKE_MODE (followed by make) Again, make --unix should also do the trick if that is easier to remember. Oh. My MAKE_MODE environment variable (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: signals / legOS internals
|
|
(...) What am I missing? Why do you need callbacks in the process structure? I was thinking if you can reference the thread, you can just call a system function (e.g. suspend(thread)), and that will suspend the thread. You do not need callbacks (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: legOS make newbe question
|
|
(...) Some versions of make look for the sh shell, others use the dos shell. Probably, make is using the dos shell and not sh. As far as I know, make does not parse the parens, the shell does. And dos does not understand the parens. My cygwin make (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: legOS make newbe question
|
|
Thanks Lou, I am sure that you are right. I also don't know what could cause it or how to fix it. I just hope there is some bright person who reads this NG and can get me on to the next step. Based upon the discussion topics that I have seen, this (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: signals / legOS internals
|
|
(...) Cool. I will proceed. (...) Yup. I was out of the loop for awhile, and am once again whompin' on this project. (...) That is true. Signals would give the task the opportunity to stop/start tasks under its control, though, without the task that (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: legOS make newbe question
|
|
(...) More to the point, it cannot recognize the '(cd' command. Now, why that is, or how you can fix it, I do not know. It would appear to be a problem with make or with your shell. It should just be farming the entire line off to the shell, which (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: signals / legOS internals
|
|
(...) No, you should not abandon your implementation - not if you want to use LegOS. I was only explaining how I implemented similar functionality, for the sake of comparison. Regarding Librcx, I might release another version at some point, to add (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: legOS make newbe question
|
|
I reinstalled everything and I have progressed to the point of seeing the first-c++.o file and it stops with the following error: -snip- C:\legOS-0.1.7>make h8300-hms-g++ -DCXX -O2 -fno-builtin -fomit-frame-pointer -Wall -Wno-unused -Wno (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: signals / legOS internals
|
|
(...) So, should I abandon my implementation? If something every bit as good is already there, it may be silly for me to continue. I haven't looked at Librcx yet, so I don't completely understand how it works. I think one of the original reasons for (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|