Date: Tue, 28 Mar 2000 19:48:02 -0500 From: bush doctor <dervish@ikhala.tcimet.net> To: Chris Costello <chris@calldei.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Warnings when linking against libc_r Message-ID: <20000328194802.A91057@ikhala.tcimet.net> In-Reply-To: <20000328161813.Q18325@holly.calldei.com>; from chris@calldei.com on Tue, Mar 28, 2000 at 04:18:13PM -0600 References: <20000328145345.B41117@goku.cl.msu.edu> <20000328161813.Q18325@holly.calldei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Out of da blue Chris Costello aka (chris@calldei.com) said:
> On Tuesday, March 28, 2000, Bush Doctor wrote:
> > I'm seeing the following diagnostics with applications linked against libc_r
> ...
>
> Do not directly link with libc_r. Instead, use the -pthread
> gcc flag. It will properly compile and link your program with
> the correct thread bits.
Thanxs Chris. If this was discussed on -current, I apologise for missing the
discussion. :( A question why can we not link directly with libc_r? If this was
discussed on -current I can look it up in the archives. Looks like gnats will
be seeing some send-pr's about this. Thanxs again!
>
> --
> |Chris Costello <chris@calldei.com>
> |I/O, I/O, it's off to work we go...
> `------------------------------------
>
#;^)
--
So ya want ta hear da roots?
bush doctor <dervish@ikhala.tcimet.net>
Of course I run FreeBSD!!
http://www.freebsd.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000328194802.A91057>