9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Gregory Pavelcak <g.pavelcak@comcast.net>
Subject: Re: [9fans] Drawterm on Mac Mini w/Ubuntu Linux
Date: Tue, 17 Jan 2006 06:00:16 -0600	[thread overview]
Message-ID: <20060117120016.8733A1140EA@dexter-peak.quanstro.net> (raw)
In-Reply-To: <1137496648.11377.1.camel@localhost.localdomain>

with va_copy: e.g.:

int
fmtprint(Fmt *f, char *fmt, ...)
{
	va_list va;
	int n;

	f->flags = 0;
	f->width = 0;
	f->prec = 0;
	va_copy(va, f->args);
	va_end(f->args);
	va_start(f->args, fmt);
	n = dofmt(f, fmt);
	va_end(f->args);
	f->flags = 0;
	f->width = 0;
	f->prec = 0;
	va_copy(f->args,va);
	va_end(va);
	if(n >= 0)
		return 0;
	return n;
}

Gregory Pavelcak <g.pavelcak@comcast.net> writes

| 
| On Mon, 2006-01-16 at 20:19 -0500, Russ Cox wrote:
| > > The subject line pretty much says it. I installed Ubuntu Linux on my Mac
| > > Mini for the heck of it. I mainly use the Mini to drawterm to Plan 9.
| > > So, the question is which drawterm, assuming that there is an
| > > appropriate one, should I use? drawterm-linux and drawterm-osx both give
| > > me `cannot execute binary file'. I also downloaded the sources from
| > > Andrey's collection, but need to find out how to get mk installed on
| > > Ubuntu. Is the build likely to work? If you know that it won't, you
| > > could save me some trouble by filling me in :-)
| > 
| > Use the sources referenced by http://swtch.com/drawterm/.
| > You'll only need make.
| > 
| > Russ
| 
| Thanks for the help. I seem to be getting close.
| 
| But, how to fix this?
| 
| make[1]: Leaving directory `/home/gp/bin/drawterm/gui-x11'
| (cd libc; make)
| make[1]: Entering directory `/home/gp/bin/drawterm/libc'
| gcc -Wall -Wno-missing-braces -ggdb -I.. -I../include -I../kern -c
| -I/usr/include/X11-D_THREAD_SAFE -pthread -O2 fmtprint.c
| fmtprint.c: In function ‘fmtprint’:
| fmtprint.c:20: error: incompatible types in assignment
| fmtprint.c:27: error: incompatible types in assignment
| make[1]: *** [fmtprint.o] Error 1
| make[1]: Leaving directory `/home/gp/bin/drawterm/libc'
| make: *** [libc/libc.a] Error 2
| 
| Greg


  reply	other threads:[~2006-01-17 12:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  1:14 Gregory Pavelcak
2006-01-17  1:19 ` Russ Cox
2006-01-17 11:17   ` Gregory Pavelcak
2006-01-17 12:00     ` erik quanstrom [this message]
2006-01-17 21:11       ` Gregory Pavelcak
2006-01-17 21:40         ` Russ Cox
2006-01-17 22:08           ` Gregory Pavelcak
2006-01-17 22:13             ` Russ Cox
2006-01-17 22:28               ` Gregory Pavelcak
2006-01-17 22:55                 ` Charles Forsyth
2006-01-17 22:33         ` Skip Tavakkolian
2006-01-17 21:41           ` Gregory Pavelcak
2006-01-17 22:40           ` Skip Tavakkolian
2006-01-18  0:37           ` Sven Moritz Hallberg
2006-01-17  1:20 ` Federico G. Benavento
2006-01-17  1:22 ` andrey mirtchovski
2006-01-17  1:25 ` [9fans] " Uriel
2006-01-17  1:34   ` andrey mirtchovski
2006-01-17  1:40   ` Russ Cox
2006-01-17  7:32     ` lucio
2006-01-17  7:29   ` lucio
2006-01-17 20:40     ` Micah Stetson
2006-01-17 10:06   ` Charles Forsyth

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=20060117120016.8733A1140EA@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=g.pavelcak@comcast.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).