9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] libbsd: incompatible type signatures
Date: Tue, 27 Aug 2013 08:21:18 +0200	[thread overview]
Message-ID: <20130827082118.030f986e@Krypton> (raw)
In-Reply-To: <616d0b615941a8bfed2f54f9ec82888f@brasstown.quanstro.net>

On Mon, 26 Aug 2013 23:32:00 -0400
erik quanstrom <quanstro@quanstro.net> wrote:

> On Tue Aug 20 03:21:29 EDT 2013, staal1978@gmail.com wrote:
> > On Mon, 19 Aug 2013 13:04:26 -0400
> > erik quanstrom <quanstro@quanstro.net> wrote:
> >
> > > it looks like 9atom doesn't do this properly.  i'll submit
> > > a 9atom patch, but simply adding it to /sys/src/ape/lib/9/libc.h
> > > doesn't work, so give me a bit.  it's a rats' nest of defines...
> > >
> > > the sloppy way to get this done would be to add
> > > -Dbind=_BIND to draw's mkfile.
> > >
> > > - erik
> > >
> >
> > Will the 9atom patch normally apply cleanly to vanilla Plan9? (I run
> > vanilla Plan9 under kvm/qemu) - alternatively, is there a way to
> > "switch repositories" and "update" to 9atom to get the improvements
> > from within an existing install?
>
> in this case /n/atom/patch/applied/lib9bindconst will apply cleanly to
> either.  this should be the normal case.
>
> - erik
>

sorry if I have missed the obvious: how/where do I mount /n/atom ?

(btw: tried to install 9atom under qemu and failed (the plan9 bootloader
would not give the CD as boot option) - is this a known problem? )



  reply	other threads:[~2013-08-27  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 15:17 Jens Staal
2013-08-19 15:30 ` lucio
2013-08-19 16:28   ` Jens Staal
2013-08-19 17:04 ` erik quanstrom
2013-08-20  7:17   ` Jens Staal
2013-08-27  3:32     ` erik quanstrom
2013-08-27  6:21       ` Jens Staal [this message]
2013-08-27 12:29         ` 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=20130827082118.030f986e@Krypton \
    --to=staal1978@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).