-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
Error running kextract: kextract file couldn't be generated #243
Comments
Hi @Yujie-Liu, thanks for reporting! I believe this is not a bug in kismet itself, but an invalid Kconfig file that prevents it from being parsed. It seems that a powerpc Kconfig file at
gives the following error:
Note the " Interestingly, this commit (a140193717ce0fcf25eaa5a3d1b9ea874b9e5114) reverts a previous commit (cea35f5ad5ffac06ea29e0d7a7f748683e1f1b7d) that fixed the recursive dependency error by removing the " There's nothing much kismet can do, since it uses Linux's own Kconfig parser, which won't process Kconfig files with recursive dependencies. Detecting it is pretty straightforward, since Linux's Kconfig tools will detect it whenever creating a configuration file, as in Would it helpful for kismet to passthrough the Kconfig error? |
@paulgazz Thanks for the detailed analysis! |
Hi @Yujie-Liu. Got it! I'll improve this error reporting. |
The text was updated successfully, but these errors were encountered: