From owner-freebsd-current Fri Sep 20 07:18:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA25345 for current-outgoing; Fri, 20 Sep 1996 07:18:17 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA25322 for ; Fri, 20 Sep 1996 07:18:14 -0700 (PDT) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id KAA04354 for ; Fri, 20 Sep 1996 10:18:11 -0400 (EDT) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) with SMTP id KAA14109 for ; Fri, 20 Sep 1996 10:18:10 -0400 (EDT) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Fri, 20 Sep 1996 10:18:10 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: FreeBSD current Subject: libgnumalloc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I saw that the recent changes to the compiler and libs deleted libgnumalloc. This means a lot of currently working ports binaries are scragged, as well as the packages behind them. I got important stuff working again by linking libfakegnumalloc to libgnumalloc, but each make world clears that back out. Sure means lots of finding and recompiling. Is it necessary to delete the old libgnumalloc? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+-----------------------------------------------