From: Bengt Kleberg <bengt.kleberg@ericsson.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] any success with current plan9port on sunos5.8?
Date: Wed, 16 Jun 2004 08:48:32 +0000 [thread overview]
Message-ID: <cam81t$jk9$1@newstree.wise.edt.ericsson.se> (raw)
In-Reply-To: <200406141908.i5EJ8Ll01370@plg2.math.uwaterloo.ca>
Richard C Bilson wrote:
...deleted
> I don't know if there's a good reason for requiring __EXTENSIONS__
> to be defined, but it didn't break anything that I can see and
> it made the yield problem go away.
on my plan9port (plan9-20040517.tar.gz) __EXTENSIONS__ is neccessary to
compile plan9/src/cmd/9term/SunOS.c . however, i think it is better to
defined it just for that file. obvious diff included below.
i would like to thank you for the diff to u.h. i also experimented with
removing __EXTENSIONS__ to get rid of sun-os yield(). however, since i
failed to remove the 3 #undef _NEED* after <sys/types.h> very little
compiled properly.
i reinstated __EXTENSIONS__, and after that i slowly got myself totally
lost in various attempts to get replace yield() with p9yield(). you
saved me. with your change to u.h (and my change to 9term/SunOS.c)
everything seems to both compile and run. no changes neccessary to
fdwait.c, sched.c nor thread.h.
bengt
*** /home/eleberg/private/plan9/src/cmd/9term/SunOS.c.original Tue Jun
15 08:42:44 2004
--- /home/eleberg/private/plan9/src/cmd/9term/SunOS.c Tue Jun 15
08:42:46 2004
***************
*** 1,4 ****
--- 1,5 ----
#include <u.h>
+ #define __EXTENSIONS__
#include <termios.h>
#include <stropts.h>
#include <libc.h>
next prev parent reply other threads:[~2004-06-16 8:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 19:08 Richard C Bilson
2004-06-14 19:14 ` Charles Forsyth
2004-06-16 8:48 ` Bengt Kleberg [this message]
2004-06-16 23:50 ` Axel Belinfante
2004-06-17 9:05 ` Bengt Kleberg
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 2:33 Richard C Bilson
2004-06-17 7:53 ` Axel Belinfante
2004-06-17 16:11 ` Russ Cox
2004-06-17 21:35 ` Axel Belinfante
2004-06-18 9:06 ` Bengt Kleberg
2004-06-18 10:09 ` Axel Belinfante
2004-06-18 9:05 ` Bengt Kleberg
2004-06-17 17:08 ` Lyndon Nerenberg
2004-06-17 17:36 ` Russ Cox
2004-06-18 9:05 ` Bengt Kleberg
2004-06-18 13:02 ` Axel Belinfante
2004-06-18 9:06 ` Bengt Kleberg
2004-06-18 9:33 ` William Josephson
2004-06-18 9:47 ` Axel Belinfante
2004-06-14 19:37 Richard C Bilson
2004-06-14 14:12 Richard C Bilson
2004-06-14 13:39 Richard C Bilson
2004-06-14 13:52 ` Axel Belinfante
2004-06-11 14:18 Richard C Bilson
2004-06-11 13:51 Richard C Bilson
2004-06-11 14:02 ` C H Forsyth
2004-06-11 13:58 ` William Josephson
2004-06-11 14:18 ` Russ Cox
2004-06-11 15:05 ` Axel Belinfante
2004-06-14 10:05 ` Bengt Kleberg
2004-06-14 11:30 ` Axel Belinfante
2004-06-16 8:48 ` Bengt Kleberg
2004-06-11 12:19 Axel Belinfante
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='cam81t$jk9$1@newstree.wise.edt.ericsson.se' \
--to=bengt.kleberg@ericsson.com \
--cc=9fans@cse.psu.edu \
/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).