Skip to content

Conversation

@tomassedovic
Copy link
Contributor

Running any cargo rpg command locally fails with:

$ cargo rpg issues ./src/2025h2/
error: failed to run custom build command for `onig_sys v69.8.1`
[...] 
   cargo:warning=oniguruma/src/regparse.c: In function ‘onig_st_init_strend_table_with_size’:
  cargo:warning=oniguruma/src/regparse.c:588:5: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(st_str_end_key *, st_str_end_key *)’ [-Wincompatible-pointer-types]
  cargo:warning=  588 |     str_end_cmp,
  cargo:warning=      |     ^~~~~~~~~~~
  cargo:warning=oniguruma/src/regparse.c:588:5: note: (near initialization for ‘hashType.compare’)
  cargo:warning=oniguruma/src/regparse.c:550:1: note: ‘str_end_cmp’ declared here
  cargo:warning=  550 | str_end_cmp(st_str_end_key* x, st_str_end_key* y)
  cargo:warning=      | ^~~~~~~~~~~
  cargo:warning=oniguruma/src/regparse.c:589:5: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(st_str_end_key *)’ [-Wincompatible-pointer-types]
  cargo:warning=  589 |     str_end_hash,
  cargo:warning=      |     ^~~~~~~~~~~~
  cargo:warning=oniguruma/src/regparse.c:589:5: note: (near initialization for ‘hashType.hash’)
  cargo:warning=oniguruma/src/regparse.c:571:1: note: ‘str_end_hash’ declared here
  cargo:warning=  571 | str_end_hash(st_str_end_key* x)
  cargo:warning=      | ^~~~~~~~~~~~```
[...] lots of skipped output

Updating to the latest onig version (via cargo update onig) fixes this.

This fixes an error with onig_sys.
Copy link
Member

@lqd lqd left a comment

Choose a reason for hiding this comment

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

Thanks!

@lqd lqd merged commit 58bd737 into rust-lang:main Sep 11, 2025
2 checks passed
@tomassedovic tomassedovic deleted the update-onig branch September 11, 2025 14:44
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