From owner-freebsd-alpha Mon Dec 10 2:41:34 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.baerum.kommune.no (mail.baerum.kommune.no [195.134.40.62]) by hub.freebsd.org (Postfix) with SMTP id 98F9237B416 for ; Mon, 10 Dec 2001 02:41:31 -0800 (PST) Received: from SA-D01-Message_Server by mail.baerum.kommune.no with Novell_GroupWise; Mon, 10 Dec 2001 11:41:14 +0100 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Mon, 10 Dec 2001 11:40:46 +0100 From: "Idar Tollefsen" To: Cc: Subject: Re: Undefined references in libc_r Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> I'm running 4.4-STABLE on an ev56 (21164A/164LX). >>=20 >> After having a lot of trouble with different ports failing >> configuration and build, I've tracked down the problem to >> be libc_r. >>=20 >> An example is glib-1.2.10. It fails configuration >> with this message: >> libc_r: undefined reference: _sys_thread_sigreturn >>=20 >> Other ports have similar problems, but with different undefined >> references (such as pthread_create, e.g.). >>=20 >> I've tried to delete /usr/src/lib/libc_r and cvsup it again, >> but it didn't help. > You also need to update libc source as the fix is there. I'll remove /usr/src/lib/libc and get it again then. I don't see how that will make any difference tough. If there was a fix in there, or any other activity, I should catch it trough a normal cvsup, shouldn't I? Or are you implying that someone managed to check in a file without changing it's version number? - IT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message