9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] frontbase
Date: Sun, 18 Feb 2024 15:37:14 -0500	[thread overview]
Message-ID: <2A4B8568-E724-466F-8BA6-6AE45DA8A770@stanleylieber.com> (raw)
In-Reply-To: <1224E13D-45C3-4C53-9A11-B6A71DC19B68@stanleylieber.com>

On February 18, 2024 3:35:52 PM EST, Stanley Lieber <sl@stanleylieber.com> wrote:
>On February 18, 2024 3:29:13 PM EST, hiro <23hiro@gmail.com> wrote:
>>and the sbase people aren't maintaining any version of this that would
>>work on bsd?
>>
>>On 2/18/24, Stanley Lieber <sl@stanleylieber.com> wrote:
>>> a bunch of years later, i've pushed minor changes to frontbase:
>>>
>>> https://code.9front.org/hg/frontbase
>>>
>>> - change default OBJTYPE to x86_64
>>> - suggest CC = egcc for openbsd (otherwise it won't build)
>>> - replace remaining mentions of "9base" with "frontbase"
>>>
>>> for those who forgot, this is our fork of the final mercurial
>>> commit of 9base. a few 9front tweaks and additions were made
>>> (circa 2016), but it hasn't been touched since then.
>>>
>>> the original intention was to have this track with 9front
>>> changes to the base tools.
>>>
>>> right now it doesn't build on openbsd with clang.
>>>
>>> patches welcome.
>>>
>>> sl
>>>
>>
>
>no clue, does that still exist?
>
>sl
>

i forgot, sbase has nothing to do with plan 9 tools.

sl

  reply	other threads:[~2024-02-18 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 17:22 Stanley Lieber
2024-02-18 20:29 ` hiro
2024-02-18 20:35   ` Stanley Lieber
2024-02-18 20:37     ` Stanley Lieber [this message]
2024-02-18 20:43       ` hiro
2024-02-18 20:47         ` Stanley Lieber

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=2A4B8568-E724-466F-8BA6-6AE45DA8A770@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /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).