wine, wine-devel: joystick_osx.c:121: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'gIOHIDManagerRef'

[adsysingle@…]

This could be an issue with Wine and I have filed a bug report with them also. I followed the directions at ​http://davidbaumgold.com/tutorials/wine-mac/#part-1 and got an error. I contacted the author and sent him the log file and here is his reply:

"Looks like there's a problem with how a file is being compiled: it can't find the symbols it needs to compile properly. This could be a problem with Wine itself, or with the way Macports installs it. I checked Google, and I don't see anyone else with this problem, which is odd."

"I suggest you create a bug report on either trac.macports.org or ​http://bugs.winehq.org (or both!) and attach that log file to that bug report. Hopefully, someone more knowledgable than me will be able to help you out. -David"

I have attached the log file to this ticket.

[ryandesign (Ryan Carsten Schmidt)]

I haven't seen this problem before either.

It might help if you attach a complete log (one that does not contain the text "Skipping completed"); to generate this, clean and try again.

You should also try wine-devel instead of wine; this will get you the newer development version of wine; if this works, then the developers of wine have already fixed the problem.

[adsysingle@…]

Wine-Devel log

[adsysingle@…]

I tried the wine-devel and had no luck, here is the log for that build (a complete one). I'm not sure if it's the same error or not. I'm not sure how to clean the wine build so I can get a complete log.

[ryandesign (Ryan Carsten Schmidt)]

Replying to adsysingle@…:

I tried the wine-devel and had no luck, here is the log for that build (a complete one). I'm not sure if it's the same error or not.

Looks like it is.

I'm not sure how to clean the wine build so I can get a complete log.

"sudo port clean wine" would do so, but the above wine-devel log should be sufficient.

[ryandesign (Ryan Carsten Schmidt)]

Replying to adsysingle@…:

This could be an issue with Wine and I have filed a bug report with them also.

By the way what is the URL of the upstream bug report?

[adsysingle@…]

I'm sorry, I don't understand your question, what is an upstream bug report?

[ryandesign (Ryan Carsten Schmidt)]

The bug report you filed with the wine project.

[adsysingle@…]

Replying to ryandesign@…:

The bug report you filed with the wine project.

Ahh, sorry, here it is ​http://bugs.winehq.org/show_bug.cgi?id=28593

[ryandesign (Ryan Carsten Schmidt)]

Ok, the last comment there was that you should try a newer development version of wine. Since you've already done that and attached the log to this MacPorts ticket, I referred them here.

I've also compared your log with mine. Based an the configure phase output there are a few differences in our systems but I haven't yet figured out which if any of them accounts for the problem:

• I'm using ccache (in macports.conf); you're not
• I have the grep, librsvg, ImageMagick and gst-plugins-base ports installed; you don't

[adsysingle@…]

Replying to ryandesign@…:

Ok, the last comment there was that you should try a newer development version of wine. Since you've already done that and attached the log to this MacPorts ticket, I referred them here.

I've also compared your log with mine. Based an the configure phase output there are a few differences in our systems but I haven't yet figured out which if any of them accounts for the problem:

• I'm using ccache (in macports.conf); you're not
• I have the grep, librsvg, ImageMagick and gst-plugins-base ports installed; you don't

Would you suggest I install these things? if so could you advise me on how to do that or where to get them please.

[ryandesign (Ryan Carsten Schmidt)]

Replying to adsysingle@…:

Would you suggest I install these things?

I don't have any ideas at the moment so it's certainly something you can try.

if so could you advise me on how to do that or where to get them please.

They are all in MacPorts under the names stated. Please try one at a time, for example to install grep do this:

sudo port clean wine-devel
sudo port install grep
sudo port install wine-devel

If you still get the same error in the log about joystick_osx.c, repeat the above with the next port I listed. If you find one of these lets the installation proceed, let me know which one.

[adsysingle@…]

I have installed each of those things, following your directions cleaning wine between each installation but it hasn't solved the problem. I am still getting an error when building.

[ryandesign (Ryan Carsten Schmidt)]

Is this still a problem with wine 1.4?

[ryandesign (Ryan Carsten Schmidt)]

Is this still a problem with wine 1.4.1 or wine-devel 1.5.11?

[jmroot (Joshua Root)]

No response; closing.