9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Stanley Lieber" <stanley.lieber@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx on OpenBSD
Date: Wed, 16 Feb 2011 10:05:42 -0600	[thread overview]
Message-ID: <d1cccbdb41f2cc918c34df736502ada7@EXAMPLE> (raw)
In-Reply-To: <AANLkTimMENJaKMswV7mJTfqKmm+ZPpOHpOTUO0PFwbo7@mail.gmail.com>

> On Wed, Feb 16, 2011 at 7:36 AM, Stanley Lieber
> <stanley.lieber@gmail.com> wrote:
>> Reading old 9fans posts, I found Iru's modifications of vx32/9vx to run on OpenBSD 4.3.
>> With this minor change:
>>
>> src/9vx/Makefrag:184:       echo 'ulong kerndate ="' `date +%s` '";' >9vx/kerndate.h
>>
>> I was able to get it to build on a current snapshot of OpenBSD.
> 
> It really needs this change to run?
> 
> ron

Without the change, gmake dies here:

echo 'ulong kerndate =' `date +%s` ';' >9vx/kerndate.h
gcc -g -O3 -MD -std=gnu99 -I.  -I. -I9vx -I9vx/a -Wall -Wno-missing-braces -c -o 9vx/stub.o 9vx/stub.c
In file included from 9vx/stub.c:405:
9vx/kerndate.h:1: error: 'Wed' undeclared here (not in a function)
9vx/kerndate.h:1: error: expected ',' or ';' before 'Dec'
gmake: *** [9vx/stub.o] Error 1

-sl




  reply	other threads:[~2011-02-16 16:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 15:36 Stanley Lieber
2011-02-15 21:01 ` ron minnich
2011-02-16 16:05   ` Stanley Lieber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-16 16:42 Stanley Lieber
2011-02-15 22:06 ` ron minnich
2011-02-16 17:06   ` Stanley Lieber
2011-02-15 23:34     ` Anthony Martin
2011-02-15 23:53       ` Stanley Lieber
2011-02-16  0:10         ` ron minnich
2011-02-16  1:13           ` Stanley Lieber
2011-02-16  1:17             ` ron minnich
2011-02-16  1:23               ` Stanley Lieber
2011-02-16  1:24               ` Devon H. O'Dell
2011-02-16  2:14             ` Anthony Martin
2011-02-16  0:50 rsdehart
2011-02-16  0:36 rsdehart
2011-02-16  0:26 rsdehart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d1cccbdb41f2cc918c34df736502ada7@EXAMPLE \
    --to=stanley.lieber@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).