To clarify, to make this hardware work you need to have several kernel options selected. For reasons below, you want to build them as modules, not monolithic-ally into the kernel (in the Linux kernel menuconfing, press M. If you don't know how to configure and compile a kernel, consult the Gentoo ...

This is still failing for me after a sync. The problem is that all though I don't now have ruby 2.2.x installed at all, I still have it in RUBY_TARGETS according to emerge --info:
RUBY_TARGETS="ruby22 ruby23"
This isn't set anywhere in /etc/portage/, and I have my profile set to the desktop stable ...

For anyone else hunting a solution to this, I've just found that I need the following lines in /etc/wpa_supplicant/wpa_supplicant.conf in order to make wpa_gui work (running as a user in the plugdev group, change to suit your needs)

# needed for wpa_gui to work
ctrl_interface=DIR=/var/run/wpa ...

Looks like you need this changeset to the ebuild:

http://sources.gentoo.org/cgi-bin/viewv ... 1.2&r2=1.3

in order for the emerge to work, which is from Thu Feb 16 17:47:47 UTC.

Just a quick note that I've put an ebuild for 1.8.0 release on the [bug=139019]bugzilla entry[/bug] which removes some more binary libs and tidies up the version code so that future bumps could be as simple as renaming the ebuild.

emerge twisted.

The only thing that makes any difference to the bandwidth usage in the end though is the bitrate you stream at - the higher that is, the more bandwidth you use, period.

The fact that flumotion streams vorbis/theora helps with the quality becuase they work well at low bitrates, but ...

I'm now working on this fairly seriously. To start off I had to create a patch to flumotion-0.2.2 to make it build, and then write the ebuild to apply it. Those two come from the bug at
http://bugs.gentoo.org/show_bug.cgi?id=138214

The best way to get started is probably to start the worker ...

I think with ivtv-0.8.x you need to to use v4l2-ctl in a lot of places where you used to use ivtv-ctl because of the merger into v4l2 in the kernel. I think the same issues apply to the channel changing mechanism, the reason it doesn't work bwing that the IOCLT API has changed so that although it ...

Does it for me as well.
The problem is in /usr/lib/sputnik.pm at about line 271 - it looks for the file in the wrong place. I tried hard coding the file location (/usr/share/doc/yosucker-73/conf/header-translation) in at that seems to work OK.
I get a load of "Header structure corruption! Message ...

Depends on developer time to get remaining bugs removed. Probably in the next month or so unless people are very busy. May well be preceded by 1.2.5 (which doesn't change much except some obscure bugs in 1.2.4).

Unmask audacity 1.2.4b - it has better checks and so will work like you expect it to. No sane reason why it remains ~x86 except lack of time to get it stabilised - every time wxGTK breaks audacity bugs get files and it's considered "unstable".

See the 101 other posts. Remerge wxGTK after major GTK+ updates, as it usually gets broken.

So to summaries, if audacity or any other wx app fails with a compile error, then try re-building wxGTK first - it's very sensitive to GTK+ changes in a way that revdep-rebuild doesn't seem to pick up.

as far as wxProtoFile goes, the key thing is to re-emerge wxGTK-2.4, as it's been built against an older GTK+ version, and the GTK+ upgrade has broken wxGTK.

Turning on OSS in the kernel will upset ALSA, so leav it off, set the "oss" use flag, emerge alsa-oss and alsa-utils, and then you will get the OSS emulation loaded at boot time, and audacity will work.

Or rebuild wxGTK 2.4.x and then install audacity 1.2.4b from main portage. The problem is that wxGTK often is affected by GTK+ changes, and so needs rebuilding, which doesn't happen because it is a library and so not caught by revdep-rebuild.

Re-emerge wxGTK since GTK+ changes, try unmasking current stable audacity (1.2.4b)

I assume you are in x86, in which case the solution for audacity is to unmask the ebuilds from portage, so you get wxGTK 2.4.2-r4 (or later), and wxGTK-2.6.2 or later, which are slotted. You can then put audacity-1.2.4b-r1 or audacity-1.3.0b on top without problems.

The trick is that you can tell ...

Make sure you have the latest wxGTK - it installs the unicode and non-unicode versions side by side.
Then unmask the latest audacity 1.2.x (nice to see portage up to date) and emerge that, because the wxGTK checks have changed to reflect the current wxGTK ebuilds, and it should then work.

Do you have the oss use flag on? If not you won't have OSS emulation loaded at bootup by alsa-utils, and so you need to start audacity as
aoss audacity
to load the emulation and make the OSS sound devices availably to audacity.
This also assumes you don't have a sound daemon getting in the way, in ...

The original problem is the gcc-3.3 to gcc-3.4 switch. This changed library interfaces for c++ libraries, including wxwidgets, which audacity depends on. You got the error because you build wxwidgets before the compiler switch and audacity after, so they didn't play nicely. Emerging audacity and ...

Put very simply, audacity can't record in mono under linux whilst playing back other tracks because it ends up playing in stereo and recording in mono. This would be fine if you had native OSS audio drivers, but you don't you have ALSA + the OSS emulation modules.

The emulation modules can't cope ...

Support for exporting to multichannel wav files is in current audacity CVS (so will be in 1.3.1).

The reason your fdisk failed was that you tried to fdisk the partition. Fdisk is a tool for making partitions on a drive, so sensibly enough it won't let you create partitions within partitions ....

So after making sure that nothing important is on the drive, you do
cfdisk /dev/sda
assuming your ...

I updated a really out of date to current glibc recently, and had to manually steal a copy of /lib/libpthread-2.3.5.so and symlink it to /lib/libpthread.so.0 in order to get almost anything to work. I think this one is related to going from kernel 2.4 (pthread only) straight to a nptlonly build of ...