From owner-freebsd-current Tue Mar 28 16:15: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 9BA5437B50F for ; Tue, 28 Mar 2000 16:15:04 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id TAA25263; Tue, 28 Mar 2000 19:48:02 -0500 (EST) (envelope-from dervish) Date: Tue, 28 Mar 2000 19:48:02 -0500 From: bush doctor To: Chris Costello Cc: freebsd-current@FreeBSD.ORG Subject: Re: Warnings when linking against libc_r Message-ID: <20000328194802.A91057@ikhala.tcimet.net> References: <20000328145345.B41117@goku.cl.msu.edu> <20000328161813.Q18325@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000328161813.Q18325@holly.calldei.com>; from chris@calldei.com on Tue, Mar 28, 2000 at 04:18:13PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 > |I/O, I/O, it's off to work we go... > `------------------------------------ > #;^) -- So ya want ta hear da roots? bush doctor 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