Created attachment 345484 [details] build.log I cannot tell what the error is. make just just reports that there was one, but in the log I cannot find it.
Created attachment 345486 [details] emerge --info '=app-accessibility/speech-dispatcher-0.7.1-r2'
$ emerge -pqv '=app-accessibility/speech-dispatcher-0.7.1-r2' [ebuild UD] app-accessibility/speech-dispatcher-0.7.1-r2 [0.8-r2] USE="alsa espeak -ao -flite -nas -pulseaudio -python -static-libs" PYTHON_TARGETS="python2_7%* -pypy1_9% -pypy2_0% -python2_5% -python2_6% (-python3_2%*)"
Confirmed. Seems quite some people are getting this issue on the forums. My use case was that I tried to downgrade from speech-dispatcher-0.8-r2 to 0.7.1-r2 (I was downgrading to chromium-26.x from 27.x). [ebuild UD ] app-accessibility/speech-dispatcher-0.7.1-r2 [0.8-r2] USE="alsa espeak pulseaudio python -ao -flite -nas -static-libs" PYTHON_TARGETS="python2_7%* -pypy1_9% -pypy2_0% -python2_5% -python2_6% (-python3_2%*)" 0 kB As a workaround I downgraded to speech-dispatcher-0.7.1-r1 (which compiled fine, and) which allowed me to downgrade chromium as well.
This issue is caused by texinfo-5.1. If you downgrade to the previous version in portage (4.13-r2) then speech-dispatcher-0.7.1-r2 compiles fine.
(In reply to comment #4) > This issue is caused by texinfo-5.1. If you downgrade to the previous > version in portage (4.13-r2) then speech-dispatcher-0.7.1-r2 compiles fine. This solution solved (temporary) the problem on my workstation, now we should wait a texinfo update/fix (which bug number?), or maybe add a "doc" use for speech-dispatcher ebuild which maybe allows the speech-dispatcher update without the texinfo problem, isn't ?
also USE='-*' works
Has anyone tested speech-dispatcher-0.8-r2 with the new texinfo? Does that build successfully? (In reply to comment #6) > also USE='-*' works Please, please, please stop suggesting USE="-*". This will most likely break your system in ways that you do not anticipate, and gentoo developers strongly discourage this practice.
Seems like it does, but chromium 27.0.1453.93 depends on speech-dispatcher 0.7*, which is also why a lot of people seem to be running into this problem.
(In reply to comment #7) > Has anyone tested speech-dispatcher-0.8-r2 with the new texinfo? Does that > build successfully? > > (In reply to comment #6) > > also USE='-*' works > > Please, please, please stop suggesting USE="-*". This will most likely break > your system in ways that you do not anticipate, and gentoo developers > strongly discourage this practice. rephrasing: also disabling all the use flags for the package make it build. If this break other dependant packages (chromium) they should add the needed use flag dependancy.
@chromium: Is this a dependency issue on your side that can be fixed, or should I do something with speech-dispatcher? Thanks, William
(In reply to comment #10) > @chromium: > Is this a dependency issue on your side that can be fixed, or should I > do something with speech-dispatcher? sys-apps/texinfo-5.1 is ~arch at this point, and now ~arch chromium (28.x) works with speech-dispatcher-0.8 (there was a short window between stable and beta where latest ~arch chromium was requiring speech-dispatcher-0.7). Feel free to adjust speech-dispatcher dependencies to prevent this problem.
Created attachment 349930 [details, diff] Fix building with recent texinfo
All, I am thinking 0.8-r2 should be our stable candidate. If we remove 0.7.1-r2 and 0.8-r1 would we break anything?
(In reply to William Hubbs from comment #13) > All, > > I am thinking 0.8-r2 should be our stable candidate. If we remove > 0.7.1-r2 and 0.8-r1 would we break anything? app-misc/gpsdrive fails to build against >=speech-dispatcher-0.8 but that package in tree fails because of some other breakages and needs updates. see #458856 #446424 and #444135 A working ebuild (except speech-dispatcher-0.8 incompatibility) can be found on https://github.com/satmd/gentoo-overlay/tree/master/app-misc/gpsdrive
(In reply to William Hubbs from comment #13) > I am thinking 0.8-r2 should be our stable candidate. If we remove > 0.7.1-r2 and 0.8-r1 would we break anything? As long as you leave 0.7.1-r1 in the tree to satisfy chromium-27's dependency (=app-accessibility/speech-dispatcher-0.7*:=) it should be fine. Ideally please coordinate with chromium@ the stabilization of 0.8.
Is there any reason, why the attached patch is not integrated as long as this version is in the tree?
Ok, the path of the file to patch have to be corrected, but then all should be working fine.
Removing speech-dispatcher-0.7.1-doc.patch eliminates the build failure. This patch caused the Czech documentation to be built, and texinfo 5.1 was failing while trying to build the Czech docs. Upstream does not build it by default, even though the lead developers are Czech! I seem to recall that there was a good reason for not building it, even before the release of texinfo 5.x, but I don't remember what it was. I just removed the patch from portage.
