linux-kernel - Detecting system includes in drivers

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>] [day] [month] [year] [list]

Message-ID: <20170720184449.GA19878@codeaurora.org>
Date:   Thu, 20 Jul 2017 11:44:49 -0700
From:   Stephen Boyd <sboyd@...eaurora.org>
To:     linux-kbuild@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org
Subject: Detecting system includes in drivers

I've run into a problem where I have a driver C file and a header
file for that driver that are in the same directory. The C file
has an include like 

    #include <driver.h>

instead of

    #include "driver.h"

and building this in tree fails, but building it out of tree with
the O= option doesn't fail. Is there anyway that building out of
tree can be made to fail as well? The difference seems to be that
we include the directory for the drivers/ path when compiling the
C file out of tree, but we don't do that when building in tree.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project