Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Macro MODULE depends on how file is compiled, extracted from build system #35

Open
ckaestne opened this issue Feb 3, 2015 · 0 comments
Open

Macro MODULE depends on how file is compiled, extracted from build system #35

ckaestne opened this issue Feb 3, 2015 · 0 comments
Labels
BuildSystemAnalysis

Comments

@ckaestne
Copy link
Owner

ckaestne commented Feb 3, 2015

Issue occured in security/smack/smackfs, where MODULE is handled incorrectly

incorrect handling of CONFIG_MODULES

the whole file can only be compiled in obj-y or obj-n because CONFIG_SECURITY_SMACK is a boolean option. That is, within that file MODULE can never be active.

However, currently MODULE is linked to CONFIG_MODULES and not whether the the specific file is compiled as a module or not. That would require a different extraction from the build system and different handling of the MODULE macro
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BuildSystemAnalysis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ckaestne