Re: Does this break binary compatability on 64bit architectures?
On Thu, Feb 24, 2005 at 05:53:02PM +0300, Nikita V. Youshchenko wrote:
> Upstream of a library package that I maintain changed function prototypes
> in the followinf way:
> > -int mailpop3_retr(mailpop3 * f, uint32_t index, char ** result,
> > +int mailpop3_retr(mailpop3 * f, unsigned int index, char ** result,
> > size_t * result_len);
> That is, 'uint32_t' was changed to 'unsigned int'.
> Does this break binary compatability on any of debian architectures (so
> soname change is needed)?
Afaik, on all 64 bit arches in debian an int is still 32 bit.