linux-kernel - Re: cifs: Fix tracing build error with O=

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190620133616.dajrd37b73k3v3kx@gondor.apana.org.au>
Date:   Thu, 20 Jun 2019 21:36:16 +0800
From:   Herbert Xu <herbert@...dor.apana.org.au>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     stfrench@...rosoft.com, linux-cifs@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>
Subject: Re: cifs: Fix tracing build error with O=

On Thu, Jun 20, 2019 at 09:56:53PM +0900, Masahiro Yamada wrote:
>
> > But it doesn't work with O=:
> >
> > $ rm -rf build-compile/fs/cifs
> > $ make O=build-compile fs/cifs
> > make[1]: Entering directory '/home/herbert/src/build/kernel/test/build-compile'
> > make[1]: Nothing to be done for '../fs/cifs'.
> > make[1]: Leaving directory '/home/herbert/src/build/kernel/test/build-compile'
> > $
> 
> You missed the trailing slash.
> 
> I suggested 'fs/cifs/' instead of 'fs/cifs'

Aha, that indeed works.  Thanks!
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt