Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 169714 - mail-client/claws-mail-2.8.1 configure fails on libetpan
Summary: mail-client/claws-mail-2.8.1 configure fails on libetpan
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
: 185391 (view as bug list)
Depends on:
Reported: 2007-03-07 07:48 UTC by Togge
Modified: 2007-07-15 10:37 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

config.log (config.log,135.50 KB, text/plain)
2007-03-07 07:50 UTC, Togge

Note You need to log in before you can comment on or make changes to this bug.
Description Togge 2007-03-07 07:48:17 UTC
When emerging mail-client/claws-mail-2.8.1 I get this:
checking whether libetpan-config hints compiles and links fine... no
*** Claws Mail requires libetpan 0.48 or newer. See 
*** You can use --disable-libetpan if you don't need IMAP4 support.
configure: error: libetpan 0.48 not found

!!! Please attach the following file when filing a report to
!!! /var/tmp/portage/mail-client/claws-mail-2.8.1/work/claws-mail-2.8.1/config.log

Missing dep?

Reproducible: Always
Comment 1 Togge 2007-03-07 07:50:22 UTC
Created attachment 112366 [details]
Comment 2 Togge 2007-03-07 07:53:21 UTC
Seems I was wrong... libetpan-0.49 is installed.

eix libetpan
[I] net-libs/libetpan
     Available versions:  0.42 (~)0.43 0.45 (~)0.46 (~)0.46-r1 (~)0.47 0.48 (~)0.49
     Installed versions:  0.49(11.44.40 2007-01-09)(berkdb -debug -gnutls ipv6 -sasl ssl)
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2007-03-07 09:25:01 UTC
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -ldb-4.3

Re-emerge libetpan and try again...
Comment 4 Togge 2007-03-07 12:52:50 UTC
That did it, Thanks!

P.s. Wonder why revdep-rebuild missed that? D.s.
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2007-07-15 10:37:56 UTC
*** Bug 185391 has been marked as a duplicate of this bug. ***