From: Alexander Sychev <santucco@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 from user space on openbsd 4.7 amd64 fails to build
Date: Sat, 3 Jul 2010 19:51:00 +0400 [thread overview]
Message-ID: <AANLkTikhkC_M-hbRl4l8hm9fX-b041CllDbwiH5NAhU5@mail.gmail.com> (raw)
In-Reply-To: <50939b8a-2334-4475-9f03-4b48064f2121@w31g2000yqb.googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Hello!
That is easy - a file OpenBSD-x86_64-asm.s doesn't exist in
/usr/local/plan9/src/libthread.
By the way, OpenBSD-x86_64.c doesn't exist too. Both files have to contain
OpenBSD-specific implementations of some functions.
For plan9port there is a separated list where you should post related
messages - http://groups.google.com/group/plan9port-dev.
--
Best regards,
santucco
On Thu, Jul 1, 2010 at 1:14 PM, quiet_lad <gavcomedy@gmail.com> wrote:
> # cd
> plan9/
> # ./
> INSTALL
> + Mailing list: http://groups.google.com/group/plan9port-dev
> + Issue tracker: http://code.swtch.com/plan9port/issues/
> + Submitting changes: http://swtch.com/go/codereview
>
> * Resetting /usr/local/plan9/config
> * Compiler version:
> gcc version 3.3.5 (propolice)
> * Building mk...
> >>> pwd
> >>> pwd
> >>> pwd
> >>> pwd
> * Building everything (be patient)...
> >>> cd /usr/local/plan9/src/libdraw; mk all
> 9c openfont.c
> openfont.c:12: warning: `n' might be used uninitialized in this
> function
> >>> mk: don't know how to make
> '/usr/local/plan9/lib/libthread.a(OpenBSD-x86_64-asm.o)' in
> /usr/local/plan9/src/libthread
> mk: for i in ... : exit status=exit(1)
>
>
[-- Attachment #2: Type: text/html, Size: 1857 bytes --]
next prev parent reply other threads:[~2010-07-03 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 9:14 quiet_lad
2010-07-03 15:51 ` Alexander Sychev [this message]
2010-07-05 8:39 ` quiet_lad
[not found] ` <cff93c22-5ee0-4568-ac02-a6abf255ebe7@w31g2000yqb.googlegroups.co>
2010-07-05 14:43 ` erik quanstrom
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=AANLkTikhkC_M-hbRl4l8hm9fX-b041CllDbwiH5NAhU5@mail.gmail.com \
--to=santucco@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).