Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 143519 - mail-mta/exim-4.62 cannot find -ltasn1, missing dev-libs/libtasn1 dependency
Summary: mail-mta/exim-4.62 cannot find -ltasn1, missing dev-libs/libtasn1 dependency
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Colin Morey (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-10 18:26 UTC by Zac Medico
Modified: 2007-04-15 20:43 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zac Medico gentoo-dev 2006-08-10 18:26:02 UTC
It seems that RDEPEND="gnutls? ( dev-libs/libtasn1 )" needs to be added to the dependencies of exim-4.62.  When building with USE="X gnutls ipv6 ldap pam perl sasl sqlite ssl -dnsdb -exiscan -exiscan-acl -lmtp -mailwrapper -mbx -mysql -nis -postgres -spf -srs -syslog -tcpd" I received the following error which went away after I installed libtasn1-0.2.18:

gcc -o exim
/usr/lib/gcc/i586-pc-linux-gnu/4.1.1/../../../../i586-pc-linux-gnu/bin/ld: cannot find -ltasn1
collect2: ld returned 1 exit status
make[1]: *** [exim] Error 1
make[1]: Leaving directory `/mnt/storage/local/var/tmp/portage/exim-4.62/work/exim-4.62/build-exim-gentoo'
make: *** [go] Error 2

!!! ERROR: mail-mta/exim-4.62 failed.
Call stack:
  ebuild.sh, line 1543:   Called dyn_compile
  ebuild.sh, line 938:   Called src_compile
  exim-4.62.ebuild, line 216:   Called die
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-03-13 23:09:20 UTC
CCing QA, I've had enough... Stop re-assigning the bugs to yourself only to keep ignoring them for ages.
Comment 2 Christian Faulhammer (RETIRED) gentoo-dev 2007-04-07 16:10:12 UTC
Fixed.
Comment 3 Colin Morey (RETIRED) gentoo-dev 2007-04-14 16:58:36 UTC
(In reply to comment #2)
> Fixed.
> 

Opfer: please read the Metadata for an ebuild before touching that ebuild. I believe this commit goes against good gentoo etiquette.
Comment 4 Charlie Shepherd (RETIRED) gentoo-dev 2007-04-14 17:19:48 UTC
(In reply to comment #3)
> Opfer: please read the Metadata for an ebuild before touching that ebuild. I
> believe this commit goes against good gentoo etiquette.

I thought the whole point of the recent discussions on -dev, the Coc and the Proctors, were, in essence, to try and get people to be less territorial about their packages.

Comment 5 Colin Morey (RETIRED) gentoo-dev 2007-04-14 17:51:42 UTC
> I thought the whole point of the recent discussions on -dev, the Coc and the
> Proctors, were, in essence, to try and get people to be less territorial about
> their packages.
> 

-dev is too noisy to read. and if you could provide references for the others i'd appreciate it. 

(I don't object to the work opfer: the fix is good thanks, but i'd have preferred it if you'd have spoken to me first.)
Comment 6 Jakub Moc (RETIRED) gentoo-dev 2007-04-14 21:31:31 UTC
(In reply to comment #3)
> Opfer: please read the Metadata for an ebuild before touching that ebuild. I
> believe this commit goes against good gentoo etiquette.

I believe leaving broken junk in the tree is against good developer etiquette. Stop moaning already, you had months to damn fix this yourself, you just didn't care.


Comment 7 Christian Faulhammer (RETIRED) gentoo-dev 2007-04-15 20:43:17 UTC
(In reply to comment #5)
> (I don't object to the work opfer: the fix is good thanks, but i'd have
> preferred it if you'd have spoken to me first.)

 It happened during a bug day, and as it was trivial (no objections raised here in the bug), I felt so free to change the ebuild.  Normally I send out a notification afterwards, but in this case you reveived the mail about it through Bugzilla.