1.1.36 compile problem on Mac OS X

doh123 · Post by **doh123** » Sun Jan 10, 2010 6:19 pm

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: Select all

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

James McKenzie · Post by **James McKenzie** » Sun Jan 10, 2010 6:34 pm

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

doh123 · Post by **doh123** » Sun Jan 10, 2010 7:24 pm

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 McKenzie

I can try git, but like to keep normal release versions...

but this was from the source download at http://ibiblio.org/pub/linux/system/emu ... 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.

James McKenzie · Post by **James McKenzie** » Sun Jan 10, 2010 7:34 pm

doh123 wrote:

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 McKenzie

I can try git, but like to keep normal release versions...

but this was from the source download at http://ibiblio.org/pub/linux/system/emu ... 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.

Doh123:

The tarball may be messed up. I don't know how that could happen, but
I've had problems with files getting corrupted as well.

This was reported on wine-devel.

James McKenzie

samir_otiv · Post by **samir_otiv** » Mon Jan 11, 2010 4:14 am

I suggest you wait for Mike Kronenberg's 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]

doh123 · Post by **doh123** » Mon Jan 11, 2010 9:10 am

samir_otiv wrote:I suggest you wait for Mike Kronenberg's 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.

Gert van den Berg · Post by **Gert van den Berg** » Mon Jan 11, 2010 10:19 am

On Mon, Jan 11, 2010 at 11:14, samir_otiv <[email protected]> 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]

It is probably easier than compiling it yourself, but you are unlikely
to be helped here if you experience problems with WineBottler.

doh123 · Post by **doh123** » Mon Jan 11, 2010 2:32 pm

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.

ryan woodsmall · Post by **ryan woodsmall** » Mon Jan 11, 2010 5:23 pm

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.

Definitely an issue in win16 code on 10.4/10.6, where it should work. I've not had any time to run a bisect on Git yet or report a bug, but there were lots of changes/fixes for win16 in 1.1.36:

http://www.winehq.org/announce/1.1.36

Anyone run a "git bisect" on OS X between 1.1.35 and 1.1.36?

James McKenzie · Post by **James McKenzie** » Mon Jan 11, 2010 11:04 pm

ryan woodsmall wrote:

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.

Definitely an issue in win16 code on 10.4/10.6, where it should work. I've not had any time to run a bisect on Git yet or report a bug, but there were lots of changes/fixes for win16 in 1.1.36:

http://www.winehq.org/announce/1.1.36

Anyone run a "git bisect" on OS X between 1.1.35 and 1.1.36?

No, but are you using the patched ld?

I'll be updating the EM_FORMATRANGE patch in about a day so I'll report
back with testing results (pass/fail) tomorrow on Leopard (10.5.8 with
the ld patch).

James McKenzie

ryan woodsmall · Post by **ryan woodsmall** » Mon Jan 11, 2010 11:07 pm

No, but are you using the patched ld?

I'll be updating the EM_FORMATRANGE patch in about a day so I'll report
back with testing results (pass/fail) tomorrow on Leopard (10.5.8 with
the ld patch).

No, no patches whatsoever. Only building straight from source, nothing custom, all standard archive instals. What's the patched ld?

samir_otiv · Post by **samir_otiv** » Tue Jan 12, 2010 2:22 am

doh123 wrote:
samir_otiv wrote:I suggest you wait for Mike Kronenberg's 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

Charles Davis · Post by **Charles Davis** » Tue Jan 12, 2010 6:07 am

ryan woodsmall wrote:

No, but are you using the patched ld?

I'll be updating the EM_FORMATRANGE patch in about a day so I'll report
back with testing results (pass/fail) tomorrow on Leopard (10.5.8 with
the ld patch).
No, no patches whatsoever. Only building straight from source, nothing custom, all standard archive instals. What's the patched ld?

I wrote a patch that "fixes" the linker bug (it's attached to Wine bug
14920) that prevents 16-bit programs from linking properly. (Apple fixed
it a different way for 10.6, hence "fixes" in quotes.) To use it, you
need the source for the ld64 package (the default linker in 10.5 up).
You just apply the patch in the root directory of the ld64 source, and
then you build the Xcode project that's included with ld64.

Again, I'd like to stress that this isn't necessary on 10.6 because
Apple has apparently fixed it (at least, AJ's configure test succeeds).

Chip

doh123 · Post by **doh123** » Tue Jan 12, 2010 10:47 am

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 bundle

While 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

samir_otiv · Post by **samir_otiv** » Wed Jan 13, 2010 2:29 am

doh123 wrote:
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 bundle
While 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

Sorry..I didn't mean to pit them against each other. I think WineSkin sounds very interesting.. BTW a custom icon can also be put using WineBottler, but what interests me about WineSkin is the fullscreen part..(...thinking about counterstrike:P)

Neway keep up the good work..!!..I'm afraid I can't help you bcoz my Mac isn't at home and there's no Mac OS X on my Mac now:)..Windows 7 is the way to go.

Good luck..!!