On 01/19/18 11:16 PM, Ken Moffat  <zarniwh...@ntlworld.com> wrote:
> 
> On Thu, Jan 18, 2018 at 12:34:04AM +0000, Ken Moffat wrote:
> > On Wed, Jan 17, 2018 at 10:28:46PM +0000, Ken Moffat wrote:
> > > > > On Tue, Jan 16, 2018 at 01:07:07AM +0100, Tim Tassonis wrote:
> > > > > > Hi All
> > > > > > 
> > > > > > On 01/16/2018 12:29 AM, Tim Tassonis wrote:
> > > [...]
> > > > > > 
> > > > > > To leave sandboxing active and get alsa sound running, you can also 
> > > > > > set
> > > > > > 
> > > > > > security.sandbox.content.syscall_whitelist
> > > > > > 
> > > > > > to 16, which is the iotcl syscall needed by alsa. For 32bit 
> > > > > > architectures,
> > > > > > the value is 54.
> > 
> > I've now built b16 with alsa on a second machine: initially no
> > sound, but setting security.sandbox.content.syscall_whitelist to 16
> > in about:config, and restarting direfox, fixed it.
> > 
> > Maybe I've left it set like that on the other machine.
> > 
> 
> Anybody willing to try building it with pulse and style (needs
> clang) on a fast multicore machine, test html5 pulse audio, and if
> necessary rebuild using alsa instead of pulse ? At the moment I'm
> the only person who apparently gets no aound with pulse, so I'm
> reluctant to move the book back to alsa if the problem is in my
> setup. More data would be welcome. TIA.
> 

Is your no-audio problem consistent, or does it happen intermittently? I
_sometimes_ get no sound with Firefox using PulseAudio. What works for me when
the sound isn't working is by closing Firefox, and then re-setting my default
sink for PulseAudio. For example: running

"pactl list short sinks," and then
"pacmd set-default-sink <sink #>"

Restarting Firefox then re-enables sound.
I cannot determine what exactly causes the sound issue, but the steps listed
above always "fixes" the sound problems (in my case!).


> 
> For rustc, the line 'channel = "stable"' needs to be deleted for
> recent versions. For firefox, use ./mach build (or ./mach build
> --verbose) and (DESTDIR=/some/where ) ./mach install.
> 
> 
The line doesn't need to be deleted; It needs to be only moved from the header
named "[install]" to the newly-added header "[rust]" 
I noticed this when my first attempt to build Rust 1.23.0 failed at the install
phase. After looking at the example config.toml file I saw that "channel="
moved places.

Therefore, the new config.toml should look like this:

cat <<EOF > config.toml
# see config.toml.example for more possible options
[llvm]
targets = "X86"

[build]
# install cargo as well as rust
extended = true

[install]
prefix = "/usr"
docdir = "share/doc/rustc-1.23.0"

[rust]
channel = "stable"
EOF


> 
> ĸen
> -- 
> Truth, in front of her huge walk-in wardrobe, selected black leather
> boots with stiletto heels for such a barefaced truth.
>  - Unseen Academicals
> -- 
> http://lists.linuxfromscratch.org/listinfo/blfs-dev
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to