Details would be useful.

Aki

> On 27/01/2026 23:33 EET Joel Mawhorter via dovecot <[email protected]> 
> wrote:
> 
>  
> Thanks Aki and Stuart for your helpful input on this. I still was not able to 
> build the latest code from github but I'm thankful smarter people than me are 
> making progress on this.
> 
> Joel
> 
> On Wed, 21 Jan 2026 13:31:14 +0200 (EET)
> Aki Tuomi <[email protected]> wrote:
> 
> > 
> > > On 19/01/2026 22:07 EET Stuart Henderson via dovecot 
> > > <[email protected]> wrote:
> > > 
> > >  
> > > On 2026-01-18, Joel Mawhorter via dovecot <[email protected]> wrote:
> > > > I'm writing to see if anyone has had success compiling Dovecot
> > > > 2.4 on OpenBSD. I can't seem to find any documentation that lists
> > > > prerequisites. At the moment, the 2.4.2 source tarball from the Dovecot
> > > > site does not seem to compile on my OpenBSD 7.8 system and the error
> > > > message is not very helpful. I'm unsure if this is just a problem of
> > > > some required package not being installed. If anyone could point me to
> > > > info to help move forward, I would appreciate that.
> > > 
> > > Even if the error message is not helpful to you, somebody else might be
> > > able to make more of it.
> > > 
> > > Some of the problems seen in 2.4.2 on openbsd:
> > > 
> > > - building test-regex fails, it expects "pkg-config --libs libpcre2-32"
> > > to return just libraries but on OpenBSD there's also -L/usr/local/lib
> > > 
> > 
> > Hi!
> > 
> > I testbuilt dovecot on openbsd 7.7, and was able to fix some of the issues. 
> > I didn't run into the test-regex problem though. Please see
> > 
> > https://github.com/dovecot/core/compare/f8dcc0ddbf8772f89d4bb3650a95aa98ab3b0907%5E...1c6b67195d279836d94e141215c626c20af93af6.patch
> > 
> > Aki
> > 
> 
> _______________________________________________
> dovecot mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to