linux-kernel - Prepending include paths when building out of tree modules

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: <201002231711.o1NHBl0q010699@dell2.home>
Date:	Tue, 23 Feb 2010 17:11:47 +0000
From:	"Marty Leisner" <leisner@...hester.rr.com>
To:	"Linux Kernel list" <linux-kernel@...r.kernel.org>
cc:	martyleisner@...oo.com, martin.leisner@...ox.com
Subject: Prepending include paths when building out of tree modules

I'm building thirdparty cryptography modules (which define they're own
crypto/* files, which was more fully populated in the 2.6.24-26 range and 
conflicts with headers in my thirdparty modules. 

Since I want to use my crypto/* hierarchy instead of the kernels, and
the source has

 #include "crytpo/aes.h"

I want to prepend paths to the kernel header search.

I added the -I to NOSTDINC_FLAGS and it works but:
     a) it doesn't seem right
     b) is there a better/more clear way?

Something like PREPEND_INCLUDE_PATH or something?  (I didn't see anything in gcc to get around this)

marty
~

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/