From owner-freebsd-current  Mon Oct  4 10:21:14 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 790AF14BFD
	for <current@FreeBSD.ORG>; Mon,  4 Oct 1999 10:21:08 -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 KAA06273;
	Mon, 4 Oct 1999 10:39:32 -0700 (PDT)
Date: Mon, 4 Oct 1999 10:39:32 -0700 (PDT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: new signal stuff breaks libc_r?
In-Reply-To: <37F8612A.6E4546EE@scc.nl>
Message-ID: <Pine.BSF.4.05.9910041030390.6368-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Mon, 4 Oct 1999, Marcel Moolenaar wrote:

> Alfred Perlstein wrote:
> > 
> > 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.
> 
> This isn't a problem report I can deal with. Please be very explicit.

I think it's something I may have broken somehow, but i'm not
exactly sure:

~ % cat t.c
#include <stdio.h>

int main(void) {

        printf("hello world.\n");

}

.(14:17:52)(bright@thumper)
~ % gcc -static t.c -pthread
/usr/lib/libc_r.a(uthread_sig.o): In function `_dispatch_signals':
/home/src/lib/libc_r/uthread/uthread_sig.c(.text+0xf05): undefined reference to `__sigisempty'

For some reason it looks like __inline is being defined like:

#define __inline

so that when signalvar.h is included the inlines for __sigisempty
aren't getting the "inline_ prefix and are assumed to be somewhere
else.

I asked phk about it and he's not having the problem with a recent
-current so I'll be futzing around searching for the reason this
is happening.

I just deleted my source tree and I'm going to re-check it out,
maybe something got corrupted?

-Alfred



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message