From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gcc trouble
Date: Fri, 7 Nov 2003 11:53:38 -0500 [thread overview]
Message-ID: <E1AI9re-000Hld-7N@t40.swtch.com> (raw)
In-Reply-To: Your message of "Fri, 07 Nov 2003 10:58:41 MST." <cca5679849683ebd349860e8ac6e290c@plan9.ucalgary.ca>
> ps: does anyone know if it's possible to link together object files
> compiled with pcc and 8c?
yes. pcc is just a wrapper around 8c.
> how about gcc and 8c/pcc?
no. these object files are completely different format.
> say I want to
> write the gui for a unix program i'm porting, one option is writing
> ape libraries for draw(),
yes, this is an option.
> the other is writing native draw() code
> which links with the rest of the program. possible?
not as much, no. ape and native plan 9 c code can't
be mixed too easily since, for example, they have
different open, read, write, etc. if you got the
linking order correct (which would be a pain) then
perhaps (perhaps!) libdraw could manage to use the
ape open, but it would still need to pull in the libc
utf routines and probably others. like fork or wait.
and as soon as you touch libthread you might as well
give up. anything is possible, but this is not worth
the trouble.
another option is writing the code in native plan 9 style
and using the porting library, which does include libdraw.
next prev parent reply other threads:[~2003-11-07 16:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 16:27 cej
2003-11-07 17:58 ` mirtchov
2003-11-07 16:53 ` Russ Cox [this message]
2003-11-07 19:14 ` mirtchov
2003-11-07 19:36 ` Russ Cox
2003-11-07 19:48 ` mirtchov
2003-11-07 19:56 ` Christopher Nielsen
2003-11-07 20:47 ` ron minnich
2003-11-07 21:05 ` Christopher Nielsen
2003-11-07 21:11 ` Charles Forsyth
2003-11-07 22:34 ` mirtchov
2003-11-08 0:08 ` Latchesar Ionkov
2003-11-08 1:35 ` Russ Cox
2003-11-08 1:54 ` Latchesar Ionkov
2003-11-08 2:14 ` Russ Cox
2003-11-08 4:35 ` ron minnich
2003-11-08 4:57 ` Geoff Collyer
2003-11-08 5:05 ` ron minnich
2003-11-08 8:24 ` Charles Forsyth
2003-11-08 17:29 ` ron minnich
2003-11-10 10:01 ` Douglas A. Gwyn
2003-11-11 0:16 ` Latchesar Ionkov
2003-11-12 23:46 ` Charles Forsyth
2003-11-20 14:33 ` Latchesar Ionkov
2003-11-20 18:34 ` boyd, rounin
2003-11-20 21:14 ` Latchesar Ionkov
2003-11-20 21:27 ` boyd, rounin
2003-11-20 21:35 ` mirtchov
2003-11-20 22:45 ` Latchesar Ionkov
2003-11-21 10:02 ` Fco.J.Ballesteros
2003-11-20 19:27 ` Joel Salomon
2003-11-20 20:03 ` Peter Bosch
2003-11-20 20:49 ` Christopher Nielsen
2003-11-20 21:01 ` boyd, rounin
2003-11-20 23:11 ` Joel Salomon
2003-11-20 23:28 ` boyd, rounin
2003-11-21 0:19 ` Christopher Nielsen
2003-11-21 0:31 ` boyd, rounin
2003-11-10 15:53 ` Joel Salomon
2003-11-11 7:01 cej
2003-11-11 7:05 cej
2003-11-21 7:08 cej
2003-11-21 8:46 ` Charles Forsyth
2003-11-21 9:53 ` Skip Tavakkolian
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=E1AI9re-000Hld-7N@t40.swtch.com \
--to=rsc@swtch.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).