Date: Mon, 1 Apr 2002 00:35:21 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Emiel Kollof <coolvibe@hackerheaven.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: kldxref problem Message-ID: <20020401003521.A88395@dragon.nuxi.com> In-Reply-To: <1017571105.901.4.camel@loki.ipv6.hackerheaven.org>; from coolvibe@hackerheaven.org on Sun, Mar 31, 2002 at 12:38:24PM %2B0200 References: <20020330205329.D51062-100000@resnet.uoregon.edu> <3CA6BFE4.8296DF74@mindspring.com> <1017571105.901.4.camel@loki.ipv6.hackerheaven.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 31, 2002 at 12:38:24PM +0200, Emiel Kollof wrote:
> On Sun, 2002-03-31 at 09:51, Terry Lambert wrote:
>
> >
> > Perhaps if the kernel printf also "ignored" the request to print
> > the little S.O.B. out, there would be less confusion...
>
> I'm still sticking to the idea that one could test for kldxref, and if
> it isn't there, don't execute it.
>
> [ -x /usr/sbin/kldxref ] && /usr/sbin/kldxref
>
> like so, which is perfectly sane bourne shell syntax, which is also used
> by BSD make.
Not really. Use:
<target>: <deps>
<tab>rule1
<tab>rule2
.if exists(/usr/sbin/kldxref)
<tab>/usr/sbin/kldxref
.endif
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?20020401003521.A88395>