From owner-freebsd-hackers Sun Jul 25 20:47:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from exit-gw.power.net (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 7F09814FF6 for ; Sun, 25 Jul 1999 20:47:31 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.8.8/8.8.8) with ESMTP id UAA06007 for ; Sun, 25 Jul 1999 20:38:55 -0700 (PDT) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.2/8.9.1) id UAA01435 for freebsd-hackers@freebsd.org; Sun, 25 Jul 1999 20:38:54 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <199907260338.UAA01435@realtime.exit.com> Subject: Upgrading from 2.2.8 to 3.2-stable... To: freebsd-hackers@freebsd.org Date: Sun, 25 Jul 1999 20:38:54 -0700 (PDT) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apologies if this appears twice. The first attempt didn't appear to work. Well, I'm having problems upgrading a system from 2.2.8 to 3.2-stable. I checked the archives, and apparently others have run into this one as well. Unfortunately, I couldn't find a fix for it. The problem is when the upgrade procedure tries to build the elf version of libmytinfo. It generates an executable, mkcaplist, which it uses to generate the caplist.c file. This is an elf executable, which promptly coredumps when the makefile tries to run it. Now, I _know_ this library has been around for a while, and others have successfully done a "make upgrade." My question is: What the hell am I doing wrong? I'm just doing a "make upgrade" on a clean /usr/obj. It crashes when it gets to libmytinfo. That's it. Any help or pointers would be greatly appreciated. Thanks. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message