950505 - Build content/media/wmf in unified mode

Status: RESOLVED FIXED

(Core :: Audio/Video, defect)

Comment 1

[(no longer active)]

Attachment: Build content/media/wmf in unified mode

Comment 2

[(no longer active)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/1566a2e95c3b

Comment 3

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

Backed out:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e353c1d40586

This caused my local Windows build to fail because many of the source files #define LOG which causes duplicate macro warnings which get treated as errors with ac_add_options --enable-warnings-as-errors. Apparently our Windows builders don't have ac_add_options --enable-warnings-as-errors, so this showed up only locally.

Comment 4

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/1566a2e95c3b

Comment 5

[(no longer active)]

(In reply to Brian Smith (:briansmith, was :bsmith; Please NEEDINFO? me if you want a response) from comment #3)
> Backed out:
> https://hg.mozilla.org/integration/mozilla-inbound/rev/e353c1d40586
> 
> This caused my local Windows build to fail because many of the source files
> #define LOG which causes duplicate macro warnings which get treated as
> errors with ac_add_options --enable-warnings-as-errors. Apparently our
> Windows builders don't have ac_add_options --enable-warnings-as-errors, so
> this showed up only locally.

It would be nice if you at least provided a build log when backing out something that has not turned our builds red, especially since that your premise is not correct:

http://mxr.mozilla.org/mozilla-central/source/browser/config/mozconfigs/win32/debug#20
http://mxr.mozilla.org/mozilla-central/source/browser/config/mozconfigs/win32/common-opt#28

Comment 6

[(no longer active)]

Also helpful would be your compiler version, your mozconfig, etc, because I can't reproduce your problem.

Comment 7

[(no longer active)]

FWIW I'm planning to reland these patches later today, I've done local debug and opt builds and cannot reproduce your problem.

Comment 8

[Carsten Book [:Tomcat]]

backout changeset was included in m-c https://tbpl.mozilla.org/?rev=832ef0e8771e

Comment 9

[(no longer active)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/ac40b01fd56b

Comment 10

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

Attachment: .mozconfig

Comment 11

[(no longer active)]

(In reply to comment #10)
> Created attachment 8348216 [details]
>   --> https://bugzilla.mozilla.org/attachment.cgi?id=8348216&action=edit
> .mozconfig

I bet --enable-logging is causing this.  Please file a new bug.  Thanks!

Comment 12

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

(In reply to :Ehsan Akhgari (needinfo? me!) from comment #11)
> (In reply to comment #10)
> > Created attachment 8348216 [details]
> >   --> https://bugzilla.mozilla.org/attachment.cgi?id=8348216&action=edit
> > .mozconfig
> 
> I bet --enable-logging is causing this.  Please file a new bug.  Thanks!

Comment #3 explains very clearly that the problem is with LOG. Why did you check these patches back in knowing that there is a bug with them, and after the bug was clearly pointed out, and without giving me even 24 hours to reply to your request? Lots of people build with --enable-logging and it isn't like I backed out the patches for fun.

Comment 13

[(no longer active)]

(In reply to Brian Smith (:briansmith, was :bsmith; Please NEEDINFO? me if you want a response) from comment #12)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #11)
> > (In reply to comment #10)
> > > Created attachment 8348216 [details]
> > >   --> https://bugzilla.mozilla.org/attachment.cgi?id=8348216&action=edit
> > > .mozconfig
> > 
> > I bet --enable-logging is causing this.  Please file a new bug.  Thanks!
> 
> Comment #3 explains very clearly that the problem is with LOG. Why did you
> check these patches back in knowing that there is a bug with them, and after
> the bug was clearly pointed out, and without giving me even 24 hours to
> reply to your request? Lots of people build with --enable-logging and it
> isn't like I backed out the patches for fun.

Because we don't backout patches which break --enable-warnings-as-errors builds on non-standard configurations.  Also, the bug was not clearly pointed out in comment 3, and I did go through the trouble of doing a --enable-warnings-as-errors debug and opt build locally, both of which succeeded.

Comment 14

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/ac40b01fd56b