Skip to content

[fio toup] Fix TMPDIR warning message in Yocto build#79

Closed
detsch wants to merge 1 commit into2025.01+fiofrom
detsch-fix-yocto-warning
Closed

[fio toup] Fix TMPDIR warning message in Yocto build#79
detsch wants to merge 1 commit into2025.01+fiofrom
detsch-fix-yocto-warning

Conversation

@detsch
Copy link
Copy Markdown
Member

@detsch detsch commented Jan 28, 2025

The output files for the asn1c tool contain an absolute path in the header comment. This path matches Yocto's TMPDIR, which should not be referenced inside source files, and lead to a warning message.

This commit removes the reference to the absolute path right after the files are generated, fixing the warning.

@detsch detsch force-pushed the detsch-fix-yocto-warning branch 4 times, most recently from 5b07b2e to 4a84b9d Compare January 28, 2025 18:35
The output files for the asn1c tool contain an absolute path in the
header comment. This path matches Yocto's TMPDIR, which should not be
referenced inside source files, and lead to a warning message.

This commit removes the reference to the absolute path right after the
files are generated, fixing the warning.

Signed-off-by: Andre Detsch <[email protected]>
@detsch detsch force-pushed the detsch-fix-yocto-warning branch from 4a84b9d to 32ee584 Compare January 28, 2025 19:02
@detsch
Copy link
Copy Markdown
Member Author

detsch commented Jan 29, 2025

This fix was not enough to prevent the warnings in an actual Yocto scarthgap build. The files are re-generated at some point and a copy of the files end up having the full absolute path inside.

Applying the fix to meta-lmp recipe seems more appropriate. I'm closing the PR in favor of foundriesio/meta-lmp#1567

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants