From: Roderick <hruodr@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Plan 9 from User Space still mantained?
Date: Thu, 20 Jun 2024 12:51:44 +0000 [thread overview]
Message-ID: <CABdqxFdOj40k_dbE-ZGJ9=48Wr3tEwxTeO20nzZ5=QX=6P_k2w@mail.gmail.com> (raw)
Dear Sirs!
I hope, I can also ask here about Plan9 port ...
I just compiled master from on FreeBSD14.0:
https://9fans.github.io/plan9port/
Is this actual? I got some warnings, bellow the messages.
I have another question, and ask first to forgive me for it ...
You know, one trusts nvi and emacs because they are so old,
because there are so much people using it. I am sure one
can trust acme and sam on plan9. But what about sam on
FreeBSD from the port? Is it reliable or should I consider it
experimental? Could it spoil a big file?
Thanks
Rodrigo
---------
#uname -a
FreeBSD fbsd.local 14.0-RELEASE-p6 FreeBSD 14.0-RELEASE-p6 #0:
Tue Mar 26 20:26:20 UTC 2024
root@amd64-builder.daemonology.net:
/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
# ./INSTALL
+ Mailing list: https://groups.google.com/group/plan9port-dev
+ Issue tracker: https://github.com/9fans/plan9port/issues/
+ Submitting changes: https://github.com/9fans/plan9port/pulls
* Resetting /usr/opt/plan9/config
* Running on FreeBSD, adjusting linker flags
* Compiler version:
FreeBSD clang version 16.0.6
(https://github.com/llvm/llvm-project.git
llvmorg-16.0.6-0-g7cbf1a259152)
* Building mk...
>>> pwd
>>> pwd
>>> pwd
>>> pwd
* Building everything (be patient)...
>>> cd /usr/opt/plan9/src/lib9p; mk all
9c -pthread req.c
req.c:63:2: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
req.c:61:1: note: previous statement is here
req.c:75:2: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
req.c:72:1: note: previous statement is here
req.c:109:2: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
req.c:107:1: note: previous statement is here
>>> cd /usr/opt/plan9/src/lib9p; mk all
9c -pthread srv.c
srv.c:104:2: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
srv.c:98:1: note: previous statement is here
srv.c:804:2: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
srv.c:801:1: note: previous statement is here
>>> cd /usr/opt/plan9/src/libmemlayer; mk all
9c -pthread draw.c
draw.c:68:3: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
draw.c:67:1: note: previous statement is here
draw.c:79:3: warning: misleading indentation; statement is not part of
the previous 'if' [-Wmisleading-indentation]
draw.c:78:1: note: previous statement is here
>>> cd /usr/opt/plan9/src/libsunrpc; mk all
9c -pthread server.c
server.c:95:3: warning: misleading indentation; statement is not part
of the previous 'if' [-Wmisleading-indentation]
server.c:94:1: note: previous statement is here
>>> cd /usr/opt/plan9/src/cmd/fossil; mk all
9c -pthread check.c
check.c:298:4: warning: misleading indentation; statement is not part
of the previous 'if' [-Wmisleading-indentation]
check.c:296:1: note: previous statement is here
check.c:604:3: warning: misleading indentation; statement is not part
of the previous 'if' [-Wmisleading-indentation]
check.c:602:1: note: previous statement is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG client.c
client.c:16:1: note: conflicting prototype is here
client.c:39:1: note: conflicting prototype is here
client.c:61:1: note: conflicting prototype is here
client.c:121:1: note: conflicting prototype is here
client.c:139:1: note: conflicting prototype is here
client.c:181:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG error.c
error.c:14:1: note: conflicting prototype is here
error.c:23:1: note: conflicting prototype is here
error.c:51:1: note: conflicting prototype is here
error.c:86:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG event.c
event.c:15:1: note: conflicting prototype is here
event.c:115:1: note: conflicting prototype is here
event.c:186:1: note: conflicting prototype is here
event.c:233:1: note: conflicting prototype is here
event.c:259:1: note: conflicting prototype is here
event.c:265:1: note: conflicting prototype is here
event.c:287:1: note: conflicting prototype is here
event.c:311:1: note: conflicting prototype is here
event.c:354:1: note: conflicting prototype is here
event.c:381:1: note: conflicting prototype is here
event.c:436:1: note: conflicting prototype is here
event.c:473:1: note: conflicting prototype is here
event.c:487:1: note: conflicting prototype is here
event.c:506:1: note: conflicting prototype is here
event.c:517:1: note: conflicting prototype is here
event.c:534:1: note: conflicting prototype is here
event.c:597:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG grab.c
grab.c:61:1: note: conflicting prototype is here
grab.c:181:1: note: conflicting prototype is here
grab.c:599:1: note: conflicting prototype is here
grab.c:626:1: note: conflicting prototype is here
grab.c:646:1: note: conflicting prototype is here
grab.c:661:1: note: conflicting prototype is here
grab.c:672:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG key.c
key.c:44:1: note: conflicting prototype is here
key.c:56:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG main.c
main.c:244:1: note: conflicting prototype is here
main.c:403:1: note: conflicting prototype is here
main.c:429:1: note: conflicting prototype is here
main.c:456:1: note: conflicting prototype is here
main.c:480:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG manage.c
manage.c:21:1: note: conflicting prototype is here
manage.c:201:1: note: conflicting prototype is here
manage.c:230:1: note: conflicting prototype is here
manage.c:242:1: note: conflicting prototype is here
manage.c:265:1: note: conflicting prototype is here
manage.c:289:1: note: conflicting prototype is here
manage.c:295:1: note: conflicting prototype is here
manage.c:344:1: note: conflicting prototype is here
manage.c:365:1: note: conflicting prototype is here
manage.c:380:1: note: conflicting prototype is here
manage.c:397:1: note: conflicting prototype is here
manage.c:419:1: note: conflicting prototype is here
manage.c:425:1: note: conflicting prototype is here
manage.c:431:1: note: conflicting prototype is here
manage.c:444:1: note: conflicting prototype is here
manage.c:457:1: note: conflicting prototype is here
>>> cd /usr/opt/plan9/src/cmd/rio; mk all
9c -pthread -I/usr/local/include -DDEBUG -DSHAPE -DDEBUG_EV -DDEBUG menu.c
menu.c:84:1: note: conflicting prototype is here
menu.c:187:1: note: conflicting prototype is here
menu.c:224:1: note: conflicting prototype is here
menu.c:246:1: note: conflicting prototype is here
menu.c:260:1: note: conflicting prototype is here
menu.c:271:1: note: conflicting prototype is here
menu.c:298:1: note: conflicting prototype is here
menu.c:332:1: note: conflicting prototype is here
menu.c:346:1: note: conflicting prototype is here
menu.c:363:1: note: conflicting prototype is here
menu.c:371:1: note: conflicting prototype is here
menu.c:406:1: note: conflicting prototype is here
menu.c:423:1: note: conflicting prototype is here
* Installing everything in /usr/opt/plan9/bin...
* Cleaning up...
* Renaming hard-coded /usr/local/plan9 paths...
* Building web manual...
* Done.
* Add these to your profile environment.
PLAN9=/usr/opt/plan9 export PLAN9
PATH=$PATH:$PLAN9/bin export PATH
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td33e0e0d414a8bb7-M42cdd7ec4a2380a5534136d6
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2024-06-20 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 12:51 Roderick [this message]
2024-06-20 13:30 ` [9fans] " wb.kloke
2024-06-20 14:59 ` [9fans] " dexen deVries
2024-06-21 8:06 ` wb.kloke
2024-06-21 9:47 ` hruodr
2024-06-21 11:36 ` wb.kloke
2024-06-23 13:22 ` wb.kloke
2024-06-21 9:39 ` David Arnold
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='CABdqxFdOj40k_dbE-ZGJ9=48Wr3tEwxTeO20nzZ5=QX=6P_k2w@mail.gmail.com' \
--to=hruodr@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).