Charles Davis wrote: > On 7/12/10 2:53 PM, dwarfcricket wrote: > > > Charles Davis wrote: > > > > > On 7/12/10 2:24 PM, dwarfcricket wrote: > > > > > > > > > > Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." :| > > > > > > > > > > > Oh, so it's a Win16 program. > > > > > > In that case, there are three things you can do: > > > - Run Windows in a VM, like John suggested. But that requires you to > > > have a Windows license. > > > - Upgrade to Snow Leopard. The reason MacPorts builds without Win16 > > > support is that Xcode 3.x has a linker that can't handle 16-bit code > > > very well. Xcode 3.2, which comes with SL, does not have this problem. > > > - Patch the linker. See bug 14920 > > > (http://bugs.winehq.org/show_bug.cgi?id=14920 ) for more info. > > > > > > If you pick one of the last two options, though, you'll then have to > > > change the Portfile to not pass --disable-win16 to Wine's configure script. > > > > > > Chip > > > > > > > > > > > Well, I don't have a Windows license, unfortunately. > > > > SO, if I were to go about patching it - how would I change the Portfile? > > > The Portfile is in > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/wine-devel. > There's a line that reads: > > configure.args-append --disable-win16 > > If you put a pound sign in front: > > # configure.args-append --disable-win16 > > then MacPorts won't disable Win16 support when it builds Wine. > > You only need to do this if you patch the linker, though. I just > realized that the Portfile is smart enough to realize when it's on SL. > There, it leaves Win16 support in. > > Chip Well, I attempted to change the Portfile, but it keeps telling me I don't have the appropriate access to do so - even though my account (I'm the admin) is allowed to Read & Write - is there another way for me to change the settings so that I may change and save the Portfile?