From owner-freebsd-current Sun Oct 3 23:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BB4FB15210; Sun, 3 Oct 1999 23:16:35 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id XAA20216; Sun, 3 Oct 1999 23:35:06 -0700 (PDT) Date: Sun, 3 Oct 1999 23:35:06 -0700 (PDT) From: Alfred Perlstein To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: new signal stuff breaks libc_r? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the signal changes... I'm finding that it _seems_ since libc_r isn't including something that properly defines __inline to inline that i'm getting unresolved symbols when linking or running programs that depend on libc_r. Anyone else getting this? compiling a void main(void){} with -pthread will barf for me, using -static I'm able to see which files are missing which inlines. thanks, -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message