Jump to content
  • 0

Is there a way to have firefox 52 without pulse audio but having sound with alsa?


adcdam
 Share

Question

5 answers to this question

Recommended Posts

  • 0

Add these USE flags to your make.conf

USE="OTHERSTUFF alsa -pulseaudio"

Since you don't have pulseaudio installed you probably want this in make.conf to cover all builds.  I have this set and sound works fine in 52.0.1

 

Alternately you could put it in your package.use file.

www-client/firefox alsa -pulseaudio
Link to comment
Share on other sites

  • 0

i get this error

 

 

 

>

>> Emerging (1 of 1) www-client/firefox-52.0.1-r1::gentoo
 * firefox-52.0.1.source.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...         [ ok ]
 * firefox-52.0-patches-08.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...       [ ok ]
 *
 * You are enabling official branding. You may not redistribute this build
 * to any users on your network or the internet. Doing so puts yourself into
 * a legal problem with Mozilla Foundation
 * You can disable it by emerging firefox _with_ the bindist USE-flag
>>> Unpacking source...
>>> Unpacking firefox-52.0.1.source.tar.xz to /var/tmp/portage/www-client/firefox-52.0.1-r1/work
>>> Unpacking firefox-52.0-patches-08.tar.xz to /var/tmp/portage/www-client/firefox-52.0.1-r1/work
 * Sorry, but firefox-52.0.1 does not support the es locale
>>> Source unpacked in /var/tmp/portage/www-client/firefox-52.0.1-r1/work
>>> Preparing source in /var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1 ...
 * Applying patches from /var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox ...
 *   1000_gentoo_install_dir.patch ...                                       [ ok ]
 *   1001_disable_sdk_install.patch ...                                      [ ok ]
 *   1002_add_gentoo_preferences.patch ...                                   [ ok ]
 *   1003_drop_build_id.patch ...                                            [ ok ]
 *   1004_dont_hardcode_libc_soname.patch ...                                [ ok ]
 *   1005_gentoo_specific_pgo.patch ...                                      [ ok ]
 *   1006_fix_hardened_pie_detection.patch ...                               [ ok ]
 *   2000_Use-C99-math-isfinite.patch ...                                    [ ok ]
 *   2001_system_harfbuzz.patch ...                                          [ ok ]
 *   2002_system_graphite2.patch ...                                         [ ok ]
 *   6000_only_attempt_to_use_getcontext_on_glibc.patch ...                  [ ok ]
 *   6001_add_missing_header_for_basename.patch ...                          [ ok ]
 *   6002_add_alternate_name_for_private_siginfo_struct_member.patch ...     [ ok ]
 *   6003_fix_syscall_wrappers_on_musl.patch ...                             [ ok ]
 * Running eautoreconf in '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1' ...
 * Running autoconf ...                                                      [ ok ]
 * Running elibtoolize in: firefox-52.0.1/
 * Running elibtoolize in: firefox-52.0.1/intl/icu/source/
 * Running elibtoolize in: firefox-52.0.1/ipc/chromium/src/third_party/libevent/

 * Portage patch failed to apply (ltmain.sh version 2.4.2)!
 * Please file a bug report to add a proper patch.
 * ERROR: www-client/firefox-52.0.1-r1::gentoo failed (prepare phase):
 *   Portage patch failed to apply!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 5554:  Called eautoreconf 'old-configure.in'
 *   environment, line 1786:  Called elibtoolize '--force' '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1'
 *   environment, line 2024:  Called die
 * The specific snippet of code:
 *                                   die "Portage patch failed to apply!";
 *
 * If you need support, post the output of `emerge --info '=www-client/firefox-52.0.1-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=www-client/firefox-52.0.1-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/www-client/firefox-52.0.1-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-52.0.1-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1'
 * S: '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1'

>>> Failed to emerge www-client/firefox-52.0.1-r1, Log file:

>>>  '/var/tmp/portage/www-client/firefox-52.0.1-r1/temp/build.log'

 * Messages for package www-client/firefox-52.0.1-r1:

 * You are enabling official branding. You may not redistribute this build
 * to any users on your network or the internet. Doing so puts yourself into
 * a legal problem with Mozilla Foundation
 * You can disable it by emerging firefox _with_ the bindist USE-flag
 * Sorry, but firefox-52.0.1 does not support the es locale
 * Portage patch failed to apply (ltmain.sh version 2.4.2)!
 * Please file a bug report to add a proper patch.
 * ERROR: www-client/firefox-52.0.1-r1::gentoo failed (prepare phase):
 *   Portage patch failed to apply!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 5554:  Called eautoreconf 'old-configure.in'
 *   environment, line 1786:  Called elibtoolize '--force' '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1'
 *   environment, line 2024:  Called die
 * The specific snippet of code:
 *                                   die "Portage patch failed to apply!";
 *
 * If you need support, post the output of `emerge --info '=www-client/firefox-52.0.1-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=www-client/firefox-52.0.1-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/www-client/firefox-52.0.1-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-52.0.1-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1'
 * S: '/var/tmp/portage/www-client/firefox-52.0.1-r1/work/firefox-52.0.1'
Link to comment
Share on other sites

  • 0

You're welcome.  Note that the Firefox devs were making noise about discontinuing ALSA support entirely because they didn't want to maintain the ALSA backend.   If that happened these options would go away.  Fortunately in the brouhaha that erupted over this move someone stepped up and offered to maintain it.  So hopefully this build option will be maintained.

 

Being able to solve problems like this without being at the mercy of distro maintainers has everything to do with why I love Funtoo.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...