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.

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

aktualizr: fix build error 'uint8_t' does not name a type [V2] #102

Merged
merged 1 commit into from
Jul 14, 2023

Conversation

DengkeDu
Copy link

My environment:
meta-updater: master branch [c10f9f]
yocto poky: master branch [303421]
ARCH: arm64

When I take :
bitbake aktualizr

Output error said :
uint8_t does not name a type

Add the header file cstdint to asn1-cer.h to fix it.

My environment:
meta-updater: master branch [c10f9f]
yocto poky: master branch [303421]
ARCH: arm64

When I take :
    bitbake aktualizr

Output error said :
    uint8_t does not name a type

Add the header file cstdint to asn1-cer.h to fix it.

Signed-off-by: dudengke <[email protected]>
@pattivacek
Copy link
Collaborator

Hello, just FYI for future reference, you don't need to close the MR and create a new one every time to just make a new change. In fact, it's much easier to follow the history if you continue to reuse the same one and just force push to the same branch.

@DengkeDu
Copy link
Author

Hello, just FYI for future reference, you don't need to close the MR and create a new one every time to just make a new change. In fact, it's much easier to follow the history if you continue to reuse the same one and just force push to the same branch.

Thanks for advice : force push, I will follow it future.

Copy link
Collaborator

@pattivacek pattivacek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, looks good, thanks! The shellcheck complaint is fixed by my MR so it's not a blocker.

@pattivacek pattivacek merged commit b2ee72e into uptane:master Jul 14, 2023
4 of 5 checks passed
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