From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] any success with current plan9port on sunos5.8?
Date: Mon, 14 Jun 2004 13:30:50 +0200 [thread overview]
Message-ID: <200406141130.i5EBUoJ13665@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Mon, 14 Jun 2004 10:05:23 +0000." <cajs41$g7a$1@newstree.wise.edt.ericsson.se>
Bengt wrote:
> Richard C Bilson wrote:
>
> > Well, I had to comment out some stuff that doesn't work and rename a
> > few symbols, but in large part it works. I believe Bengt already
> > described most of these problems. I'm typing this in acme right now.
> >
>
> it has to be added that i only got things to compile. i can not get the
> graphical programs (sam, acme, 9term) to work. the window appears, but
> there is no content. a working acme is much better result than i
> managed. congratulations.
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,
do something like
nm o.acme |grep yield
If you have both p9yield and yield you likely have the same problem.
in the same way, try (typing path from memory)
nm $PLAN9/src/libthread/fdwait.o | grep yield
that is where my problem originated.
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.
My fix was:
; cvs diff fdwait.c
Index: fdwait.c
===================================================================
RCS file: /cvs/plan9/src/libthread/fdwait.c,v
retrieving revision 1.8
diff -r1.8 fdwait.c
1c1
< #define NOPLAN9DEFINES
---
> //#define NOPLAN9DEFINES
This is to make sure that the following workaround to
deal with the yield name clash has the right effect.
Index: thread.h
===================================================================
RCS file: /cvs/plan9/include/thread.h,v
retrieving revision 1.9
diff -r1.9 thread.h
124c124,128
< int yield(void);
---
> 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 .
Axel.
next prev parent reply other threads:[~2004-06-14 11:30 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 [this message]
2004-06-16 8:48 ` Bengt Kleberg
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=200406141130.i5EBUoJ13665@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).