Configure error during port upgrade

2015-02-28 Thread Rob Belics
I've had this problem since trying to upgrade to version 35, I think, and except for showing this a month ago, haven't had a chance to look into it. Here is the output trying to upgrade Firefox using portmaster. I also tried uninstalling Firefox and reinstalling to no avail: Installing setuptools,

[package - 84amd64-default][www/firefox-esr] Failed for firefox-esr-31.4.0_2, 1 in stage

2015-02-28 Thread pkg-fallout
You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: ge...@freebsd.org Last committer: jbe...@freebsd.org Ident: $FreeBSD: head/www/firefox-esr/Makefile

[package - 84amd64-default][www/libxul] Failed for libxul-31.4.0_2 in stage

2015-02-28 Thread pkg-fallout
You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: ge...@freebsd.org Last committer: jbe...@freebsd.org Ident: $FreeBSD: head/www/libxul/Makefile 3785

[Bug 198090] www/firefox: 36 - build fail

2015-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198090 Jan Beich changed: What|Removed |Added Status|New |Closed CC|

[Bug 198090] www/firefox: 36 - build fail

2015-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198090 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: jbeich Date: Sat Feb 28 13:54:14 UTC 2015 New revision: 380142 URL: https://svnweb.freebsd.org/changeset/ports/380142 Log: Unbreak build when LOGGING o

FreeBSD Port: www/firefox (36)

2015-02-28 Thread Holger Schröder
Firefox 36 not build :( http://pastebin.de/53993 ... ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"

maintainer-feedback requested: [Bug 198090] www/firefox: 36 - build fail

2015-02-28 Thread bugzilla-noreply
rozhuk...@gmail.com has reassigned Bugzilla Automation 's request for maintainer-feedback to ge...@freebsd.org: Bug 198090: www/firefox: 36 - build fail https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198090 --- Description --- Looks like: https://bugzilla.mozilla.org/show_bug.cgi?id=1128161

[Bug 198090] www/firefox: 36 - build fail

2015-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198090 Bug ID: 198090 Summary: www/firefox: 36 - build fail Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects M

Re: Compiling Firefox 36.0 fails on 10.1-RELEASE/amd64

2015-02-28 Thread Piotr Kubaj
On 02/28/15 11:29, Matthew D. Fuller wrote: > On Sat, Feb 28, 2015 at 10:51:13AM +0100 I heard the voice of > Jan Beich, and lo! it spake thus: >> >> Did you set any options? I cannot reproduce with default build in >> poudriere jail for 10.1R amd64. > > I get the same failure on -CURRENT. A litt

Re: Compiling Firefox 36.0 fails on 10.1-RELEASE/amd64

2015-02-28 Thread Matthew D. Fuller
On Sat, Feb 28, 2015 at 10:51:13AM +0100 I heard the voice of Jan Beich, and lo! it spake thus: > > Did you set any options? I cannot reproduce with default build in > poudriere jail for 10.1R amd64. I get the same failure on -CURRENT. A little fiddling with showconfig suggests my non-default op

Re: Compiling Firefox 36.0 fails on 10.1-RELEASE/amd64

2015-02-28 Thread Jan Beich
Piotr Kubaj writes: > ../../dom/media/mediasource/Unified_cpp_media_mediasource0.o: In > function > `mozilla::MediaSourceReader::GetMozDebugReaderData(nsAString_internal&)': > /usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.1/dom/media/mediasource/Unified_cpp_media_medias

FreeBSD ports you maintain which are out of date

2015-02-28 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you