From owner-freebsd-ports Mon Jan 10 8: 7:35 2000 Delivered-To: freebsd-ports@freebsd.org Received: from sawmill.grauel.com (sawmill.grauel.com [199.233.104.39]) by hub.freebsd.org (Postfix) with ESMTP id 7AD7414C98 for ; Mon, 10 Jan 2000 08:07:32 -0800 (PST) (envelope-from rjk@sawmill.grauel.com) Received: (from rjk@localhost) by sawmill.grauel.com (8.9.3/8.8.8) id LAA02277; Mon, 10 Jan 2000 11:08:39 -0500 (EST) (envelope-from rjk) From: "Richard J. Kuhns" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14458.1031.343602.739791@sawmill.grauel.com> Date: Mon, 10 Jan 2000 11:08:39 -0500 (EST) To: freebsd-ports@freebsd.org Subject: Hint for anyone going from 2.2.x to 3.x/4.x X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently upgraded a couple of machines from 2.2.8 to 3.3/3.4. As time permitted I also rebuilt a number of ports, since the default object format is now ELF, and I found a couple of ports that compiled just fine on 1 system, but failed on another (Imlib was one). All dependencies were found with no trouble; it just didn't work. After some searching, I found the problem: libtool. Even though I had the most recent installed (1.3.3) and it doesn't include any binaries that would be affected by the a.out --> elf change, you've got to remove/reinstall it. It hard-codes the os version it was installed under, and then passes that to other ports that use it. For imlib, this caused an attempt to link in /usr/lib/c++rt0.o, which is not present under 3.x. To summarize: if you installed libtool while running 2.2.x, and you upgrade to 3.x/4.x, remove libtool and reinstall it. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message