From owner-freebsd-current@FreeBSD.ORG Fri Jan 13 02:04:04 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 562CE16A41F; Fri, 13 Jan 2006 02:04:04 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CED1B43D46; Fri, 13 Jan 2006 02:04:03 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id k0D2422B045414; Thu, 12 Jan 2006 18:04:02 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id k0D242Gm045413; Thu, 12 Jan 2006 18:04:02 -0800 (PST) (envelope-from obrien) Date: Thu, 12 Jan 2006 18:04:02 -0800 From: "David O'Brien" To: soc-victor@freebsd.org Message-ID: <20060113020402.GA45246@dragon.NUXI.org> Mail-Followup-To: freebsd-current@freebsd.org, soc-victor@freebsd.org References: <49402550601120436x1228e447o21e4bf13ecf12edc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49402550601120436x1228e447o21e4bf13ecf12edc@mail.gmail.com> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2006 02:04:04 -0000 On Thu, Jan 12, 2006 at 02:36:27PM +0200, victor cruceru wrote: > Hi All, > Please find below. > > > Message: 16 > > Date: Wed, 11 Jan 2006 18:44:03 -0700 > > From: Scott Long > > Subject: Re: [head tinderbox] failure on amd64/amd64 > > > > As a safe measure, we can build and install a special PIC archive, > > > similar to libc_pic.a and libgcc_pic.a, and use it here. This is > > > all in an assumption that it's still unsafe to produce the libdisk.so. > > > > > > > > > Cheers, > > > > One way or another, please fix it. Why is bsnmp linking to libdisk > > anyways? It's an absolutely horrible library. > > > > Scott > > > Because it was my decision to use libdisk I have to answer to this question. > First, only one bsnmp module is linking to this libdisk (a module for > HOST-RESOURCES-MIB). ... > I can try to replace the usage of libdisk with something else which > will do the job of detecting the disks and the partitions in a running How does one use 'snmp_hostres'? The AMD64 world builds fine with this patch: diff -u -u -0 -r1.2 Makefile --- usr.sbin/bsnmpd/modules/snmp_hostres/Makefile 9 Jan 2006 13:01:26 -0000 1.2 +++ usr.sbin/bsnmpd/modules/snmp_hostres/Makefile 12 Jan 2006 23:20:48 -0000 @@ -72,2 +72,2 @@ -DPADD= ${LIBKVM} ${LIBDEVINFO} ${LIBM} ${LIBDISK} ${LIBMEMSTAT} -LDADD= -lkvm -ldevinfo -lm -ldisk -lmemstat +DPADD= ${LIBKVM} ${LIBDEVINFO} ${LIBM} ${LIBMEMSTAT} +LDADD= -lkvm -ldevinfo -lm -lmemstat So what would I do with 'snmp_hostres' to show me unresolved symbol errors? Can we commit this patch for now, until things are figured out? diff -u -u -0 -r1.9 Makefile --- usr.sbin/bsnmpd/modules/Makefile 9 Jan 2006 12:34:07 -0000 1.9 +++ usr.sbin/bsnmpd/modules/Makefile 13 Jan 2006 02:00:31 -0000 @@ -10 +10 @@ - snmp_hostres \ + ${_snmp_hostres} \ @@ -17,0 +18,4 @@ +.if ${MACHINE_ARCH} != "amd64" +_snmp_hostres= snmp_hostres +.endif + -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon?