/dev/dsp missing in debian and cannot hear festival utterance - bash

Tried to make an utterance in festival and it seems /dev/dsp/ is missing in the debian. How to add this?
festival> (SayText "Hello")
Linux: can't open /dev/dsp
#<Utterance 0xb669c708>

Followed the instruction on https://wiki.debian.org/SoundFAQ
installing oss-compat using
apt-get install oss-compat
solves the issue basically but might be good to load the snd-pcm-oss using
modprobe snd-pcm-oss
this has to be done as root. This will create the /dev/dsp and solve the issue.

Related

I can't seem to get rdkafka to play nice with the confuent-kafka-go package

this is my first question on StackOverflow. Usually I find a solution from someone else's question but this time the internet does not seem to have many answers.
So I'm getting this message after using go get and every time I try and compile and run my application.
# pkg-config --cflags rdkafka
Package rdkafka was not found in the pkg-config
search path. Perhaps you should add the directory containing `rdkafka.pc'
to the PKG_CONFIG_PATH environment variable Package 'rdkafka', required by
'virtual:world', not found
I searched the issues on the github page for the repo and found one thread related to this, but none of those solutions seem to work for me. I'm running fedora 26, I have go 1.9 installed.
I've tried:
dnf install
Compiling from source as instructed on their README
yum install because I became desperate.
Downloading and installing from the RPM
Has anyone come accross this and maybe have an idea of how I can fix it?
I suggest that you install librdkafka from Confluent's repository as described in their documentation. But I think that you'll need to build librdkafka from source RPMs, like I'm doing for Ubuntu.
So I got it working thanks to Remi. Adding the repo from https://rpms.remirepo.net/ (I used the one for Fedora 26). Then just installing it using:
sudo dnf --enablerepo=remi install librdkafka-devel

Installation of asciidoctor on osx 10.11.5 for newbie?

I tried to follow the installation process defined at: http://asciidoctor.org/docs/install-asciidoctor-macosx/#rvm-procedure-recommended but it failed with the error message
Error running 'requirements_osx_brew_update_system ruby-2.3.0',
showing last 15 lines of
/Users/richardcoffre/.rvm/log/1466510618_ruby-2.3.0/update_system.log
Because I am a newbie, but want to use asciidoc format, I need an updated and detailed installation process to install asciidoctor.
Best regards
Richard
Install Homebrew
brew install ruby
Open new terminal tab/window
which gem, it should print /usr/local/bin/gem
gem install asciidoctor
We should probably create a Homebrew package for Asciidoctor, it's unnecessary complicated now.
I am aware this does not exactly answer your question...
An alternative to this installation approach is to use an Application like AsciidoctorFX:
Or even simpler the preview extension for chrome:
If you are a developer, there is a good integration with several build system (maven, gradle, rake, gulp, grunt...). In that case the package manager will download Asciidoctor and the dependencies for you.

How to package go project for homebrew

We're developing runscripts and try to support something like brew install runscripts.
It's written in golang and have some dependencies which required to go get. Now I have no idea to write the Formula to setup GOPATH and run go get. Our project can be compiled into an binary but we need run --init to install it.
Can anyone helps to give an example about a homebrew Formula of go project?
Fork homebrew, look at the content of Library/Formula/consul.rb. You don't need to manually generate all the resources. Use homebrew-go-resources. A more complete intro could be found here.
I have refer to termshare.rb and it seems we can simply go get and homebrew will handle anything about GOPATH for us.
That's great and I think my problem is solved.
The best I could find is how docker-swarm is added to brew: https://github.com/Homebrew/homebrew/blob/4c6857b0e337b2d5afd49dcf7209b6b5091709f4/Library/Formula/docker-swarm.rb
It's relatively clean and simple to follow.
You can use goreleaser to generate the formula automatically: https://goreleaser.com/customization/homebrew/
Here is a possible work around creating a build directory within the checkout as the GOPATH:
...
def install
system "mkdir -p build/src"
system "ln -s `pwd` build/src/repo"
system "GOPATH=`pwd`/build go get repo/mytool"
bin.install "build/bin/mytool"
...
end
...

can't find import go-gtk

I've been playing around with Google Go, I love the power behind it and decided to try out some libraries. I tried using goinstall to install github.com/mattn/go-gtk/gtk but when I try to compile an example I'm getting:
can't find import: github.com/mattn/go-gtk/gtk
I've heard that others have problems with goinstall, is there anything I can do to fix this? I also saw that some people fixed this by putting the path as something like github.com/mattn/go-gtk/gtk/gtk.so but it's still not working for me.
Use:
go install github.com/mattn/go-gtk/gtk
and it will download and install this library in $GOPATH/src
Use following command to install necessary packages
go get github.com/mattn/go-gtk

Ruby Gems Problem: uninitialized constant Gem::GemRunner

I had a rails 2.2 app running, when I tried to add the latest rspec plugin to it. I did that checking it from github with the script/plugin install command. That made some rake task to stop working, I googled for a while and found that I had to upgrade RubyGems. I did that and got the following error:
uninitialized constant Gem::GemRunner
It was a small and simple app under version control, so I erased everything, and apt-get remove ruby and rubygems, and reinstalled everything once again (doing apt-get install ruby, rubygems)
The problem it's still there, and I can't figure how to solve it. I'm quite new with Ubuntu, so maybe I'm not removing the packages really? (it takes very little time to execute the apt-get removes, so I'm not very confident)
What am I doing wrong? Is that a good way to do a 'clean start' (removing via apt and then reinstalling?)
PS: I've read that the problem is solved by modifiing framework.rb, but I cant find that file in the location that the author states...
I have a blog post that solves this issue.
It's because it's still trying to use the old gem executable, so you just symbolically link the new one (gem1.8) in place of the old one.

Resources