Date: Fri, 13 Jan 2006 13:12:17 +0200 From: victor cruceru <victor.cruceru@gmail.com> To: freebsd-current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 Message-ID: <49402550601130312y24253976x107542f5ff4fdad3@mail.gmail.com> In-Reply-To: <20060113020402.GA45246@dragon.NUXI.org> References: <49402550601120436x1228e447o21e4bf13ecf12edc@mail.gmail.com> <20060113020402.GA45246@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi David,
Thank you for looking into this issue.
Also many thanks for the fix you submitted for amd64.
I'll try these days to replace this usage of libdisk with libgeom.
Please find below.
On 1/13/06, David O'Brien <obrien@freebsd.org> wrote:
> 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 <scottl@samsco.org>
> > > 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 ques=
tion.
> > 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 p=
atch:
>
> 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=3D ${LIBKVM} ${LIBDEVINFO} ${LIBM} ${LIBDISK} ${LIBMEMSTAT}
> -LDADD=3D -lkvm -ldevinfo -lm -ldisk -lmemstat
> +DPADD=3D ${LIBKVM} ${LIBDEVINFO} ${LIBM} ${LIBMEMSTAT}
> +LDADD=3D -lkvm -ldevinfo -lm -lmemstat
>
> So what would I do with 'snmp_hostres' to show me unresolved symbol error=
s?
For sure Harti will have a better explanation but I can try to respond
to this question.
The shared lib produced from this directory is used by the bsnmpd
agent to be loaded at runtime. When this shared lib is loaded we will
see the undefined symbols. One way to control when this so is loaded
is via the agent config file (usually located in /etc).
>
> 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} !=3D "amd64"
> +_snmp_hostres=3D 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?
>
--
victor cruceru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49402550601130312y24253976x107542f5ff4fdad3>