Date: Sat, 02 Nov 2002 15:13:00 +0000 From: Mark Murray <mark@grondar.org> To: Adam K Kirchhoff <adamk@voicenet.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: __sF Message-ID: <200211021513.gA2FD0d0071422@grimreaper.grondar.org> In-Reply-To: <20021102095138.U647-100000@sorrow.ashke.com> ; from Adam K Kirchhoff <adamk@voicenet.com> "Sat, 02 Nov 2002 09:56:28 EST." References: <20021102095138.U647-100000@sorrow.ashke.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> In both cases, FreeBSD doesn't seem to like __sF. This is being discussed /ad nauseam/ on the lists. If you are running CURRENT, the onus is on you to keep up with developments. :-) > Now, the first time this happened, I simply cvsuped a couple days > later and the problem went away, but now it's back, which is making me > think I never really solved the problem the first time around. > > Any ideas on how to permanently fix this problem? Rebuild _everything_. Ports, libraries, dependancies, the lot. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn 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?200211021513.gA2FD0d0071422>