9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ISHWAR RATTAN <rattan@cps.cmich.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: plan9port compilation failure
Date: Thu,  6 Jul 2006 23:27:07 -0400	[thread overview]
Message-ID: <Pine.GSO.4.61.0607062324190.18210@cps222.cps.cmich.edu> (raw)
In-Reply-To: <676c3c4f0607061319r25765e59pc566320f1b2d4e69@mail.gmail.com>



On Thu, 6 Jul 2006, Richard Bilson wrote:

> There's a block of code that is #ifdef __sun__ in threadimpl.h that
> breaks Solaris. I was just in the process of preparing a diff when I
> was distracted by other things.
>
> In particular, this block is unnecessary and harmful:
>
> #if defined(__sun__)
> #	define mcontext libthread_mcontext
> #	define mcontext_t libthread_mcontext_t
> #	define ucontext libthread_ucontext
> #	define ucontext_t libthread_ucontext_t
> #	include "sparc-ucontext.h"
> #endif
>

After commenting out this code in src/libthread/thread_impl.h, I was able
to a little further now the compilation stopped at:
...
9l -o o.readcons readcons.o
9l -o o.resample resample.o
ld: fatal: library -lmemlayer: not found
ld: fatal: library -lmemdraw: not found
ld: fatal: File processing errors. No output written to o.resample
collect2: ld returned 1 exit status
mk: 9l -o o.resample ...  : exit status=exit(1)
mk: for i in ...  : exit status=exit(1)
$

---
-ishwar



  reply	other threads:[~2006-07-07  3:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 20:06 ISHWAR RATTAN
2006-07-06 20:19 ` Richard Bilson
2006-07-07  3:27   ` ISHWAR RATTAN [this message]
2006-07-07  3:30     ` William Josephson
2006-07-07 16:44       ` Russ Cox
2006-07-10 15:26         ` Axel Belinfante
2006-07-11  2:37           ` Roman Shaposhnik
2006-07-12  9:26             ` 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=Pine.GSO.4.61.0607062324190.18210@cps222.cps.cmich.edu \
    --to=rattan@cps.cmich.edu \
    --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).