Following an upgrade to Thunderbird 3.1.10 I got the following message following the breakage of Enigmail for my MUA.

I did that and got the following message from the upstream developer for Enigmail:

Okay that last part isn't going to happen (At least I'm hoping it won't have to).

Alternatively, he suggests that I may want to compile and maintain an Enigmail version myself, which I found appealing, but rather mired in versioning too.

My current gcc version is 4.4.4 on this machine, and on another it's 4.5.2 ( -current).

The two versions of Enigmail from the enigmail.net site for x86_64 were compiled with 4.4.3 (deb-squeeze) and 4.5.0 (Arch).

Okay. so now I go off into supposition and ponderance mode here...

I'm wondering what compiler was used for the Thunderbird package in Slackware64 -current, and whether I should try just installing that on my 13.1 box here (There's other reasons why I don't want to migrate my laptop to 13.37 just yet), since I keep a (current weekly ) mirror of -current locally.

Or, I can try a compile with the particular gcc that Pat used for the latest TB package for 13.1?

Or maybe, someone has this .XPI

I'm not building a Thunderbird from scratch and integrating it. I'll got back to pine and mutt for my gnupg stuff if need be, and maybe even see what clawsmail is like.

Suggestions and options anyone? I'd like this to be simple, but I'm wondering if either doing an Enigmail build based on gcc-4.5.2 or 4.4.4 and then using the SlackBuild (from 13.1 or -current) to install it, and following that up with building and generating an Enigmail .XPI is the shortest path to nirvana.

I am seeking maintainability, so perhaps the best solution would be to start (if it won't break anything) with the source for the SlackBuild from --current, build on --current, and package on this 13.1 laptop?

Y'all don't have to thank me for being as clear as mud on this one LOL!

I have TB 3.1.10 and have enigmail version 1.2.2 with no problems. Did you try to download the XPI directly from enigmail's site? I remember this happened to me quite a while back and I think I just installed a new xpi and I never saw that message again.

hm...

I'm wondering if I just build Thunderbird from

with GCC 4.5.2 (i.e., on one of my Slackware 64 -current boxes) and then check out how to create an .XPI for Enigmail using the same compiler?

Yes I d/l'd it directly from enigmail's site. And when I checked my plugins directory, I had a few Enigmails in there, the latest one prior to the update of Thunderbird actually being the same version as the one I tried to install by downloading from the developer's site (Which, by the way, turns out to the "EMO" site - enigmail.mozilla.org I think - that Olav is referring to, as opposed to the "AMO" site - addons.mozilla.org that I'm going to try now).

I can't for the life of me remember what I did last time to make it work - it's been a while.

I do remember that each time I upgrade TB, that it always turns out to be a hassle getting Enigmail working again.

I'm not bashing enigmail, because I can understand that since, what we're dealing with here is sensitive, there are additional considerations in building it that other plugins and extensions don't need to involve.

But geez.

The only official Enigmail download for Linux is built for 32-bit systems. There are a few contributed downloads for 64-bit Linux systems, but they aren't likely to work for Slackware64. Building your own is fairly easy, and that is how I do it. You don't need to build a complete Thunderbird package to replace the one installed by Slackware. Rather, only parts of Thunderbird need to be built to make an Enigmail package. This only takes a few minutes on reasonable hardware.

The instructions for building an Enigmail XPI package on this page are easy to follow. Once you've built the XPI you can install it using Thunderbird's add-on manager.

Or you can try my Enigmail builds if you'd rather not build it yourself:
Slackware64 13.1:
enigmail-1.1.2-linux-x86_64.xpi
enigmail-1.1.2-linux-x86_64.xpi.asc

Slackware64-13.37:
enigmail-1.1.2-linux-x86_64.xpi
enigmail-1.1.2-linux-x86_64.xpi.asc

The above GPG signatures are created with my GPG key here. You don't know me from any other random person on the Internet, so I understand if that doesn't mean much to you.

Either building it yourself or using my XPI should not necessitate replacing the Thunderbird package installed by Slackware.

Oh man, I just got back to this. Too bad I didn't notice it earlier.

I already make packages for Slackware64 13.37 based on the latest compiler and also for made them available in their repos.

And you're right, that with only a few posts, and not knowing you, etc., I would have been inclined to do it myself anyway, and besides, Olav asked me to.

But I see you've been thoughtfully putting stuff up since 2009 so I'll follow you and add bookmarks to your redmine site.

And I saw some other kewl, and thoughtful stuff there too.

Besides, it's always nice to meet another serious Slacker

Kindest regards,

I run Slackware 13.37 with Thunderbird 3.1.10. I downloaded and installed "enigmail-1.1.2-linux-x86_64-gcc4.4.3.xpi" and it works perfectly with this version of Thunderbird.
I guess, by looking at your error message "Thunderbird build type (Linux_x86_64-gcc3)", that you have built / are running this Thunderbird on a non-Slackware system. There is no 64bit Slackware that shipped a gcc3 compiler. Are you running Slamd64 or Bluewhite64?

Eric

Okay Eric, first off, sorry for the long, mundane post

Okay The version I was trying to install Enigmail on was mozilla-thunderbird-3.1.10-x86_64-1_slack13.1 from ftp://carroll.cac.psu.edu/pub/linux/..._slack13.1.txz (01 May 2011).

I have no idea why I got the whacky gcc 3 notification when I tried to install the Enigmail XPIs...

I saw only two that were available from the enigmail.mozdev.org site (enigmail.net). This one: http://www.mozilla-enigmail.org/down...n/octet-stream (built on Debian squeeze x86_64 with gcc-4.4.3-20100108)

And this one: http://www.mozilla-enigmail.org/down...n/octet-stream (built using Arch Linux amd64 with gcc-4.5.0)

Neither one worked for me with the Stock Slackware version I had upgraded to above, and reported the odd, gcc 3 error, in my original post.

So I just went ahead and built Thunderbird from the sources on my own mirror at ../slackware64-current/source/xap/mozilla-thunderbird/ (ran the SlackBuild on a Slackware64 -current box of mine, and then built a corresponding Enigmail from source on the same machine).

Next, I installed the resultig mozilla-thunderbird package on my 13.1 box, and installed the corresponding Enigmail plugin I had also compiled from the tools==>addons==>install menu in TB.

Runs great.

Eric, I stared at that weird gcc 3 error for a while. But that's what kept getting reported to me each time I tried to install either one of those XPI's mentioned above from the enigmail.net website (enigmail.mozdev.org).

My particular Thunderbird installation up to that point was the stock, 64/13.1, and current a/o this changelog for the 14 November 2010 security Announcement:

I did not install this thunderbird from the 09 December Announcment because, as I recall, it was such a MAJOR hassle to get Enigmail working again the previous month LOL! (Shame on me for six months - I know)

So what I did, was just added mozilla-thunderbird to /etc/slackpkg/blacklist for as long as I thought I could get away with it (until I started prep'ing my laptop for the u/g to 13.37).

Where did you get your *enigmail-1.1.2-linux-x86_64-gcc4.4.3.xpi* version? Is it the Debian Squeeze version I linked to above?

If so, I might just try upgradpkg'ing *down* to the stock thunderbird package in ftp://carroll.cac.psu.edu/pub/linux/...slack13.37.txz (Even though I think this is prolly identical to my -current build).

Then I should be running the same as you are and one step closer to getting my other apps ready for the u/g to 13.37 on this laptop

Regardless, thanks for chiming in

Kindest regards,