From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: "Brian L. Stuart" <blstuart@bellsouth.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
Alexander Kapshuk <alexander.kapshuk@gmail.com>
Subject: Re: [9fans] Inferno on Plan9
Date: Thu, 28 Dec 2017 20:28:58 +0000 [thread overview]
Message-ID: <254996213.6156537.1514492938456@mail.yahoo.com> (raw)
In-Reply-To: <254996213.6156537.1514492938456.ref@mail.yahoo.com>
Alexander Kapshuk wrote:
> On Thu, Dec 28, 2017 at 9:54 PM, Brian L. Stuart <blstuart@bellsouth.net> wrote:
>> Which version of FreeBSD did you use, and did you use the
>> Inferno on bitbucket? I'm finding it a long way from building
>> out of the box there these days.
>
> While not a FreeBSD user, the bitbucket repository is:
> grep bitbucket ~/inferno-os/.hg/hgrc
> default = https://bitbucket.org/inferno-os/inferno-os
>
> Care to elaborate a bit more on what sort of trouble you're having
> building Inferno on your system?
I'm using FreeBSD 11.1. Things have changed a little since
they switched from gcc to clang. I'm also running on an am64
install.
First, I had to rebuild mk. The supplied binary expected the
libc shared library to be named libc.6.so, but the one present
on the system is just libc.so. In doing that, I found there was
no setfcr-FreeBSD-386 source file. Copying the Linux one
made it possible to build lib9. Now I'm fighting with the floating
point stuff. None of the FPxxxx constants are found. I seem
to remember running into the same thing last year and did
eventually sort it out. The other problem then was that a
couple of the X libraries weren't part of the 32-bit support
and I could only build emu-g.
BLS
next parent reply other threads:[~2017-12-28 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <254996213.6156537.1514492938456.ref@mail.yahoo.com>
2017-12-28 20:28 ` Brian L. Stuart [this message]
[not found] <1477623683.7350613.1514746208525.ref@mail.yahoo.com>
2017-12-31 18:50 ` Brian L. Stuart
[not found] <348140488.6702383.1514581916226.ref@mail.yahoo.com>
2017-12-29 21:11 ` Brian L. Stuart
2017-12-30 11:37 ` Andre Wingor
2017-12-30 13:41 ` James A. Robinson
2017-12-30 16:59 ` Andre Wingor
2017-12-30 18:38 ` Rui Carmo
2017-12-30 19:57 ` Andre Wingor
[not found] <2051690395.6631505.1514574682474.ref@mail.yahoo.com>
2017-12-29 19:11 ` Brian L. Stuart
2017-12-29 19:14 ` Bakul Shah
[not found] <1551839886.6502293.1514557846735.ref@mail.yahoo.com>
2017-12-29 14:30 ` G B
[not found] <1100617170.6129986.1514490844113.ref@mail.yahoo.com>
2017-12-28 19:54 ` Brian L. Stuart
2017-12-28 20:11 ` Alexander Kapshuk
[not found] <1500946834.4036010.1514049193160.ref@mail.yahoo.com>
2017-12-23 17:13 ` G B
2017-12-23 17:57 ` Alexander Kapshuk
2006-05-29 19:48 [9fans] inferno on plan9 mattmobile
2006-05-29 19:39 ` quanstro
2006-05-29 22:35 ` Gabriel Ivanes
2006-05-29 22:38 ` Charles Forsyth
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=254996213.6156537.1514492938456@mail.yahoo.com \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
--cc=alexander.kapshuk@gmail.com \
/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).