9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Fwd: [9fans] Re: request: native graphics on OS X
Date: Wed, 10 Jan 2007 12:03:17 -0800	[thread overview]
Message-ID: <3e1162e60701101203l61b7e6c9o1c3890edb989773c@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60701101151m38efec2do8027141a8ac4115c@mail.gmail.com>

Meant for this to go to 9fans.

---------- Forwarded message ----------
From: David Leimbach <leimy2k@gmail.com>
Date: Jan 10, 2007 11:51 AM
Subject: Re: [9fans] Re: request: native graphics on OS X
To: Skip Tavakkolian <skip@9netics.com>


On 1/10/07, David Leimbach <leimy2k@gmail.com> wrote:
> On 1/10/07, David Leimbach <leimy2k@gmail.com> wrote:
> > On 1/10/07, Skip Tavakkolian <skip@9netics.com> wrote:
> > > > ranlib: file: ../libmachdep.a(md5block.o) has no symbols
> > > > ranlib: file: ../libmachdep.a(sha1block.o) has no symbols
> > >
> > > for your machine it should have picked posix-386 as machinedep.
> > > was it able to build that library?
> > >
> > >
> >
> > It did pick the 386 directory, and produced no symbols.
> >
> > sha1block.s is an empty file, same with md5block.s
> >
> > gcc -E uses the .spp files to produce these and comes up with nothing
> > in the output.
> >
> > Dave
> >
> And the reason it has no output is because gcc on Apple thinks that
> .spp or .sp files are linker input files, which will be ignored due to
> the -E option, since linking isn't done.
>
> The following makefile change to the posix-386 directory fixes it:
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/drawterm/posix-386/Makefile,v
> retrieving revision 1.6
> diff -u -r1.6 Makefile
> --- Makefile    9 Jan 2007 22:17:21 -0000       1.6
> +++ Makefile    10 Jan 2007 19:40:37 -0000
> @@ -20,8 +20,8 @@
>         $(AS) -o $*.$O $*.s
>
>  md5block.s: md5block.spp
> -       gcc -E md5block.spp >md5block.s
> +       cat md5block.spp | gcc -E - >md5block.s
>
>  sha1block.s: sha1block.spp
> -       gcc -E sha1block.spp >sha1block.s
> +       cat sha1block.spp | gcc -E - >sha1block.s
>

Ok this patch seems to get me 100% compiled :-)  I had to replace
__Darwin__ with __APPLE__ because gcc doesn't set __Darwin__ anymore.

And even after that, it behaves just as Andrey's binary did, it just
gives me the "spinny beachball of doom" on Mac OS X that causes me to
force quit.

I suppose I'll have to break out the debug tools sometime.

>8------------------------------->8

Index: Makefile
===================================================================
RCS file: /cvs/drawterm/posix-386/Makefile,v
retrieving revision 1.6
diff -u -r1.6 Makefile
--- Makefile    9 Jan 2007 22:17:21 -0000       1.6
+++ Makefile    10 Jan 2007 19:48:58 -0000
@@ -20,8 +20,8 @@
        $(AS) -o $*.$O $*.s

 md5block.s: md5block.spp
-       gcc -E md5block.spp >md5block.s
+       cat md5block.spp | gcc -E - >md5block.s

 sha1block.s: sha1block.spp
-       gcc -E sha1block.spp >sha1block.s
+       cat sha1block.spp | gcc -E - >sha1block.s

Index: md5block.spp
===================================================================
RCS file: /cvs/drawterm/posix-386/md5block.spp,v
retrieving revision 1.2
diff -u -r1.2 md5block.spp
--- md5block.spp        9 Jan 2007 22:17:21 -0000       1.2
+++ md5block.spp        10 Jan 2007 19:48:58 -0000
@@ -116,7 +116,7 @@
        .text

        .p2align 2,0x90
-#ifdef __Darwin__
+#ifdef __APPLE__
        .globl __md5block
        __md5block:
 #else
Index: sha1block.spp
===================================================================
RCS file: /cvs/drawterm/posix-386/sha1block.spp,v
retrieving revision 1.2
diff -u -r1.2 sha1block.spp
--- sha1block.spp       9 Jan 2007 22:17:21 -0000       1.2
+++ sha1block.spp       10 Jan 2007 19:48:58 -0000
@@ -1,7 +1,7 @@
 .text

 .p2align 2,0x90
-#ifdef __Darwin__
+#ifdef __APPLE__
 .globl __sha1block
 __sha1block:
 #else

8<-----------------8<


       reply	other threads:[~2007-01-10 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3e1162e60701100853g5fdfcd3biee499db044d08c2d@mail.gmail.com>
     [not found] ` <000623fb1023a5f733c3334516192f41@9netics.com>
     [not found]   ` <3e1162e60701101131h71bbfc70oee234fc314fc0ade@mail.gmail.com>
     [not found]     ` <3e1162e60701101140y441d2d88w85dbce3611149084@mail.gmail.com>
     [not found]       ` <3e1162e60701101151m38efec2do8027141a8ac4115c@mail.gmail.com>
2007-01-10 20:03         ` David Leimbach [this message]
2007-01-11 22:43           ` andrey mirtchovski
2007-01-11 22:48             ` David Leimbach
2007-01-11 22:53               ` andrey mirtchovski
2007-01-11 22:54               ` David Leimbach

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=3e1162e60701101203l61b7e6c9o1c3890edb989773c@mail.gmail.com \
    --to=leimy2k@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).