648720 - Build failure in ../mailnews/base/src/nsMsgRDFDataSource.cpp

Status: RESOLVED FIXED

(MailNews Core :: Build Config, defect)

Description

[Bengt-Erik Soderstrom]

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.2a1pre) Gecko/20110407 Firefox/4.2a1pre SeaMonkey/2.2a1pre
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.2a1pre) Gecko/20110407 Firefox/4.2a1pre SeaMonkey/2.2a1pre

Since a few days the following happens:

../mailnews/base/src/nsMsgRDFDataSource.cpp:108: error: expected constructor, destructor, or type conversion before ‘NS_IMPL_CYCLE_COLLECTING_RELEASE_AMBIGUOUS’

Build fails- Using Ubuntu 10.10 with gcc 4.4.5 in a 64-bit environment.

Reproducible: Always

Comment 1

[Philip Chee]

update to the latest mozilla-central and comm-central sources, clobber your objdir and then try rebuilding. There have been significant changes on trunk recently.

Comment 2

[Bengt-Erik Soderstrom]

(In reply to comment #1)
> update to the latest mozilla-central and comm-central sources, clobber your
> objdir and then try rebuilding. There have been significant changes on trunk
> recently.

I did all this, really:

1. I always start with 'python client.py' In this way both mozilla-central and comm-central are updated to the latest source. If I then encounter build problems, I always nuke the object directory and restart.

2. Restart with an empty object directory did not help in this case.

3. 2 days ago the build was successful, just after bugs 647000 and 647003 were resolved.

Comment 3

[Bengt-Erik Soderstrom]

I am also making a try with Fedora 14, 32 -bit, which has gcc 4.5.1. I will report the result as soon as it is available

Comment 4

[Bengt-Erik Soderstrom]

Fedora 14 32-bit build finished. Same error:
 ../mailnews/base/src/nsMsgRDFDataSource.cpp:108: error: expected constructor,
destructor, or type conversion before
‘NS_IMPL_CYCLE_COLLECTING_RELEASE_AMBIGUOUS’

This build was done on a different machine, with its own source.

Comment 5

[Mark Banner (:standard8)]

This failure is shown on tinderbox and its fallout from bug 584048.

Comment 6

[Mark Banner (:standard8)]

(or rather fallout from bug 584048 landing in mozilla-central).

Comment 7

[Ian Neal]

Attachment: Switch from ambiguous patch v1.0 [Checked in: Comment 14]

In theory, fairly simple.

Comment 8

[David :Bienvenu]

Comment on attachment 524847 [details] [diff] [review]
Switch from ambiguous patch v1.0 [Checked in: Comment 14]

looks like the right thing to do - I'll try building with this.

Comment 9

[Ian Neal]

(In reply to comment #8)
> Comment on attachment 524847 [details] [diff] [review]
> Switch from ambiguous patch v1,0
> 
> looks like the right thing to do - I'll try building with this.

I'm testing against comm-central/mozilla-central tree, so if you have a comm-central/mozilla-2.0 tree to test against that would be good.

Comment 10

[David :Bienvenu]

I've kicked off a build against moz 2.0

Comment 11

[Ian Neal]

Comment on attachment 524847 [details] [diff] [review]
Switch from ambiguous patch v1.0 [Checked in: Comment 14]

Build completed without error against comm-central/mozilla-central
Started app and accessed addressbook and messages without issue.

Comment 12

[Bengt-Erik Soderstrom]

Also for me the build now, with the patch applied, was successful on comm-central trunk.

Comment 13

[[e-mail]]

I should have said that I already fixed this in my SeaMonkey 2.2 tree and tested the fix against my SeaMonkey 2.1 tree half an hour before I was CCd ;-)

Comment 14

[Ian Neal]

Comment on attachment 524847 [details] [diff] [review]
Switch from ambiguous patch v1.0 [Checked in: Comment 14]

http://hg.mozilla.org/comm-central/rev/3bb7223d1f3a

Comment 15

[Ian Neal]

Comment on attachment 524847 [details] [diff] [review]
Switch from ambiguous patch v1.0 [Checked in: Comment 14]

Well telepathy is partially working then ;)