9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] where does drawterm get bufimage?
@ 2009-12-30  8:40 Tom Lieber
  2009-12-31  1:23 ` kokamoto
  0 siblings, 1 reply; 3+ messages in thread
From: Tom Lieber @ 2009-12-30  8:40 UTC (permalink / raw)
  To: 9fans

Browsing the source for drawterm, I can't figure out where bufimage
(and a few others) are ever defined.

$ grep bufimage . -r
./include/draw.h:extern uchar*	bufimage(Display*, int);
./libdraw/alloc.c:	a = bufimage(d, 1+4+4+1+4+1+4*4+4*4+4);
./libdraw/alloc.c:			a = bufimage(d, 1+4);
./libdraw/alloc.c:	a = bufimage(d, 1+4+1+n);
./libdraw/alloc.c:		a = bufimage(d, 1+4);
./libdraw/alloc.c:	a = bufimage(i->display, 1+4+1+1+n);
./libdraw/alloc.c:	a = bufimage(d, 1+4);

$ find . -type f | xargs nm | grep bufim
                 U _bufimage
                 U _bufimage

gcc  -o drawterm main.o cpu.o readcons.o secstore.o latin1.o
posix-factotum.o   kern/libkern.a exportfs/libexportfs.a
libauth/libauth.a libauthsrv/libauthsrv.a libsec/libsec.a
libmp/libmp.a libmemdraw/libmemdraw.a libmemlayer/libmemlayer.a
libdraw/libdraw.a gui-osx/libgui.a libc/libc.a  kern/libkern.a
exportfs/libexportfs.a libauth/libauth.a libauthsrv/libauthsrv.a
libsec/libsec.a libmp/libmp.a libmemdraw/libmemdraw.a
libmemlayer/libmemlayer.a libdraw/libdraw.a gui-osx/libgui.a
libc/libc.a  kern/libkern.a exportfs/libexportfs.a libauth/libauth.a
libauthsrv/libauthsrv.a libsec/libsec.a libmp/libmp.a
libmemdraw/libmemdraw.a libmemlayer/libmemlayer.a libdraw/libdraw.a
gui-osx/libgui.a libc/libc.a  libmachdep.a -ggdb -framework Carbon
-framework QuickTime

That fails on OS X 10.6, but if I feed it md5block.c and sha1block.c
from posix-port/ so that it can get to the linking step, it only
complains about missing QuickTime functions (no mention of bufimage).
Carbon and QuickTime are the only external libraries that get linked,
unless I'm missing something.

--
Tom Lieber
http://AllTom.com/



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] where does drawterm get bufimage?
  2009-12-30  8:40 [9fans] where does drawterm get bufimage? Tom Lieber
@ 2009-12-31  1:23 ` kokamoto
  2009-12-31  1:34   ` David Leimbach
  0 siblings, 1 reply; 3+ messages in thread
From: kokamoto @ 2009-12-31  1:23 UTC (permalink / raw)
  To: 9fans

> gcc  -o drawterm main.o cpu.o readcons.o secstore.o latin1.o
> 
> That fails on OS X 10.6, 

You need to add -m32 option to gcc for OXS 10.6.
Oh, boy, I'm just a newbie to OSX world.☺

Kenji




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] where does drawterm get bufimage?
  2009-12-31  1:23 ` kokamoto
@ 2009-12-31  1:34   ` David Leimbach
  0 siblings, 0 replies; 3+ messages in thread
From: David Leimbach @ 2009-12-31  1:34 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

On Wed, Dec 30, 2009 at 5:23 PM, <kokamoto@hera.eonet.ne.jp> wrote:

> > gcc  -o drawterm main.o cpu.o readcons.o secstore.o latin1.o
> >
> > That fails on OS X 10.6,
>
> You need to add -m32 option to gcc for OXS 10.6.
> Oh, boy, I'm just a newbie to OSX world.☺
>
> Kenji
>
>
> Depends actually.  If you're on a 32bit Intel, I think without -m32 you're
probably ok, but it's best to be safe.

Note you don't need to be running the 64bit kernel to get the 64bit binaries
to work either.  In fact, I'm not sure I'd recommend the 64bit kernel unless
your machine boots to it on it's own.

Dave

[-- Attachment #2: Type: text/html, Size: 973 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-12-31  1:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-12-30  8:40 [9fans] where does drawterm get bufimage? Tom Lieber
2009-12-31  1:23 ` kokamoto
2009-12-31  1:34   ` David Leimbach

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).