http://bugs.winehq.org/show_bug.cgi?id=24478
--- Comment #11 from Erich Hoover ehoover@mines.edu 2010-11-04 22:24:35 CDT --- (In reply to comment #10)
Follow-up: If I manually edit pin.c and move "#include "config.h"" to the very top of the list of #include lines then this patch compiles successfully. Previously there were several other #include lines ahead of it.
Yeah, a recent change broke that - it'll be fixed before I submit.
Unfortunately I still hear no background music of any kind (neither opening screen, nor in-game radio stations [other than speech]) in Fallout: New Vegas. I was hoping it would work for me because New Vegas uses the same basic engine as Fallout 3. The game is otherwise fully playable and stable, even for hours at a time, once it loads.
Have you compiled patches before? Did you try with F3 (I do not yet own F:NV)? I know that I sometimes forget to open a new terminal sometimes after compiling Wine from source. You can test that the correct version of Wine is being used by executing "which wine" from a terminal, when you compile Wine yourself it should return "/usr/local/bin/wine" whereas a "release" build will report "/usr/bin/wine".