From owner-freebsd-questions Sat May 16 20:26:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23068 for freebsd-questions-outgoing; Sat, 16 May 1998 20:26:33 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from grizzly.fas.com (chs0346.awod.com [208.140.97.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23059 for ; Sat, 16 May 1998 20:26:28 -0700 (PDT) (envelope-from stanb@awod.com) Message-Id: <199805170326.UAA23059@hub.freebsd.org> Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA137145578; Sat, 16 May 1998 23:26:18 -0400 Subject: Who broke the ports To: freebsd-questions@FreeBSD.ORG (Free BSD Questions list) Date: Sat, 16 May 1998 23:26:18 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just updated to the latest STABLE and wne to compile motzila from the ports collection. It complained about a tk file and sugested that I re-install tk. Made sense so I grabed the port, but I seem to be stucjk in an endless loop here. I am getting messages like: ===> tk-8.0.2 : You have an old file (/usr/lib/libtcl75.so.1.1.safe) that could cause problems for some ports to compile. Please remove it and try again. You may have to reinstall tcl from the ports tree afterwards. Please note the .safe extension, this is after I renamed this file, it still finds it! Whats going on here? -- Stan Brown stanb@netcom.com 770-996-6955 Factory Automation Systems Atlanta Ga. -- Windows 98: n. 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message