Or to put it in another way. I am convinced that >= 2.2.13p1-1 package
has already the needed fix, since this snippet:
AC_CHECK_LIB(com_err, com_err, [
# com_err is already in library path
# guess we're okay
# can use system com_err
Hi Steve,
you didn't check enough :). The triple check was needed. The current
cyrus-imapd debian package (>= 2.2.13p1-1 and >= 2.4.6-3) runs
configure with --with-com_err="" which is different from just using
--with-com_err.
Using --with-com_err sets the value to 'yes' which makes cyrus-imapd
co
On Sun, Apr 10, 2011 at 09:49:05AM -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 10 Apr 2011, Steve Langasek wrote:
> > multiarch. The attached patch has been applied in Ubuntu for this issue,
> > correcting this call to use --with-com_err with no argument to get the
> > default search path.
On Sun, 10 Apr 2011, Steve Langasek wrote:
> multiarch. The attached patch has been applied in Ubuntu for this issue,
> correcting this call to use --with-com_err with no argument to get the
> default search path.
Has this been triple-checked to do the right thing? I used to have to
employ extre
Package: cyrus-imapd-2.2
Version: 2.2.13-19
Severity: normal
Tags: patch
User: vor...@debian.org
Usertags: multiarch
Hi folks,
The current cyrus-imapd-2.2 package fails to build from source in a
multiarch library environment, because passing --with-com_err=/usr on the
commandline results in a har
5 matches
Mail list logo