Using libsndfile, ncurses, alsa-libs and of course fftw3 library, one can write a 200-liner console program in C that performs spectral analysis of a sound file while playing it. This is of course limited to audio files supported by libsndfile, which is currently wav and ogg. But nothing prevents people to do lame -d or use a similar decoder and pipe the resulting wave to the program.
What I am talking about? Look:
https://github.com/jirislaby/collected_sources/tree/master/snd_fft
https://github.com/jirislaby/L2capUsing Bluetooth, a phone can move with mouse pointer and press mouse buttons on your machine. The only thing needed is to run l2cap from the repository on the machine and the Java app on the phone. Of course l2cap is Linux-specific but it should not be that hard to extend to other systems.
When creating an RPM of some package this error might occur. Sometimes it does not make much sense as it lists only debug files as unpackaged.
In this case, it is most likely caused by invalid use of %exclude macro. Grr. I spent a bunch of time debugging this. HTH somebody.
So the second pile of TTY patches have been accepted…
And now, the most of drivers in the tree was augmented to operate with tty_port structure. The only few remaining will be changed in the next merge window (a month or so). After that, every out-of-tree driver will be broken unless it is fixed right now. You have been warned.
One might ask, why we are doing this change? The answer is simple: The code is broken. Some of the code predates Linux 1.0. Yes, it is no argument, but you know what? It is full of ancient broken code designed originally for uniprocessor, no preemption and such. Thus there are many race conditions without any real chance to fix them in the state the code stands now.
And yet, Big-Kernel-Lock (BKL). You heard that it is gone from the kernel for some time already, right? No, it is not. It is still there. Some parts of the kernel still have left-overs from this ancient coarse-grained crap. In TTY, it is called Big-TTY-Mutex. And nobody really knows what is protected by the lock (and what is not). And as a reader may suggest, I volunteered to find out.
The plan is to centralize common code which is repeated over and over. This is done by using tty_port helpers. Next, we will move TTY I/O buffers from tty_struct to tty_port and revamp locking a bit. The move will also ensure that we will not need to care about tty_struct in a prevalent count of interrupt service routines, timers etc. They really need TTY buffers, not a structure which randomly comes and goes with every open and close the way tty_struct does. And since tty_port is in the memory intact as long as the device stays in the machine (and its interrupt service routine installed in the kernel), it is a perfect place to put the buffers in. And this is exactly what is happening here right now.
Stay tuned and report bugs!
$ ant jar
...
.../build.xml:89: Problem: failed to create task or type
antlib:org/apache/tools/ant/antlr:antlr3
.../build.xml:92: Problem: failed to create task or type
antlib:net.sf.antcontrib.cpptasks:cc
The cure is (and always was) simple on openSUSE. One just needs to define OPT_JAR_LIST environment variable with appropriate jar names of packages where those classes are defined:
OPT_JAR_LIST='ant-antlr3.jar cpptasks.jar' ant jar
error: 'void clang::ento::register...Checker(clang::ento::CheckerManager&)' should have been declared inside 'clang::ento'
clang -cc1 -analyzer-checker-help
cat /dev/zero > /dev/null &
#include <stdio.h>
struct A {
};
int main(void)
{
printf("%zu\n", sizeof(struct A));
return 0;
}
Tak jako informatik nemůže ladit programy v rutinním provozu, neměl by ani zákonodárce ladit své zákony až po uvedení v platnost.
fuj order by cas desc'; select 1; -- '