From owner-freebsd-current Fri Sep 20 12:12:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21779 for current-outgoing; Fri, 20 Sep 1996 12:12:02 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA21752 for ; Fri, 20 Sep 1996 12:11:58 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA19881; Fri, 20 Sep 1996 12:11:59 -0700 (PDT) To: Chuck Robey cc: FreeBSD current Subject: Re: libgnumalloc In-reply-to: Your message of "Fri, 20 Sep 1996 10:18:10 EDT." Date: Fri, 20 Sep 1996 12:11:59 -0700 Message-ID: <19879.843246719@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I agree - this change just broke a whole bunch of X installations, including all of mine. I don't think that things should be left in this state. Jordan > 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! > ----------------------------+----------------------------------------------- >