9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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:20 +0000	[thread overview]
Message-ID: <cam46k$hfh$1@newstree.wise.edt.ericsson.se> (raw)
In-Reply-To: <200406141130.i5EBUoJ13665@zamenhof.cs.utwente.nl>

Axel Belinfante wrote:
...deleted
> Just to make sure you do not have the same problem as I had:
> check which *yield* symbols are present in your non-working binary,

i have both p9yield and yield present.


...deleted
> Fix it by recompiling fdwait.c such that the yield() call
> in that file gets #define'ed to p9yield, so there is no
> reference any more to the sunos system library yield routine.

will do.


...deleted
>>int	p9yield(void);
>>#ifndef NOPLAN9DEFINES
>>#define       yield   p9yield
>>#endif
>>
> 
> 
> Looking at it now, I guess a different (better?!?) solution might be
> to simply remove the #ifndef NOPLAN9DEFINES and #endif lines from
> around above #define in thread.h .

imho the idea of NOPLAN9DEFINES is to make sure that only the original 
operating systems definitions are present. it would be very confusing to 
  get yield() replaced with p9yield() after having defined NOPLAN9DEFINES.

your first idea is better. however, i do not think it is perfect. 
instead, i wonder why fdwait.c had NOPLAN9DEFINE. if it was neccessary 
surely something else is now broken when it was removed. and if it was 
not neccessary, why was it there?


bengt


  reply	other threads:[~2004-06-16  8:48 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2004-06-16  8:48   ` [9fans] plan9port 9term Bengt Kleberg
2004-06-17  0:01     ` Axel Belinfante
2004-06-17  0:48       ` boyd, rounin
2004-06-17  9:05       ` Bengt Kleberg
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17  2:33 [9fans] any success with current plan9port on sunos5.8? 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 19:08 Richard C Bilson
2004-06-14 19:14 ` Charles Forsyth
2004-06-16  8:48 ` Bengt Kleberg
2004-06-16 23:50   ` Axel Belinfante
2004-06-17  9:05     ` Bengt Kleberg
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 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='cam46k$hfh$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).