Summary: | www-client/chromium-24.0.1312.27 pulse_output.cc ‘kChannelOrderings’ was not declared in this scope | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rick Farina (Zero_Chaos) <zerochaos> |
Component: | New packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | http://code.google.com/p/chromium/issues/detail?id=32757 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
Rick Farina (Zero_Chaos)
2012-12-04 19:39:46 UTC
Created attachment 331440 [details]
build log
From the log: media/audio/pulse/pulse_output.cc: In function ‘pa_channel_map media::ChannelLayoutToPAChannelMap(media::ChannelLayout)’: media/audio/pulse/pulse_output.cc:89:28: error: ‘kChannelOrderings’ was not declared in this scope Adding upstream bug, which includes a patch. (In reply to comment #3) > Adding upstream bug, which includes a patch. Fixes compile. Special note, seems to take ~6GB of RAM to build, might want a warning about that. We do warn about it if the build process fails. Otherwise, it is just another pointless elog message. functionality check passed. with this patch I would suggest to unmask pulseaudio useflag. (In reply to comment #6) > functionality check passed. with this patch I would suggest to unmask > pulseaudio useflag. Thank you for reporting this. Now that patch has been committed upstream as part of the other bug. Please notify us when the flag can be unmasked for an actual release. We'd rather not apply custom patches here, especially ones not properly submitted upstream. (In reply to comment #7) > (In reply to comment #6) > > functionality check passed. with this patch I would suggest to unmask > > pulseaudio useflag. > > Thank you for reporting this. Now that patch has been committed upstream as > part of the other bug. Please notify us when the flag can be unmasked for an > actual release. We'd rather not apply custom patches here, especially ones > not properly submitted upstream. So wait, we are closing the bug, not adding the patch, and not unmasking the use flag and I'm expected to test build every version of chromium until the patch is applied then report? That about the size of it? I didn't realize the trunk already had the fix for your build issue, which was probably caused by upgrading to pulseaudio-2.1. Unfortunately, you are testing code that does not include the latest upstream changes/fixes. The next chromium-25 release will probably have the latest changes. If it does, we can unmask the flag for that version. If not, we probably wait for chromium-26. |