Re: Need help with incompatible pointer types on i686

2024-02-21 Thread Orion Poplawski
On 2/16/24 16:58, Orion Poplawski wrote: On 2/16/24 01:29, Michael J Gruber wrote: Am Fr., 16. Feb. 2024 um 07:15 Uhr schrieb Elliott Sales de Andrade : On Thu, Feb 15, 2024 at 11:39 PM Orion Poplawski wrote: We're hitting this with h5py on i686:

Re: Need help with incompatible pointer types on i686

2024-02-17 Thread Kevin Kofler via devel
Michael J Gruber wrote: > numpy definitely needs to fix this. You cannot just go by bitsize and > signedness. You never could and now you can't ;) You actually had to before C99, where stdint.h was introduced. On some platforms or compilers, such as MSVC, you still cannot use C99, only C89/C90.

Re: Need help with incompatible pointer types on i686

2024-02-16 Thread Orion Poplawski
On 2/16/24 01:29, Michael J Gruber wrote: Am Fr., 16. Feb. 2024 um 07:15 Uhr schrieb Elliott Sales de Andrade : On Thu, Feb 15, 2024 at 11:39 PM Orion Poplawski wrote: We're hitting this with h5py on i686: /builddir/build/BUILD/h5py-3.10.0/serial/h5py/defs.c: In function

Re: Need help with incompatible pointer types on i686

2024-02-16 Thread Sérgio Basto
On Fri, 2024-02-16 at 14:01 +0100, Florian Weimer wrote: > * Orion Poplawski: > > > It seems that numpy is defining a uint32_t type as long unsigned > > int > > on i686, while glibc(?) is defining it as unsigned int.  Now what > > puzzles me a little is that on i686 aren't these both 4-byte > >

Re: Need help with incompatible pointer types on i686

2024-02-16 Thread Florian Weimer
* Orion Poplawski: > It seems that numpy is defining a uint32_t type as long unsigned int > on i686, while glibc(?) is defining it as unsigned int. Now what > puzzles me a little is that on i686 aren't these both 4-byte integers > and no not incompatible at all? The types int and long are

Re: Need help with incompatible pointer types on i686

2024-02-16 Thread Michael J Gruber
Am Fr., 16. Feb. 2024 um 07:15 Uhr schrieb Elliott Sales de Andrade : > > On Thu, Feb 15, 2024 at 11:39 PM Orion Poplawski wrote: > > > > We're hitting this with h5py on i686: > > > > /builddir/build/BUILD/h5py-3.10.0/serial/h5py/defs.c: In function > > ‘__pyx_f_4h5py_4defs_H5Dread_chunk’: > >

Re: Need help with incompatible pointer types on i686

2024-02-15 Thread Elliott Sales de Andrade
On Thu, Feb 15, 2024 at 11:39 PM Orion Poplawski wrote: > > We're hitting this with h5py on i686: > > /builddir/build/BUILD/h5py-3.10.0/serial/h5py/defs.c: In function > ‘__pyx_f_4h5py_4defs_H5Dread_chunk’: > /builddir/build/BUILD/h5py-3.10.0/serial/h5py/defs.c:14922:85: error: > passing argument

Need help with incompatible pointer types on i686

2024-02-15 Thread Orion Poplawski
We're hitting this with h5py on i686: /builddir/build/BUILD/h5py-3.10.0/serial/h5py/defs.c: In function ‘__pyx_f_4h5py_4defs_H5Dread_chunk’: /builddir/build/BUILD/h5py-3.10.0/serial/h5py/defs.c:14922:85: error: passing argument 4 of ‘H5Dread_chunk’ from incompatible pointer type