From owner-freebsd-current Sun Apr 4 16:10:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 10BA614CE1 for ; Sun, 4 Apr 1999 16:10:09 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA25141; Sun, 4 Apr 1999 19:07:31 -0400 (EDT) Date: Sun, 4 Apr 1999 19:07:31 -0400 (EDT) From: Daniel Eischen Message-Id: <199904042307.TAA25141@pcnet1.pcnet.com> To: kushn@mail.kar.net, obrien@NUXI.com Subject: Re: 4.0-CURRENT world broken Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vladimir Kushnir wrote: > On Sun, 4 Apr 1999, David O'Brien wrote: > > > > The FreeBSD 4.0-CURRENT world appears to be broken. The file that > > > appears to be causing the problem is pthread_private.h, included by > > > isatty.c. > > > > > > You're the only one reporting this problem. Possibly your /usr/obj isn't > > clean? > > > > No, I had the same breakage awhile ago. It comes from old headers > /usr/src/lib/libc_r/uthread/pthread{.h,_np.h} (don't remember where they > come from, but they were there and conflicted with the correct headers > from /usr/src/include). > Removing of those headers has fixed everything Possibly from LinuxThreads changes? You've got to remember that if you make any local modifications to the source tree, things are liable to break. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message