> It's not wine's fault, and you're not missing any dependencies; the >> new version of gcc is probably buggy, and the bug is triggered by >> something inside wine. > >If you've compiled Wine before and are re-using object files from an >old gcc it's possible that there is a conflict between the object >files from before and the object files with your new version of gcc. >So, you could try a "make clean" and then compile again. > >Erich Hoover >ehoo...@mines.edu
I tried "make distclean" and also tried a new wine-git download... so far nothing. On with the flags test.
