From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P in C++
Date: Mon, 15 Dec 2008 21:31:07 -0500 [thread overview]
Message-ID: <856A9289-A66E-4042-883B-E4D7383F3BF6@mac.com> (raw)
In-Reply-To: <140e7ec30812151816l69ee7e9dla0279d4cd39eaa71@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1011 bytes --]
On Dec 15, 2008, at 9:16 PM, sqweek wrote:
> On Tue, Dec 16, 2008 at 8:34 AM, Pietro Gagliardi <pietro10@mac.com>
> wrote:
>> On Dec 15, 2008, at 6:25 PM, Rodolfo kix Garcia wrote:
>>> gcc -L /usr/local/plan9/lib -L. -ltry -lthread demo1.C -o demo1
>>> ## OK!
>>
>> I think linking lthread will give you POSIX threads and that -L
>> appends to
>> the list, rather than going before, so /usr/lib will be searched
>> before
>> plan9ports. Try explicitly setting the path of the -l argument. Does
>> -l/usr/local/plan9/lib/libthread.so (or whatever it is) help?
>
> You can't use -l with a full path, but you can simply specify the
> full path of the library:
> gcc -o demo1 demo1.C /usr/local/plan9/lib/libthread.a
> Note that the order of the objects on the command-line is as usual
> important.
> -sqweek
>
Ah yes, something I forgot while drifting through the hordes of gcc
madness that is... not using gcc. Thanks for refreshing my memory. Now
to see if this is working for kix.
[-- Attachment #1.2: Type: text/html, Size: 1584 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2008-12-16 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 15:45 Rodolfo kix García
2008-12-15 16:56 ` sqweek
2008-12-15 16:59 ` Iruata Souza
2008-12-15 21:13 ` Pietro Gagliardi
2008-12-15 23:25 ` Rodolfo kix Garcia
2008-12-15 23:34 ` Pietro Gagliardi
2008-12-16 2:16 ` sqweek
2008-12-16 2:31 ` Pietro Gagliardi [this message]
2008-12-13 21:18 ` kix
2008-12-17 22:14 ` Rodolfo kix Garcia
2008-12-18 7:16 ` sqweek
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=856A9289-A66E-4042-883B-E4D7383F3BF6@mac.com \
--to=pietro10@mac.com \
--cc=9fans@9fans.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).