From owner-freebsd-ports Tue Oct 2 17:35:23 2001 Delivered-To: freebsd-ports@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id AD9C837B403 for ; Tue, 2 Oct 2001 17:35:20 -0700 (PDT) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA26372 for ports@FreeBSD.org; Tue, 2 Oct 2001 17:23:06 -0700 (MST) (envelope-from chad) Date: Tue, 2 Oct 2001 17:23:06 -0700 From: "Chad R. Larson" To: ports@FreeBSD.org Subject: bzip2 make breakage Message-ID: <20011002172306.A26342@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I had to make the following edit to get bzip2 to build on my 2.2.8-STABLE system. It doesn't look to me like this is an O/S version issue, however. We were passing the name of the shared object being built to the linker as an option. Can't work, doesn't exist yet. And wouldn't make much sense even if it did. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** -patch-aa Tue Oct 2 17:10:46 2001 --- patch-aa Tue Oct 2 17:11:32 2001 *************** *** 40,46 **** fi +libbz2.so.1: $(SO_OBJS) ! + $(CC) -shared -Wl,-soname -Wl,libbz2.so.1 -o libbz2.so.1 $(SO_OBJS) + ln -sf libbz2.so.1 libbz2.so + test: bzip2 --- 40,46 ---- fi +libbz2.so.1: $(SO_OBJS) ! + $(CC) -shared -Wl,-soname -o libbz2.so.1 $(SO_OBJS) + ln -sf libbz2.so.1 libbz2.so + test: bzip2 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message