From owner-freebsd-current Tue Sep 22 23:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16060 for freebsd-current-outgoing; Tue, 22 Sep 1998 23:23:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles87.castles.com [208.214.165.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16030 for ; Tue, 22 Sep 1998 23:22:54 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA00964; Tue, 22 Sep 1998 23:28:14 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809230628.XAA00964@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Terry Lambert , chuckr@mat.net, freebsd-current@FreeBSD.ORG Subject: Re: elf & compat In-reply-to: Your message of "Tue, 22 Sep 1998 21:25:16 PDT." <1235.906524716@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Sep 1998 23:28:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So a program which, when build a.out, require an a.out libgnumalloc, > > will, when built ELF, *not* require an ELF libgnumalloc? > > Uh, what? > > > How does that work? > > How does what work? :-) Terry's brain, and the answer is that it doesn't. What you're missing, Terry, is that you can't build a program that requires libgnumalloc. You can *run* one, but you can't build one. Since you can't build them, and you couldn't build them for a long time before we went ELF, you'll never want to run them (because they don't exist). Please note carefully the scope of the above discussion before indulging in a meaningless display of pedantry. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message