From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gcc trouble
Date: Fri, 7 Nov 2003 10:58:41 -0700 [thread overview]
Message-ID: <cca5679849683ebd349860e8ac6e290c@plan9.ucalgary.ca> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D124BF7@XMAIL.asuch.cas.cz>
I was having the same problems today! funny...
when you compile with gcc make sure you link the libraries from
/386/lib/gnu/... you should have them all there.
it's a pity that the gcc port has fallen behind -- ape just
doesn't cut it for some things. i tried compiling /sys/src/gnu/ape/
today and it complained about lib9c.h, which is nowhere to be found on my
system. I hacked around it, but then ran into problems trying to find
getsockname(), even though libbsd.a was specified and was in the path
and...
so, porting links will be put on hold for another few months...
andrey
ps: does anyone know if it's possible to link together object files
compiled with pcc and 8c? how about gcc and 8c/pcc? say I want to
write the gui for a unix program i'm porting, one option is writing
ape libraries for draw(), the other is writing native draw() code
which links with the rest of the program. possible?
next prev parent reply other threads:[~2003-11-07 17:58 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 [this message]
2003-11-07 16:53 ` Russ Cox
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=cca5679849683ebd349860e8ac6e290c@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).