search for: compile_error_if_tru

....libs/guid.o > guid.c:106:2: error: array size is negative > buffer_create_from_data(&buf, guid_r, GUID_128_SIZE); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ./buffer.h:23:8: note: expanded from macro 'buffer_create_from_data' > (void)COMPILE_ERROR_IF_TRUE(__builtin_object_size((d),3) < ((s)?(s):1)); \ > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ./macros.h:161:15: note: expanded from macro 'COMPILE_ERROR_IF_TRUE' > (sizeof(char[1 - 2 * !!(condition)]) - 1) >...

http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz.sig A lot of changes since v2.2.18, so here's a release candidate first. If no bugs are reported, I'm planning on making the final release sometimes this week. The most interesting new features here are the imap-hibernate process, quota count backend and director/proxy

http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz.sig A lot of changes since v2.2.18, so here's a release candidate first. If no bugs are reported, I'm planning on making the final release sometimes this week. The most interesting new features here are the imap-hibernate process, quota count backend and director/proxy

...> guid.c:106:2: error: array size is negative >> buffer_create_from_data(&buf, guid_r, GUID_128_SIZE); >> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> ./buffer.h:23:8: note: expanded from macro 'buffer_create_from_data' >> (void)COMPILE_ERROR_IF_TRUE(__builtin_object_size((d),3) < ((s)?(s):1)); \ What happens if in src/lib/buffer.h line 23 you change the __builtin_object_size((d),3) to __builtin_object_size((d),1)? Does it work?

...2: error: array size is negative >>> buffer_create_from_data(&buf, guid_r, GUID_128_SIZE); >>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> ./buffer.h:23:8: note: expanded from macro 'buffer_create_from_data' >>> (void)COMPILE_ERROR_IF_TRUE(__builtin_object_size((d),3) < ((s)?(s):1)); \ > > What happens if in src/lib/buffer.h line 23 you change the __builtin_object_size((d),3) to __builtin_object_size((d),1)? Does it work? Yes, it works. Now dovecot-2.2.19.rc1 compiles fine. Thanks, Marcin P.S. Is such warnings something...

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

...ed-to-trash-plugin.c:2: deleted-to-trash-plugin.c:232:27: error: 'struct last_copy_info' has no member named 'mail_id' array_append(&last_copy.mail_id, &mail->uid, 1); ^ /usr/include/dovecot/macros.h:155:26: note: in definition of macro 'COMPILE_ERROR_IF_TRUE' (sizeof(char[1 - 2 * !!(condition)]) - 1) ^ /usr/include/dovecot/array.h:48:2: note: in expansion of macro 'COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE' COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE( \ ^ /usr/include/dovecot/array.h:152:33: note: in expansion of macr...