From owner-freebsd-current Sat Nov 7 09:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19323 for freebsd-current-outgoing; Sat, 7 Nov 1998 09:44:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19318 for ; Sat, 7 Nov 1998 09:44:05 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA21951; Sat, 7 Nov 1998 09:42:23 -0800 (PST) (envelope-from jdp) Message-Id: <199811071742.JAA21951@austin.polstra.com> To: dwhite@resnet.uoregon.edu Subject: Re: What is wrong? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: "Alexander B. Povolotsky" , current@FreeBSD.ORG Date: Sat, 07 Nov 1998 09:42:23 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug White wrote: > On Fri, 6 Nov 1998, Alexander B. Povolotsky wrote: > > > attempt to run cvsup (extracted from ports/net/cvsup-binary) leads to > > > > ELF interpreter /usr/libexec/ld-elf.so.1 not found > > > > What can be wrong? > > The cvsup binary you extracted is in ELF format and your systemhasn't been > transitioned to ELF yet. Grab a new -CURRENT and run 'make aout-to-elf' > to update yourself. Hrm, Alexander, are you sure you grabbed the "cvsup-bin" port? (You said "cvsup-binary, but there is no port with that name.) The executable in the "cvsup-bin" port is statically linked, and it's also a.out. I wouldn't expect the problems you reported, if you used that port. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message