Re: Timo - is the v2.3.15 GCC limitation really necessarily or it's just a bug?

2021-08-01 Thread Aki Tuomi
> On 01/08/2021 23:44 Michael Orlitzky wrote: > > > On Sun, 2021-08-01 at 21:53 +0300, Mart Pirita wrote: > > > > As Docvecot does not support INC_PATH= and ignores --includedir= option, > > You can try CPPFLAGS="-I" in the future. I don't know how a > normal person would ever figure it ou

Re: Timo - is the v2.3.15 GCC limitation really necessarily or it's just a bug?

2021-08-01 Thread Michael Orlitzky
On Sun, 2021-08-01 at 21:53 +0300, Mart Pirita wrote: > > As Docvecot does not support INC_PATH= and ignores --includedir= option, You can try CPPFLAGS="-I" in the future. I don't know how a normal person would ever figure it out, but that's the "correct" way to include headers from a non-defaul

Re: Timo - is the v2.3.15 GCC limitation really necessarily or it's just a bug?

2021-08-01 Thread Mart Pirita
Hi, Update: 1) Centos 5 and 6, compiled GCC 4.8.5 and successfully built Dovecot v2.3.15. 2) RedHat based customized build, first compiled GCC 4.7.4 and with it compiled GCC 4.8.5, then added --disable-hardening to options, got new error: In file included from /usr/include/sys/wait.h:79:0,

RE: SQL Backend for IMAP METADATA Dictionary

2021-08-01 Thread Joseph D Wagner
Thanks. I had to change: username(255) NOT NULL to: username(255) NOT NULL DEFAULT '' But I confirmed it works for both /private and /shared. Thanks for all your help. I wish I could post this to the wiki. I hope this email on the mailing list archive will help people in the future. Joseph D. W

RE: SQL Backend for IMAP METADATA Dictionary

2021-08-01 Thread Aki Tuomi
Hi, I realized that the priv map entry should work for shared too. So just use pattern = $key. The username field should always be there for IMAP metadata for both shared and priv. Aki On 1 August 2021 7.10.06 UTC, Joseph D Wagner wrote: >This works for /priv: > >map { > pattern = $key > t

RE: SQL Backend for IMAP METADATA Dictionary

2021-08-01 Thread Joseph D Wagner
This works for /priv: map { pattern = $key table = attr_priv fields { attr_name = $key } username_field = username value_field = attr_value } Not sure what to do about /shared. I tried, for example, to comment out the /priv map and use just this /shared map: map { pattern = $