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

[3.17] error: ‘uint32_t’ does not name a type #678

Closed
picca opened this issue Dec 31, 2023 · 2 comments · Fixed by #755
Closed

[3.17] error: ‘uint32_t’ does not name a type #678

picca opened this issue Dec 31, 2023 · 2 comments · Fixed by #755

Comments

@picca
Copy link

picca commented Dec 31, 2023

Still doing some packaging and I end up with this error

It seems that the header is missing

/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc: In function ‘unsigned int dxtbx::boost_python::cbf_decompress(const char*, std::size_t, int*, std::size_t)’:
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:122:50: warning: comparison of integer expressions of different signedness: ‘long int’ and ‘std::size_t’ {aka ‘long unsigned int’} [-Wsign-compare]
  122 |   while ((j < packed_sz) && ((values - original) < values_sz)) {
      |                              ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc: At global scope:
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:168:8: error: ‘uint32_t’ does not name a type
  168 | inline uint32_t read_uint32_from_bytearray(const char *buf) {
      |        ^~~~~~~~
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:4:1: note: ‘uint32_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
    3 | #include <assert.h>
  +++ |+#include <cstdint>
    4 | 
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:186:8: error: ‘uint16_t’ does not name a type
  186 | inline uint16_t read_uint16_from_bytearray(const char *buf) {
      |        ^~~~~~~~
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:186:8: note: ‘uint16_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc: In function ‘void dxtbx::boost_python::rod_TY6_decompress(int*, const char*, const char*, int, int)’:
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:202:26: warning: comparison of integer expressions of different signedness: ‘size_t’ {aka ‘long unsigned int’} and ‘const int’ [-Wsign-compare]
  202 |   for (size_t iy = 0; iy < slow; iy++) {
      |                       ~~~^~~~~~
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:203:72: error: ‘uint32_t’ was not declared in this scope
  203 |     size_t ipos = read_uint32_from_bytearray(buf_offsets + iy * sizeof(uint32_t));
      |                                                                        ^~~~~~~~
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:203:72: note: ‘uint32_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:203:19: error: ‘read_uint32_from_bytearray’ was not declared in this scope
  203 |     size_t ipos = read_uint32_from_bytearray(buf_offsets + iy * sizeof(uint32_t));
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/dxtbx/src/dxtbx/boost_python/compression.cc:217:31: error: ‘read_uint16_from_bytearray’ was not declared in this scope
  217 |       firstpx = (signed short)read_uint16_from_bytearray(buf_data + ipos);
      |                               ^~~~~~~~~~~~~~~~~~~~~~~~~~
@picca
Copy link
Author

picca commented Dec 31, 2023

Sorry this should be for the dxtbx project.

@picca
Copy link
Author

picca commented Jan 8, 2024

Is it possible to move it to the dxtbx issue tracker ?

@phyy-nx phyy-nx transferred this issue from cctbx/cctbx_project Jan 10, 2024
@picca picca changed the title [2023.11] error: ‘uint32_t’ does not name a type [3.17] error: ‘uint32_t’ does not name a type Jan 17, 2024
ndevenish added a commit that referenced this issue Sep 9, 2024
Something has updated in the default conda-forge installation that means
we are now hitting this.

Fixes #678.
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 a pull request may close this issue.

1 participant