9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John Floren" <slawmaster@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] getting drawterm on macos and x86
Date: Sun,  5 Nov 2006 20:53:17 -0500	[thread overview]
Message-ID: <7d3530220611051753s6f3a8e3amba2f9b02c70614ed@mail.gmail.com> (raw)
In-Reply-To: <13426df10611051725q7870a39dob29ef6bbe1689091@mail.gmail.com>

Sorry, I'm probably reading this wrong... but this stuff makes it look
like drawterm has audio compatibility. Can somebody clear this up for
me?

Thanks

John

On 11/5/06, ron minnich <rminnich@gmail.com> wrote:
> here is what it took for:
> maya-gokhales-computer:~/src/drawterm maya$ uname -a
> Darwin maya-gokhales-computer.local 8.8.1 Darwin Kernel Version 8.8.1: Mon
> Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 i386 i386
> maya-gokhales-computer:~/src/drawterm maya$ gcc -v -v
> Using built-in specs.
> Target: i686-apple-darwin8
> Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure
> --disable-checking -enable-werror --prefix=/usr --mandir=/share/man
> --enable-languages=c,objc,c++,obj-c++
> --program-transform-name=/^[cg][^.-]*$/s/$/- 4.0/
> --with-gxx-include-dir=/include/c++/4.0.0
> --with-slibdir=/usr/lib --build=powerpc-apple-darwin8 --with-arch=nocona
> --with-tune=generic --program-prefix= --host=i686-apple-darwin8
> --target=i686-apple-darwin8
> Thread model: posix
> gcc version 4.0.1 (Apple Computer, Inc. build 5367)
>
> Summary: no audio. They keep screwing with concatentation in cpp. The rules
> on gas pseudo ops keep changing.
>
> other than that it's fine, i.e. it is working for me.
>
> ron
>
> diff -r drawterm/Make.unix drawterm.hacked/Make.unix
> 16,17c16,17
> < # AUDIO=none
> < AUDIO=unix
> ---
> >  AUDIO=none
> > #AUDIO=unix
> diff -r drawterm/posix-386/md5block.spp drawterm.hacked
> /posix-386/md5block.spp
> 46c46,47
> < #define PAYME(x) $ ## x
> ---
> > //#define PAYME(x) $ ## x
> > #define PAYME(x) $  x
> 120c121,122
> <               .type _md5block, @function
> ---
> > //            .type _md5block, @function
> >       .globl  _md5block
> 121a124,125
> >       .globl  __md5block
> >       __md5block:
> diff -r drawterm/posix-386/sha1block.spp
> drawterm.hacked/posix-386/sha1block.spp
> 3a4
> > //    .type _sha1block, @function
> 5d5
> <       .type _sha1block, @function
> 6a7,8
> > .globl __sha1block
> > __sha1block:
>
>


--
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn


  reply	other threads:[~2006-11-06  1:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  1:25 ron minnich
2006-11-06  1:53 ` John Floren [this message]
2006-11-06 13:30 ` erik quanstrom
2006-11-06 16:52 ` David Leimbach
2006-11-06 17:04   ` ron minnich
2006-11-06 17:24     ` David Leimbach
2006-11-06 20:27       ` ron minnich
2006-11-06 20:31         ` David Leimbach
2006-11-06 20:36           ` David Leimbach
2006-11-06 20:41             ` David Leimbach
2006-11-06 20:47             ` ron minnich
2006-11-06 21:06               ` Steve Simon
2006-11-06 21:30                 ` David Leimbach
2006-11-06 21:43                 ` ron minnich

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=7d3530220611051753s6f3a8e3amba2f9b02c70614ed@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).