I'm trying to compile Wine 1.1.36 on my normal Mac OS X 10.4 build machine. I've successfully built Wine 1.1.5 through 1.1.35 all on this machine.... but 1.1.36 is giving me a problem during configure. Anyone know what might be causing this? these are the last few lines when it dumps out during configure Code: config.status: creating dlls/wtsapi32/Makefile config.status: creating dlls/wuapi/Makefile config.status: creating dlls/wuaueng/Makefile config.status: creating dlls/xinput1_1/Makefile config.status: creating dlls/xinput1_2/Makefile config.status: creating dlls/xinput1_3/Makefile config.status: creating dlls/xinput1_3/tests/Makefile config.status: creating dlls/xinput9_1_0/Makefile config.status: creating dlls/xmllite/Makefile config.status: creating documentation/Makefile config.status: creating fonts/Makefile config.status: error: cannot find input file: `include/Makefile.in' the full output is here... http://pastebin.com/m30e0c5a3 I'm no expert, but it looks like something is put together wrong in the source.... like its looking in the wrong places. any ideas how i can get this to compile, or what the major changes are from 1.1.35 to 1.1.36 that caused this? the only configure option I'm using is a non-standard prefix
doh123 wrote:> I'm trying to compile Wine 1.1.36 on my normal Mac OS X 10.4 build machine. I've successfully built Wine 1.1.5 through 1.1.35 all on this machine.... but 1.1.36 is giving me a problem during configure. Anyone know what might be causing this? > > these are the last few lines when it dumps out during configure > > Code: > config.status: creating dlls/wtsapi32/Makefile > config.status: creating dlls/wuapi/Makefile > config.status: creating dlls/wuaueng/Makefile > config.status: creating dlls/xinput1_1/Makefile > config.status: creating dlls/xinput1_2/Makefile > config.status: creating dlls/xinput1_3/Makefile > config.status: creating dlls/xinput1_3/tests/Makefile > config.status: creating dlls/xinput9_1_0/Makefile > config.status: creating dlls/xmllite/Makefile > config.status: creating documentation/Makefile > config.status: creating fonts/Makefile > config.status: error: cannot find input file: `include/Makefile.in' > >You may have to resync your git. This file is present in the git I just updated. James McKenzie
James McKenzie wrote:> doh123 wrote: > > > I'm trying to compile Wine 1.1.36 on my normal Mac OS X 10.4 build machine. I've successfully built Wine 1.1.5 through 1.1.35 all on this machine.... but 1.1.36 is giving me a problem during configure. Anyone know what might be causing this? > > > > these are the last few lines when it dumps out during configure > > > > Code: > > config.status: creating dlls/wtsapi32/Makefile > > config.status: creating dlls/wuapi/Makefile > > config.status: creating dlls/wuaueng/Makefile > > config.status: creating dlls/xinput1_1/Makefile > > config.status: creating dlls/xinput1_2/Makefile > > config.status: creating dlls/xinput1_3/Makefile > > config.status: creating dlls/xinput1_3/tests/Makefile > > config.status: creating dlls/xinput9_1_0/Makefile > > config.status: creating dlls/xmllite/Makefile > > config.status: creating documentation/Makefile > > config.status: creating fonts/Makefile > > config.status: error: cannot find input file: `include/Makefile.in' > > > > > > > You may have to resync your git. This file is present in the git I just > updated. > > James McKenzieI can try git, but like to keep normal release versions... but this was from the source download at http://ibiblio.org/pub/linux/system/emulators/wine/wine-1.1.36.tar.bz2 linked right off the release page. maybe there's is just messed up? I'll try some other places and get the latest from git.
I suggest you wait for Mike Kronenberg's (http://mike.kronenberg.org) build of Wine. It's easy to use and has a useful tool called WineBottler along with it which helps manage prefixes and create application bundles. It's one of the best builds of Wine around for Mac OS X[/url]
ok, I jumped the gun on making this thread... I downloaded the source from the second link on the release info page and it didn't have these errors. it does have a different problem though... that might be related to the win16 changes.... I didn't write down the error, but the "make" erred out and failed on one of the win16 files... never had a problem with win16 building before. I built it with --disable-win16 and the compile went through. I wouldn't mind leaving win16 support in, but its not a major concern.
doh123 wrote:> > samir_otiv wrote: > > I suggest you wait for Mike Kronenberg's (http://mike.kronenberg.org) build of Wine. It's easy to use and has a useful tool called WineBottler along with it which helps manage prefixes and create application bundles. It's one of the best builds of Wine around for Mac OS X[/url] > > > WineBottler is a nice build for general uses, I suggest it to a lot of people, but I make a wrapper app used for porting (http://wineskin.sourceforge.net/), which has a different goal (its not for general Wine usage), where I have to have my own builds compiled to work right in the wrapper.I think WineBottler also does the same thing. It can make bundles which are ports of Windows software, and these bundles can be made to include Wine, so the target computer doesn't need Wine installed, and to the end user its very easy - just like any other bundle
samir_otiv wrote:> > I think WineBottler also does the same thing. It can make bundles which are ports of Windows software, and these bundles can be made to include Wine, so the target computer doesn't need Wine installed, and to the end user its very easy - just like any other bundleWhile this isn't really about a debate over which is better... Wineskin or WineBottler's bundled up .app install... I know I still have a lot of work to do on Wineskin (I'm currently re-writing the whole configure app in it), but I much prefer the customizability I put into it, to easily change out Wine versions, not be stuck with only 1 version... edit source code for little work arounds... and that I build in an X server.. so its the same on all platforms, not going by the default install... and that it has its own custom Icon and not just run under "X11.app"... I have built in work arounds for Xquartz limitations, to easily launch in fullscreen mode or windowed, and change the resolutions for fullscreen. Its very helpful since Wineskin is used a lot for game ports... but there are many differences in the two