Greetings,
I have spent hours on a trivial problem that I still haven't figured out. I
am using 9front, and I am building a C app using mk. I understand about
that parallel stuff so I am calling mk with -s for now. There are actually
three problems, but the fact that it won't build is clearly th
On Wednesday 18 of December 2013 09:23:19 Blake McBride wrote:
>
> Problem 1:
>
it seems you have an un-stated dependency/cies among your intermediate targets
/ prerequisites.
Say, foo.o depends on foo.c and foo.h -- but foo.h also depends on
generated_foo.h, which should be generated by mak
Thanks for the help! See below:
On Wed, Dec 18, 2013 at 9:37 AM, dexen deVries wrote:
> On Wednesday 18 of December 2013 09:23:19 Blake McBride wrote:
> >
> > Problem 1:
> >
>
>
> it seems you have an un-stated dependency/cies among your intermediate
> targets
> / prerequisites.
>
> Say, foo.o
On Wed, Dec 18, 2013 at 9:23 AM, Blake McBride wrote:
>
>
> Problem 3:
>
> Somehow Unix or GNU "make" doesn't mix up buffered stdout with unbuffered
> stderr output. They remain in order so the total out of make and all of
> the commands are shown in order and in context. You know, so a human ca
On Wed, 18 Dec 2013 10:11:22 CST Blake McBride wrote:
> >
> > Somehow Unix or GNU "make" doesn't mix up buffered stdout with unbuffered
> > stderr output. They remain in order so the total out of make and all of
> > the commands are shown in order and in context. You know, so a human can
> > und
D on Plan 9? This is madness.
--
Aram Hăvărneanu
This is not D. It is a language of my own design called Dynace. It adds
multiple inheritance, a metaobject protocol, generic functions, weak
typing, garbage collection all to standard C. Class users (*.c files) are
standard C in every way, there is only one data type added. The system is
writte
Seeing a Go link on your homepage I thought, oh, you also program in go?
And then found that you actually *play* go (Google harmed a lot looking for
information on the game). More surprising :D
On Wed, Dec 18, 2013 at 6:18 PM, Blake McBride wrote:
> This is not D. It is a language of my own de
Often there is a set of reasonable, alternative algorithms one may utilize
to solve a problem. Then, there is a set of unreasonable algorithms one
may employ that may or may not solve the problem given various conditions.
"make" has a proven reasonable algorithm to solve the problem for which it
Quoting Blake McBride :
I'd be a better judge if I understood the purposeful, thought out reason
behind the problems I am experiencing - assuming there is one. "That's
just the way it works" or "we do it differently because we are not unix"
are stupid as hell arguments.
No they aren't.
Meanw
On Wed, 18 Dec 2013 11:28:21 CST Blake McBride wrote:
>
> I'd be a better judge if I understood the purposeful, thought out reason
> behind the problems I am experiencing - assuming there is one. "That's
> just the way it works" or "we do it differently because we are not unix"
> are stupid as h
In response to both of you:
On Wed, Dec 18, 2013 at 11:28 AM, Blake McBride wrote:
> ...
>
> I remain confident that there is a thought out, reasonable algorithm
> employed by mk that I am yet ignorant of.
>
> Blake
>
>
If you could point me in the right direction, I'd surely appreciate it.
On
In particular, why would manual execution while echoing $status (to be sure
no errors are reported) work, but mk execution of the exact same sequence not
work?
Thanks!
Blake
On Wed, Dec 18, 2013 at 12:20 PM, Blake McBride wrote:
> In response to both of you:
>
> On Wed, Dec 18, 2013 at 11:28
The problem is solved, but I do have questions that I couldn't the answer
to in any of the docs.
On Wed, Dec 18, 2013 at 9:37 AM, dexen deVries wrote:
>
>
> -s won't help you there, because it regards processing of /command line/
> arguments, not of prerequisites. consider:
>
> $ NPROC=1 mk my_ta
On Wed Dec 18 04:48:29 EST 2013, conor.willi...@gmail.com wrote:
> i'm getting an error code 87 writing usbdisk to my key:
>
> according to the web: The second fix prevents USB Image Tool from
> restoring invalid images in device mode. A valid device mode image
> has to be multiple of 512. If
You could put NPROC=1 in the mkfile.
Thanks. That is what I was wondering. In the interim, and having a better
understanding of what is going on, I was able to re-work my mkfile to
support parallel builds where possible. I am, however, experiencing a new
problem. I will write that up in a separate post.
Thank for the info!
Blake
Greetings,
I apologize for beating the heck out of the group. I admit that some of my
questions are premature. I appreciate everyones help.
I have a better handle on what is going on, and with that knowledge, I was
able to restructure the mkfile to work correctly in parallel. I am
encountering
> On Dec 18, 2013, at 17:01, Blake McBride wrote:
>
> I apologize for beating the heck out of the group. I admit that some of my
> questions are premature. I appreciate everyones help.
>
Don't worry about asking questions ever, man. It's good to see, seeing people
willing to ask questions
> I think this is caused because the time slice is too short and the system
> can't tell the build times apart. Even though main clearly came after main.8
> the system sees them as the same time. Of course this can cause mk to
> dothe link again unnecessarily if
> mk is called again. This is wha
I'm finally getting tired of having to type passwords and am setting up
secstore on the 9atom cpuserver on a VirtualBox VM on my mac. I'm running
into some problems presumably because some of the secstore files and
directories are owned by glenda and not adm (i'm part of the adm and sys
groups)
I
Thanks for the encouragement. I'll move into other areas soon. I'll try
to do as much research as possible before posting.
On Wed, Dec 18, 2013 at 4:08 PM, Matthew Veety wrote:
>
>
> > On Dec 18, 2013, at 17:01, Blake McBride wrote:
> >
> > I apologize for beating the heck out of the group.
On Wed, Dec 18, 2013 at 4:16 PM, erik quanstrom wrote:
> > I think this is caused because the time slice is too short and the system
> > can't tell the build times apart. Even though main clearly came after
> main.8
> > the system sees them as the same time. Of course this can cause mk to
> > do
In part to substitute issues with time with issues with checksums, I am
writing a build tool for Inferno loosely inspired by djb's redo. I think
it deals nicely with some of the problems of make/mk tools: it handles
multiple outputs, treats shell variables as /env files for dependencies,
and uses
Thanks, I managed to convert the key this way and added it to factotum.
I think I also need to add the server's CA's certificate, so factotum can
check the server identity. Right?
I converted the CA crt to DER like this:
openssl x509 -in ca.crt.pem -inform PEM -out ca.crt.der -outform DER
Not I'
An Exynos port of Plan 9 on a ChromeBook... that would be seriously cool!
On Thu, Dec 19, 2013 at 4:12 PM, Steven Stallion wrote:
> Evening 9fans,
>
> While working on the Chromebook (nee exynos) port I ended up in a
> situation where I needed to use a more sophisticated JTAG debugger to
> find
> I'm finally getting tired of having to type passwords and am setting up
> secstore on the 9atom cpuserver on a VirtualBox VM on my mac. I'm running
> into some problems presumably because some of the secstore files and
> directories are owned by glenda and not adm (i'm part of the adm and sys
> g
> So, I think you are saying, that for pieces in a mkfile that take less than
> 1s to build it is possible for them to be build again, unnecessarily, when
> mk is run again. This is normal and just the way it is. Is that correct?
to be more explicit. if a is built from b and mtime(a) <= mtime(b
> In part to substitute issues with time with issues with checksums, I am
> writing a build tool for Inferno loosely inspired by djb's redo. I think
> it deals nicely with some of the problems of make/mk tools: it handles
> multiple outputs, treats shell variables as /env files for dependencies,
>
On Thu, 19 Dec 2013 00:40:52 EST erik quanstrom wrote:
> if the point is to
> make mk precise, that goal can be accomplished with a little effort.
I suppose making atime, mtime of type struct timespec would
break too much including 9p?
> I think I also need to add the server's CA's certificate, so factotum
> can check the server identity. Right?
Factotum is meant to store the private keys. The CA certificate
would probably have its place in /sys/lib/tls (in PEM format).
However, this is not needed, since the current X.509 implem
31 matches
Mail list logo
