Bug 207510 – www-client/epiphany-2.20.3 doesn't compile with gcc-4.3

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description milan hodoscek 2008-01-26 00:19:01 UTC]

www-client/epiphany-2.20.3 doesn't compile with gcc-4.3

Rename one of the duplicate parameters aURI in:

embed/mozilla/EphyBrowser.h

and cert in 

embed/mozilla/mozilla-x509-cert.h

[Comment 1 Rémi Cardona (RETIRED) 2008-01-26 08:12:48 UTC]

Please send patches to upstream, copy the bug url here and we'll put them in portage.

Thanks for reporting

[Comment 2 milan hodoscek 2008-01-27 17:44:51 UTC]

This is the link to the upstream bug report and patch

 http://bugzilla.gnome.org/show_bug.cgi?id=512408

And this is the error message so people can find this bug report

mv -f .deps/libephymozillaembed_la-EphySingle.Tpo .deps/libephymozillaembed_la-EphySingle.Plo
mv -f .deps/libephymozillaembed_la-GeckoCookiePromptService.Tpo .deps/libephymozillaembed_la-GeckoCookiePromptService.Plo
In file included from EventContext.cpp:79:
EphyBrowser.h:190: error: multiple parameters named 'aURI'
make[4]: *** [libephymozillaembed_la-EventContext.lo] Error 1
mv -f .deps/libephymozillaembed_la-GeckoFormSigningDialog.Tpo .deps/libephymozillaembed_la-GeckoFormSigningDialog.Plo
mv -f .deps/libephymozillaembed_la-EphyUtils.Tpo .deps/libephymozillaembed_la-EphyUtils.Plo
make[4]: Leaving directory `/var/tmp/portage/www-client/epiphany-2.20.3/work/epiphany-2.20.3/embed/mozilla'

[Comment 3 Gilles Dartiguelongue (RETIRED) 2008-04-26 22:06:22 UTC]

afaik, 2.22 has it, closing.

[Comment 4 Peter Alfredsen (RETIRED) 2008-06-24 18:57:27 UTC]

*** Bug 229271 has been marked as a duplicate of this bug. ***

[Comment 5 Manfred Knick 2008-06-25 13:44:31 UTC]

(In reply to comment #3)
> afaik, 2.22 has it, closing.
> 

I disagree.

Being forced to exploit gcc-4.3.1 (for whatever reason)
does not necessarily imply being prepared 
to pull in (another non-stable) gnome-2.22 tree.

[Comment 6 Rémi Cardona (RETIRED) 2008-06-25 14:22:43 UTC]

(In reply to comment #5)
> I disagree.

Ok

> Being forced to exploit gcc-4.3.1 (for whatever reason)
> does not necessarily imply being prepared 
> to pull in (another non-stable) gnome-2.22 tree.

The overall Gentoo policy is very clear on the topic. Mixing unstable and stable is _your_ problem, not ours. We are already trying our best to maintain a stable Gnome (2.20), an unstable one (2.22) and an experimental one (2.23/24).

If you mix and match stable and unstable, you're own your own.

Besides, Gnome 2.22 is very close to going stable.

[Comment 7 Manfred Knick 2008-06-25 15:36:20 UTC]

(In reply to comment #6)
> (In reply to comment #5)
> 
> The overall Gentoo policy is very clear on the topic. Mixing unstable and
> stable is _your_ problem, not ours. 

Accepted.

> We are already trying our best to maintain
> a stable Gnome (2.20), an unstable one (2.22) and an experimental one
> (2.23/24).

I defenitely really value the profund work!

> Besides, Gnome 2.22 is very close to going stable.
Nice to hear.

In the meantime, I restrained to KDE 3.5.9 which cleanly compiles 
with gcc-4.3.1 ; for the meantime, that's sufficient for me.

Thank you!

Kind regards
Manfred