Which side need the issue?

Locked-chess-official · November 17, 2025, 8:43am

Under using “python_undef” to shield the macro in “pyconfig.h”, the compiling of numpy failed, due to two macros “SIZEOF_VOID_P” and “LONG_BIT” which shielded by “python_undef”:

github.com/numpy/numpy

numpy/_core/src/common/npy_hashtable.cpp

main


      
          static inline Py_hash_t
          identity_list_hash(PyObject *const *v, int len)
          {
              Py_uhash_t acc = _NpyHASH_XXPRIME_5;
              for (int i = 0; i < len; i++) {
                  /*
                   * Lane is the single item hash, which for us is the rotated pointer.
                   * Identical to the python type hash (pointers end with 0s normally).
                   */
                  size_t y = (size_t)v[i];
                  Py_uhash_t lane = (y >> 4) | (y << (8 * SIZEOF_VOID_P - 4));
                  acc += lane * _NpyHASH_XXPRIME_2;
                  acc = _NpyHASH_XXROTATE(acc);
                  acc *= _NpyHASH_XXPRIME_1;
              }
              return acc;
          }
          #undef _NpyHASH_XXPRIME_1
          #undef _NpyHASH_XXPRIME_2
          #undef _NpyHASH_XXPRIME_5
          #undef _NpyHASH_XXROTATE

github.com/numpy/numpy

numpy/_core/src/umath/string_fastsearch.h

main


      
          #if LONG_BIT >= 128
          #define STRINGLIB_BLOOM_WIDTH 128
          #elif LONG_BIT >= 64
          #define STRINGLIB_BLOOM_WIDTH 64
          #elif LONG_BIT >= 32
          #define STRINGLIB_BLOOM_WIDTH 32
          #else
          #error "LONG_BIT is smaller than 32"
          #endif

I think that the using of it should be forbidden finally, however, how to replace? If there is no way to get them now, is it needed to add the way to get them?

c-rob · November 17, 2025, 9:56am

Perhaps you could change the subject to “Compiling of numpy failed”. I think you will attract more people to your post. There’s a different edit button to the right of the subject to edit it.

What’s your OS name and version? Is it for a Raspberry Pi or something like that?
Why are you compiling numpy if there are wheels for common operating systems already? This might shed light on the puzzle.

Locked-chess-official · November 17, 2025, 10:55am

It is a special python environment: all of the macros which were defined in “pyconfig.h” and non-standard (not start with “Py”, “PY”, “_Py”, “_PY”) become just local in “Python.h” and won’t effect outside. To test the environment for PEP743, I made the package “python_undef” and test the famous python C-extern package in this environment. I list the four conditions:
0 means that the compiling still success.
1 means that the compiling failed due to that the project misuses these macros.
2 means that the compiling failed due to the environment of my OS (need to download many things).
-1 means that the compiling failed due to just the change and the project didn’t use any macros like these.

Now package “jpype1” match result 0, while “numpy” match the result 1.