Date: Mon, 18 May 1998 14:52:00 -0700 From: Jahan <jahan@pc.jaring.my> To: freebsd-current@FreeBSD.ORG Subject: Re: Undefined symbol "___error" Message-ID: <3560AD80.BF17AA1B@pc.jaring.my> References: <199805122155.QAA04191@unix.tfs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Look, no one is pushing us for using FreeBSD.If we use, its our problem or benefit. I WANNA STRESS THIS POINT TO MAINTNERS. Plz HAVE PROPER DOCUMNET ON HOW TO UPGRADE FROM FreeBSD x.x.x to FreeBSD x.x.x We are users ( me alone ?) really having problem upgrading. I have mentioned earlier.I had problem compiling from one point of cvsupped files. I mailed the problem here. We ( me alone ?) do not want to spoon fed too, but guideline. Even some faq's are not listed in faq ( telnet, ip accounting, lpr, increasing swap space,sound card). Plz do something about that. I will prefer better document than better fency new version of OS. Jim Bryant wrote: > In reply: > > Jim Bryant <jbryant@unix.tfs.net> writes: > > > this has got to be one of the most damnned inconvenient changes i > > > have ever seen freebsd take... > > > > So who forced you to run current? If you don't like this, stick to stable. > > > > > does this mean that ALL third party programs that use curses MUST be > > > recompiled?!?!?! > > > > Recompiled, no. Relinked, yes. > > > > > just because, as i understand it, they didn't want to bump the lib > > > version numbers?!?!?! > > > > <URL:http://www.freebsd.org/handbook/handbook285.html#615>; > > > > > does anyone realize how much this change breaks????!!!! > > > > Again, this is -current. If you can't stand the heat, stay out of the > > kitchen. > > > > BTW, are your ? and ! keys stuck?????!?!?!??!!!! > > 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. > > jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3560AD80.BF17AA1B>