Date: Mon, 01 Apr 2002 15:07:46 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "Crist J. Clark" <cjc@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG, Emiel Kollof <coolvibe@hackerheaven.org> Subject: Re: kldxref problem Message-ID: <3CA8E842.CC6A9D18@mindspring.com> References: <20020330205329.D51062-100000@resnet.uoregon.edu> <3CA6BFE4.8296DF74@mindspring.com> <1017571105.901.4.camel@loki.ipv6.hackerheaven.org> <20020401003521.A88395@dragon.nuxi.com> <20020401111708.V99214@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Crist J. Clark" wrote: > This whole argument ignores what the real problem is. The really > correct way to handle this is to use the kldxref(8) built in the > 'buildworld' phase. (It's bad form to be using any executables from > the base system if we have a full object tree.) Actually using the one > in /usr/obj/usr/src/usr.sbin/kldxref seems pretty ugly. The better > thing to do is to have a version in /usr/obj/usr/src/<arch>/usr/sbin > by making it a crosstool. The failure should not be ignored in this > case. Uh, that doesn't work incredibly well when the machine you are on is an x86, and the machine that the buildworld targets is, say, the Alpha. This came up in the first place because it's a cross-envrionment issue that needs resolving. The "workaround" exists because the workaround cops out on the cross-environment part of the process and spits out the warnming, instead. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CA8E842.CC6A9D18>