From owner-freebsd-questions Tue Jul 28 12:59:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00401 for freebsd-questions-outgoing; Tue, 28 Jul 1998 12:59:03 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00256 for ; Tue, 28 Jul 1998 12:58:18 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id MAA06554; Tue, 28 Jul 1998 12:57:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Jul 1998 12:57:05 -0700 (PDT) From: Doug White To: Alex Osokin cc: freebsd-questions@FreeBSD.ORG Subject: Re: sendmail 8.9.1 build problem: ld: -lbind: no match In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998, Alex Osokin wrote: > Re, > > Just trying to build sendmail 8.9.1 and got: > > # sh Build > Configuration: os=FreeBSD, rel=2.2.7-STABLE, rbase=2, rroot=2.2, > arch=i386, sfx= > Making in obj.FreeBSD.2.2.7-STABLE.i386 > cc -o sendmail alias.o arpadate.o clock.o collect.o conf.o convtime.o > daemon.o deliver.o domain.o envelope.o err.o headers.o macro.o main.o > map.o mci.o mime.o parseaddr.o queue.o readcf.o recipient.o safefile.o > savemail.o snprintf.o srvrsmtp.o stab.o stats.o sysexits.o trace.o udb.o > usersmtp.o util.o version.o -lbind -lutil > ld: -lbind: no match > *** Error code 1 > > Does anybody know where to check whats missing? Some libriary? It wants the nameserver resolver library, which we have integrated into libc. Remove -lbind from the CFLAGS list. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message