[Users] [Bug 3673] Be more friendly instead of "configure: error: 'encrypt'-function not found."

[Perry E. Metzger]

Replying very late (as I was not paying attention to the issue for
some weeks...)

On Thu, 8 Dec 2016 08:52:56 +0100 wwp <subscript at free.fr> wrote:
> Hello Perry,
> On Wed, 7 Dec 2016 16:50:31 -0500 "Perry E. Metzger"
> <perry at piermont.com> wrote:
> 
> > On Wed, 7 Dec 2016 09:45:48 +0000 Paul <claws at thewildbeast.co.uk>
> > wrote:  
> > > Hi Perry,
> > > 
> > > Then it must be this commit:
> > > 
> > > http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=abbf2f8a104fcb5e72226a2edf0ecd1cd5d29b93
> > > 
> > > Try reverting that.    
> > 
> > It still failed. I expected it would, as this is OS X, not
> > FreeBSD, and that line should only alter things if we're running
> > FreeBSD.
> > 
> > On a hunch, though, I added |*darwin* to the case statement, and
> > it got past the encrypt error only to blow up when it claimed that
> > libetpan isn't present. (It is present, and everything worked fine
> > under 3.14.0...)
> > 
> > Ideas here? Is adding "|*darwin*" to the case the right thing? (I
> > have no idea what this library call it is looking for is even
> > for.) Ideas on how to fix the libetpan failure? The errors are
> > here.
> > 
> > ] checking whether to use libetpan... yes
> > ] checking for libetpan-config... /opt/local/bin/libetpan-config
> > ] checking libetpan/libetpan.h usability... yes
> > ] checking libetpan/libetpan.h presence... yes
> > ] checking for libetpan/libetpan.h... yes
> > ] checking whether libetpan-config hints compiles and links
> > fine... no ] *** Claws Mail requires libetpan 0.57 or newer. See
> > http://www.etpan.org/ ] *** You can use --disable-libetpan if you
> > don't need IMAP4 and/or NNTP support. ] configure: error:
> > libetpan 0.57 not found  
> 
> I'd be curious to know if 3.14.0 still builds fine on your system!

It builds just fine. Remember, this isn't just my system, but all
MacPorts users -- I'm the MacPorts maintainer for claws.

And I still have no idea why 3.14.1 won't build under MacPorts (or on
the Mac). It makes no sense to me.


Perry
-- 
Perry E. Metzger		perry at piermont.com