When emerging epiphany-1.0.7 it fails while compiling epiphany with the following text: ***************************************************************************** Epiphany can be built using Mozilla 1.4, 1.4.1, 1.5, or 1.6 or trunk snapshot, but the version available is 1.7.2. When using Mozilla trunk snapshot, a successful build is not guaranteed due to the frequently changing state of the Mozilla interfaces and the limited resources of the Epiphany team to support non-release Mozilla snapshots. ***************************************************************************** To install a later version of epiphany is difficult (we have a large deployment of gentoo) as gnome would have to be upgraded from 2.4 to 2.6. Reproducible: Always Steps to Reproduce: 1. Install machine with Gnome 2.4, epiphany-1.0.7 and Mozilla 1.6 2. Upgrade to Mozilla 1.7.2-r1 3. emerge =epiphany-1.0.7 Actual Results: During compile time of epiphany it stops with the error: checking for compiler -fshort-wchar option... yes checking for mozilla version... 1.7.2 configure: error: ***************************************************************************** Epiphany can be built using Mozilla 1.4, 1.4.1, 1.5, or 1.6 or trunk snapshot, but the version available is 1.7.2. When using Mozilla trunk snapshot, a successful build is not guaranteed due to the frequently changing state of the Mozilla interfaces and the limited resources of the Epiphany team to support non-release Mozilla snapshots. ***************************************************************************** Expected Results: Build OK, or a version of epiphany compatible with Gnome 2.4 and Mozilla 1.7
well mozilla API sadly changes too much atm to be a reliable build partner for epiphany, so you really have to go with the flow a bit. Normally i would say 'stay with the old mozilla', but it has security issues so you should update. Things you can try : * try fooling the config script that it is fine to build against mozilla-1.7.2 and see if it builds & works -> try to build vs the 'trunk' (probably won't though) * update the deployment, if you have a large deployment on similar machines you should just use one machine as buildbot & supply the others with binary packs from there. It shouldn't be too much work, although it might give other bugs. * backport the mozilla fixes to a compliant mozilla (1.6 or 1.4). I'm not sure what the extent of the fixes is, but there's probably patches for the issues for older mozilla's. This requires quite a bit of knowledge to do right i think. Besides that I don't think this is a Gentoo problem as is, since this is sort of beyond the scope of what we support at this point. A 'corporate' version of gentoo should fix this. So I'm closing this from that p.o.v., although we are open to further questions about the proposed solutions. But it might be better to do that on IRC or something.
