Date: Wed, 22 Nov 2017 17:23:16 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Mathieu Demers <math_demers@yahoo.fr> Cc: gecko@freebsd.org, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: Building bug report Message-ID: <CAN6yY1sNWmW8=604uHEyNWZJEnMMqxbpRX%2BP-5B4QDxRnQdJaA@mail.gmail.com> In-Reply-To: <ef78f769-9651-98e7-8c68-d4c79516403e@yahoo.fr> References: <ef78f769-9651-98e7-8c68-d4c79516403e@yahoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 21, 2017 at 6:15 PM, Mathieu Demers via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hi, > > I have tried to build Firefox57 for 3 days but I had always the same error > when it is building. > > There are the infos: > > FreeBSD Laptop-Mathieu 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri > Jul 21 02:08:28 UTC 2017 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > /usr/ports/www/firefox/Makefile: > $FreeBSD: head/www/firefox/Makefile 454194 2017-11-14 19:04:44Z > jbeich $ > > The error building: > > gmake[3]: Leaving directory '/usr/ports/www/firefox/work/firefox-57.0' > gmake[2]: *** [/usr/ports/www/firefox/work/firefox-57.0/client.mk:237: > profiledbuild] Error 2 > gmake[2]: Leaving directory '/usr/ports/www/firefox/work/firefox-57.0' > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/www/firefox > *** Error code 1 > > Stop. > make: stopped in /usr/ports/www/firefox > > ===>>> make build failed for www/firefox > ===>>> Aborting update > > ===>>> Update for www/firefox failed > ===>>> Aborting update > Did you build with "MAKE_JOBS_UNSAFE=yes" as suggested? This will put the actual error at the end of the output. Without that, it is pretty impossible to troubleshoot. t very least we need he full error which, with "MAKE_JOBS_UNSAFE=yes" defined, should be immediately before the tiny snippet you provided. Please include, at very least, the output from the compile, link, or whatever triggered the error. Also, what non-standard configuration options do you have? "make showconfig" will print this out. A full log that is publicly accessible is best, but should be put in a publicly accessible place as it will likely be too large for a mail message. Finally, is there a reason not to use the binary package? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sNWmW8=604uHEyNWZJEnMMqxbpRX%2BP-5B4QDxRnQdJaA>