Date: Sat, 25 Oct 2014 03:16:01 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 194490] www/firefox 33.0 does not build under poudriere Message-ID: <bug-194490-21738-ELhU1tRQQO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194490-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-194490-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194490 --- Comment #2 from Don Lewis <truckman@FreeBSD.org> --- I think this only fails on FreeBSD 8. The reason is that FreeBSD 8 does not have jemalloc in libc, so the firefox port builds its own internal copy of jemalloc, and the configure step for that fails. When I tested on FreeBSD 10, the port seems to detect the presence of jemalloc and does not attempt to build its own copy. Interestingly i386 and amd64 fail differently. On i386, bsd.port.mk sets CONFIGURE_TARGET to i386-portbld-freebsd8.4, which does not match i386-unknown-freebsd8.4, triggering a false detection of a crossbuild: configuring in memory/jemalloc/src running /bin/sh /wrkdirs/usr/ports/www/firefox/work/mozilla-release/memory/jemalloc/src/configure --build=i386-portbld-freebsd8.4 --host=i386-unknown-freebsd8.4 ... On amd64, bsd.gecko.mk overrides CONFIGURE_TARGET and sets it to x86_64-unknown-freebsd8.4, which does not match amd64-unknown-freebsd8.4, giving the same end result: configuring in memory/jemalloc/src running /bin/sh /wrkdirs/usr/ports/www/firefox/work/mozilla-release/memory/jemalloc/src/configure --build=x86_64-unknown-freebsd8.4 --host=amd64-unknown-freebsd8.4 ... -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194490-21738-ELhU1tRQQO>