From owner-freebsd-current Tue May 12 11:25:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24950 for freebsd-current-outgoing; Tue, 12 May 1998 11:25:10 -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 LAA24940 for ; Tue, 12 May 1998 11:25:06 -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 LAA03211; Tue, 12 May 1998 11:28:20 -0700 (PDT) From: Steve Kargl Message-Id: <199805121828.LAA03211@troutmask.apl.washington.edu> Subject: Re: Undefined symbol "___error" In-Reply-To: <199805121547.KAA03044@unix.tfs.net> from Jim Bryant at "May 12, 98 10:47:03 am" To: jbryant@unix.tfs.net Date: Tue, 12 May 1998 11:28:20 -0700 (PDT) Cc: ben@stuyts.nl, 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: >>> has this problem been fixed? >> >> The only solution is to recompile less. From what I understand there has >> been an incompatible change in libc, and no version no increase of the >> shared lib. >> >> After I recompiled trafshow, it ran fine. > > this has got to be one of the most damnned inconvenient changes i > have ever seen freebsd take... > > does this mean that ALL third party programs that use curses MUST be > recompiled?!?!?! The answer is probably "yes". > just because, as i understand it, they didn't want to bump the lib > version numbers?!?!?! The version number can be bumped once per release, and that bump will probably occur sometime prior to the release of FreeBSD-3.0. > > does anyone realize how much this change breaks????!!!! > Does someone know the meaning of "-current"? If someone isn't prepared to recompile seemingly broken apps, then don't run -current. If 3rd party software is critical, then run an official release of FreeBSD or the -stable branch. See the handbook at http://www.freebsd.org about who should be running -current. -- 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