compiling Firefox/Seamonkey/Thunderbird

[Bob Melson]

Jan,
Thanks for your reply to my earlier email.  I appreciate you taking the time.
Attached is file junk.gz, which is the output from running make DISABLE_MAKE_JOBS=yes in the /usr/ports/www/firefox directory.
Lest you think me a total moron, let me hasten to say that I ordinarily DO use portmaster when upgrading ports; I learned some time back that that usually does the right thing.  That's one of the reasons I'm left scratching my head over this problem - if it's doing the right thing, then my system's screwed up or there's something not quite right in the generated makefile in /usr/ports/www/firefox/work/firefox-43.0.3.  (You may well ask why I don't just use the pkg system.  No reason, except that I prefer to roll my own for the extra customization that provides.)
Anyway, thanks again for your reply and for any insight you might be able to provide.
Bob Melson
 

      From: Jan Beich <jbeich at vfemail.net>
 To: Bob Melson <melson.r at att.net> 
Cc: gecko at FreeBSD.org
 Sent: Tuesday, December 29, 2015 1:55 PM
 Subject: Re: compiling Firefox/Seamonkey/Thunderbird
   
Bob Melson <melson.r at att.net> writes:

> /usr/ports/www/firefox/work/firefox-43.0.1/config/recurse.mk:32:
> recipe for target 'compile' failed
> gmake[3]: *** [compile] Error 2
> gmake[3]: Leaving directory
[...]

Please, post a full build log or one with DISABLE_MAKE_JOBS defined.
The actual error message is lost among other jobs that built fine.

moz.build and Makefile errors are rare, so the culprit line can often be
found by searching for "error:" (without quotes) emitted by the compiler.
The line before may indicate the command that failed.

> gmake: *** [build] Error 2

ports/200853 is unrelated. That error only happens during configure, not
build stage.

> My question, then, is what must I do to successfully compile any one
> or all of these applications?

Try using portmaster or portupgrade to build ports. It does the right
thing by upgrading dependencies first. Otherwise, debugging one's build
environment can be done via poudriere: set up a matching jail with the
same release/architecture as the host then slowly copy bits until the
port(s) breaks.

Alternatively, try comparing with logs from the package cluster. Looking
at the selected options, passed configure and compiler flags, etc. may
give you a few hints.

http://beefy2.nyi.freebsd.org/data/93amd64-default/404493/logs/firefox-43.0.1_1,1.log
http://beefy2.nyi.freebsd.org/build.html?mastername=93amd64-default&build=404493