Date: Mon, 01 Apr 2002 18:08:40 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: cjclark@alum.mit.edu Cc: freebsd-current@FreeBSD.ORG, Emiel Kollof <coolvibe@hackerheaven.org> Subject: Re: kldxref problem Message-ID: <3CA912A8.167AFEDB@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> <3CA8E842.CC6A9D18@mindspring.com> <20020401163441.A99214@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Crist J. Clark" wrote: > > 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. > > An 'installworld' doesn't even come close to working in a cross > environment for a whole variety of reasons, so I don't see the > relevance. > > The situation this question comes up is typically 5-CURRENT builds on > 4-STABLE systems, not in cross-archetecture builds. Since this is the recommended upgrade path for going from 4.x to 5.x right now, it's an issue, if you can't cross-build 5.x on 4.x. That other things are broken doesn't really excuse this being broken. The problem is that the kldxref deserves to get its own tools build, so that there is a version that works against 5.x code that can be built on 4.x (or NetBSD or Linux or Solaris or whatever). -- 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?3CA912A8.167AFEDB>