I have no idea what this refers to or where it comes from. Any further
information you could provide would be greatly appreciated!
Thanks
On Tue, Jun 30, 2020, at 5:14 AM, Sergey wrote:
> On Monday 22 June 2020, ellie timoney wrote:
>
> > The Cyrus team is proud to announce the immediate avail
On Friday 16 October 2015, Sergey wrote:
> I wanted to build Cyrus-IMAP with libpcre but it did not success.
> System libpcre-devel package install headers to /usr/include/pcre.
I returned to this question. 3.2.2 still does not find /usr/include/pcre/pcre.h
$ pkg-config --cflags libpcre
-I/usr/
On Monday 22 June 2020, ellie timoney wrote:
> The Cyrus team is proud to announce the immediate availability of a new
> version of Cyrus IMAP: 3.2.2
Tests have issued a new warning compared to 3.0.x (building in Linux):
verify-elf: WARNING: ./usr/lib64/libcyrus.so.0.0.0: found executable STACK
On Monday 29 June 2020, ellie timoney wrote:
> If you _want_ to use the hardware CRC32c algorithm
No. I want for Cyrus-IMAP works on systems without SSE4 when it built
on system with SSE4.
> > Can Cyrus-IMAP be running on systems without SSE4 at this case?
>
> Yep, it'll work just fine. The ha
Ellie,
I also had the doubt about this feature, though I'd already seen a mention that
the result of the hw implementation is incompatible (and before your last mail
completely forgot about it).
Maybe it makes sense to remove its mention (and detection) from configure
altogether, until it beco