9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9pi + apple keyboard
Date: Thu, 24 Jan 2013 10:16:22 -0500	[thread overview]
Message-ID: <cd36532e2536313e5a2e52e8bf7f0d70@brasstown.quanstro.net> (raw)
In-Reply-To: <CAJsduKmtm76vO29-nTQog_L_HRGf2=JHnmw7kN+k=Q2R5RA-kA@mail.gmail.com>

On Thu Jan 24 05:30:18 EST 2013, phineas.pett@gmail.com wrote:
> Hi,
>
> I noticed I have this same problem with man -P on the Raspberry Pi
> (though I remember that it worked initially).  What exactly did you
> recompile?  The Raspberry Pi kernel?
>
> Thanks,
> Phin
>
> On 1/23/13, erik quanstrom <quanstro@quanstro.net> wrote:
> > it appears that i shot myself in the foot with version skew with
> > the amd64-version of 5l.
> >
> > i can't really explain how that happened, but a recompile has
> > sorted things out.

i doubt this is the same thing.  it was a problem that was
entirely on the amd64 machine.  gs was aborting early in malloc.
this is what i did to fix it.

	; echo $objtype
	amd64
	; rm /sys/src/cmd/cc/*.a?
	; cd /sys/src/cmd;
	; for(i in 5[cl])@{cd $i; mk install;mk clean}
	; @{cd gs; objtype=arm mk install;mk clean}

i imagine that i simply left some junk around from before
the transition to 2mb pages.

i did have tr2post installed.

- erik



  parent reply	other threads:[~2013-01-24 15:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 10:31 James Chapman
2013-01-22 10:39 ` Richard Miller
2013-01-22 10:58   ` James Chapman
2013-01-22 17:02     ` a
2013-01-22 17:06       ` erik quanstrom
2013-01-22 17:45         ` Nicolas Bercher
2013-01-22 18:50           ` Aram Hăvărneanu
2013-01-23  7:46             ` Lyndon Nerenberg
2013-01-22 21:36           ` erik quanstrom
2013-01-23 10:36             ` Richard Miller
2013-01-23 10:55               ` Lluís Batlle i Rossell
2013-01-23 12:11                 ` Richard Miller
2013-01-23 15:45                   ` Nicolas Bercher
2013-01-23 15:48                     ` erik quanstrom
2013-01-23 21:10                       ` erik quanstrom
2013-01-23 22:21                         ` Richard Miller
2013-01-23 22:37                           ` erik quanstrom
2013-01-23 23:15                             ` Richard Miller
2013-01-23 23:33                             ` erik quanstrom
2013-01-24  1:37                               ` erik quanstrom
2013-01-24 10:29                                 ` Phineas Pett
2013-01-24 12:42                                   ` lucio
2013-01-24 13:06                                     ` Phineas Pett
2013-01-24 13:33                                       ` lucio
2013-01-24 13:40                                         ` Richard Miller
2013-01-24 14:55                                           ` lucio
2013-01-24 20:56                                             ` Steve Simon
2013-01-24 15:16                                   ` erik quanstrom [this message]
2013-01-26 11:59                         ` Lluís Batlle i Rossell
2013-01-26 12:12                           ` erik quanstrom
2013-01-26 13:18                             ` Lluís Batlle i Rossell
2013-01-23  8:05         ` Harri Haataja
2013-01-23 10:45           ` Richard Miller
2013-01-23 12:05     ` James Chapman

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=cd36532e2536313e5a2e52e8bf7f0d70@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).