From owner-freebsd-current Tue May 12 17:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04433 for freebsd-current-outgoing; Tue, 12 May 1998 17:23:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04417 for ; Tue, 12 May 1998 17:23:48 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id RAA06810; Tue, 12 May 1998 17:27:02 -0700 (PDT) From: Steve Kargl Message-Id: <199805130027.RAA06810@troutmask.apl.washington.edu> Subject: Re: Undefined symbol "___error" In-Reply-To: <199805122155.QAA04191@unix.tfs.net> from Jim Bryant at "May 12, 98 04:55:33 pm" To: jbryant@unix.tfs.net Date: Tue, 12 May 1998 17:27:02 -0700 (PDT) Cc: dag-erli@ifi.uio.no, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jim Bryant: > In reply: > > i understand the meaning of -current... even the one that says some > idiotic change could bring down 60% of the apps ever written for > FreeBSD. that is why such changes are made in -current. if such > changes ever made it to -release, then watch how fast people split the > fold and go to openbsd, or even linux for fear that anything they > write will have to be re-released with the very next version of > -release. > > i'll submit a diff tonight/tomorrow that will satisfy the requirements > for the call without even relinking the target; a do-nothing stub that > should have been factored in when the original __error was removed. > Before you go to the trouble of making a diff, you might want check the CVS repository for the reason for the breakage: ******* 1.10 Thu Apr 30 9:38:03 1998 UTC by jb CVS Tags: HEAD Diffs to 1.9 Make errno finally and permanently thread-aware so that it is no longer necessary to compile with _THREAD_SAFE defined. This means that people will get thread-aware code whether they like it or not. This change is required to allow a process to link against libpthread and libc to use kernel threads (and prevent each thread from clobbering another thread's errno just [by] doing a syscall). This is bound to break some ports, but it is strictly allowed by ANSI C, so anything that breaks as a result was already broken anyway 8-). "Sorry". ******* Your diff will be a step backwards. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message