[SOLVED] firefox-47.0

3rensho · 06-14-2016, 07:03 AM

I'm running Slackware64-current + GCC-5.4. Firefox-45.2.0esr built fine so decided to build Firefox-47.0. The build stops with -

firefox-47.0/obj/config.cache
js/src> Refreshing /tmp/firefox-47.0/js/src/old-configure with /usr/bin/autoconf213
js/src> autoconf213: error: invalid option `--localdir=/tmp/firefox-47.0/js/src'
js/src> Try `autoconf213 --help' for more information.
js/src> Traceback (most recent call last):
js/src> File "/tmp/firefox-47.0/build/../configure.py", line 123, in <module>
js/src> sys.exit(main(sys.argv[1:]))
js/src> File "/tmp/firefox-47.0/build/../configure.py", line 114, in main
js/src> autoconf_refresh(old_configure)
js/src> File "/tmp/firefox-47.0/build/../configure.py", line 99, in autoconf_refresh
js/src> configure + '.in'], stdout=fh)
js/src> File "/usr/lib64/python2.7/subprocess.py", line 540, in check_call
js/src> raise CalledProcessError(retcode, cmd)
js/src> subprocess.CalledProcessError: Command '[u'sh', u'/usr/bin/autoconf213', u'--localdir=/tmp/firefox-47.0/js/src', u'/tmp/firefox-47.0/js/src/old-configure.in']' returned non-zero exit status 1

*** Fix above errors and then restart with\
"make -f client.mk build"

I've done a lot of searching for the above error but have yet to find a solution. When I first tried to build 47.0 it stopped with the error that it couldn't autoconf213. I created a link in /usr/bin for autoconf213 -> autoconf. That got me one step further to the above error.

Is this error arising because of the GCC version or something else?? Thanks in advance.

Keruskerfuerst · 06-14-2016, 01:29 PM

You should better stick with the ESR version.
Use google and read, what is written about the ESR version.

3rensho · 06-15-2016, 12:43 AM

Your response has no bearing on the question at hand. Nothing is ever accomplished by giving up. Anyone else have any thoughts on the error I am seeing.

Keruskerfuerst · 06-15-2016, 01:22 AM

Something with the make/configure script is wrong.

invalid option `--localdir=/tmp/firefox-47.0/js/src'

hazel · 06-15-2016, 01:24 AM

My guess is that you really do need autoconf-2.13 for this build; a symbolic link might fool the configure script but it doesn't work in make. In Crux, autoconf-2.13 is listed as a build dependency for firefox and there is a separate package that installs it alongside the later autoconf. Debian has a separate package for it too.
From the Mozilla site:

Quote:

Why doesn't Mozilla support autoconf 2.5x?

Simply put, autoconf 2.5x does not offer anything to make the upgrade worth the effort. Autoconf 2.5x is not backwards compatible with autoconf 2.13 and the additional restrictions made by the newer versions of autoconf would require a major rewrite of the Mozilla build system for questionable gain.

Some of the 2.13 features, such as the ability to pass additional arguments to sub-configures, are not available in 2.5x. People have asked repeated about those features on the autoconf mailing list without any favorable response. Rewriting the configures of the sub-projects of Mozilla (NSPR & LDAP) is not an acceptable tradeoff. The sub-projects are also standalone projects and forking an entire codebase because of a build system incompatiblity is silly.

petelq · 06-15-2016, 03:03 AM

I know some people enjoy the challenge of compiling software but with firefox I just dl the tar file and unzip it into its own folder in /usr/share. You create a symlink in /usr/bin and that's it.

3rensho · 06-15-2016, 10:09 AM

Thank you all for your suggestions/comments. I'll get autoconf-2.13 installed.

petelq · 06-15-2016, 01:54 PM

Quote:

Originally Posted by petelq

I know some people enjoy the challenge of compiling software but with firefox I just dl the tar file and unzip it into its own folder in /usr/share. You create a symlink in /usr/bin and that's it.

I didn't really think that would go down very well!

oldpink · 06-16-2016, 02:19 PM

FWIW, I installed Autoconf-2.13 and I still couldn't build this version of Firefox.
On top of that, someone must ask the obvious here: Why exactly is it that Firefox would require an old version of Autoconf, one that's actually dated June 15, 1999?
Am I missing something here, or is there some rational explanation for a sudden change between 46.0 and 47.0 that requires an Autoconf that's over sixteen years old?
The developers over at Mozilla may not have noticed it, but the current version of Autoconf is clear up at 2.69.
On top of that, installing that ancient version of Autoconf still fails for some other incomprehensible reason.

sundialsvcs · 06-16-2016, 04:23 PM

Code:

while (true) { firefox_version++; sleep(1) };

...

oldpink · 06-16-2016, 05:29 PM

Quote:

Originally Posted by sundialsvcs

Code:

while (true) { firefox_version++; sleep(1) };

...

Yes, I get it, but the fact remains that this is the first version of Firefox that I haven't been able to compile myself, a practice that I prefer to get the build optimized using options specific to my CPU.
You've got to admit it's really oddball that 46.0 builds just fine using Autoconf-2.69, then out comes 47.0 that requires Autoconf-2.13, yet still fails to build even then.

3rensho · 06-28-2016, 11:25 PM

Well, looks like they got the problem fixed with 47.0.1. Just built it (with PGO enabled) and build went without a hitch.