From owner-freebsd-ports Tue Sep 8 18:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21605 for freebsd-ports-outgoing; Tue, 8 Sep 1998 18:02:50 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21600 for ; Tue, 8 Sep 1998 18:02:49 -0700 (PDT) (envelope-from brian@smarter.than.nu) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with SMTP id SAA00425; Tue, 8 Sep 1998 18:03:17 -0700 (PDT) (envelope-from brian@smarter.than.nu) Date: Tue, 8 Sep 1998 18:03:17 -0700 (PDT) From: "Brian W. Buchanan" To: Chuck Robey cc: freebsd-ports@FreeBSD.ORG Subject: Re: Problem building ssh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 8 Sep 1998, Chuck Robey wrote: > > I nuked the libc in /usr/lib. Port compiles fine now. Thanks. > > Just be careful ... what with moving FreeBSD-current from aout to elf, > what you described doing ranges from smart to very dangerous. You have > to be aware of the new rules (if you were working elf, and you nuked the > libc in /usr/lib, you just destroyed your main elf libc!) I'm still using aout. I think I know better than to go about nuking the main copy of essential sharedlibs. ;) -- Brian Buchanan brian@smarter.than.nu Never believe that you know the whole story. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message