Archive autoconf213 (fix seamonky for this)

[thomas]

1. Only Firefox, Seamonkey and Thunderbird has a reference to autoconf213. Is it still valid that those packages needs that old version of autoconf?
   At least Firefox compiles fine if there is no autoconf213.
2. The description of autoconf213 says that FF now uses Python2 for configuration - that seems a bit outdated, too as FF does not need a P2 installation.

Can't we drop autoconf213 at all?

[Bruce Dubbs]

Good idea. Need to double check, but it is something we want to do.

[Joe Locash]

Firefox and Thunderbird build fine with out it. Seamonkey bombs in mach configure with:

 0:06.18 ERROR: Could not find autoconf 2.13

[Xi Ruoyao]

Maybe we should just archive Seamonkey as well then :).

[Bruce Dubbs]

I used to use SM and liked it, but moved to TB/FF. I think there are still uses that like SM, so I am reluctant to remove it.

[Douglas R. Reno]

I'm reluctant to remove it as well, Seamonkey works well for me and I don't have much of an issue maintaining it now that upstream has moved away from Python3. They might be working on the new autoconf changes as well

[Xi Ruoyao]

We need to wait for SeaMonkey improvement or figure out how to build SeaMonkey without it ourselves.

[Xi Ruoyao]

It looks like SeaMonkey checks for autoconf-2.13 but it does not really use it. I tried AUTOCONF=true ./mach configure and it worked, the following ./mach build and ./mach install also succeeded.

Could someone else confirm or dis-confirm my finding?

[Bruce Dubbs]

Replying to Xi Ruoyao:

It looks like SeaMonkey checks for autoconf-2.13 but it does not really use it. I tried AUTOCONF=true ./mach configure and it worked, the following ./mach build and ./mach install also succeeded.

Could someone else confirm or dis-confirm my finding?

I'll take a look, but I note that arch is still calling for autoconf-2.13.

[Bruce Dubbs]

I can confirm it builds and runs without autoconf213. To make sure I now have:

$ ls /usr/bin/*2.13*
/usr/bin/autoconf2.13.NOUSE    /usr/bin/autoreconf2.13.NOUSE  /usr/bin/autoupdate2.13.NOUSE
/usr/bin/autoheader2.13.NOUSE  /usr/bin/autoscan2.13.NOUSE    /usr/bin/ifnames2.13

I hadn't built the current version of SM, so I was surprised by the the patch and the number of sed commands. In any case I got:

27.5 Elapsed Time -  seamonkey-2.53.17.1
 
md5sum : 15c73a5e725b7f002b2789706ae643d9  /usr/src/seamonkey/seamonkey-2.53.17.1.source.tar.xz
259840 /usr/src/seamonkey/seamonkey-2.53.17.1.source.tar.xz SIZE (253.750 MB)
3063292 kilobytes BUILD SIZE (2991.496 MB)
SBU=2.977

hostname: pippin120
BFLAGS=-j24

With a test run I got a few javascript error messages on the console:

$ seamonkey https://www.linuxfromscratch.org
[calBackendLoader] Using Thunderbird's builtin libical backend
JavaScript error: resource://devtools/client/framework/gDevTools.jsm, line 150: TypeError: browser[name] is undefined
JavaScript error: resource://devtools/client/framework/browser-menus.js, line 223: TypeError: menu is null
JavaScript error: jar:file:///usr/lib/seamonkey/omni.ja!/components/devtools-startup.js, line 300: NS_ERROR_FILE_NOT_FOUND: 
Document https://www.linuxfromscratch.org/ loaded successfully
JavaScript error: resource://devtools/client/framework/gDevTools.jsm, line 150: TypeError: browser[name] is undefined
JavaScript error: resource://devtools/client/framework/devtools-browser.js, line 632: TypeError: tabContainer is undefined

The browser did seem to work OK.

With that I think we can archive autoconf2.13.

[Joe Locash]

I can also confirm that this works. Saw the same javascript runtime errors when built with autoconf213 and without.

[Xi Ruoyao]

Fixed at r12.0-630-g4e7ec17c2e.