Get configuration flags

[jorl17]

Hello all.

Not often do I ask a question myself, but here's one:

How do I know which compile flags (and/or compiler toolkit) were used to build a wine binary that I may have? I'm asking this question because, somehow, my own compiled version of Wine can't run an application, even though binaries that I grabbed from packages for other distros do work: flawlessly, in fact.

I can live with restraining those "custom binaries" in their own dusty little folders, but I'd like to know why something that other people build works and something I don't doesn't. The only thing that configure tells me is that it can't find OpenCL, libsane, OSSv4 and libcapi20, which shouldn't make any difference. My guess is that it's the compiler messing up (GCC 4.4.5).

Cheers, and thanks,

Jorl17

Note: Of course I know I can go and ask those in charge of packaging these binaries how they built it, but I decided to ask just in case.

[jjmckenzie]

Hello all.
I can live with restraining those "custom binaries" in their own dusty little folders, but I'd like to know why something that other people build works and something I don't doesn't. The only thing that configure tells me is that it can't find OpenCL, libsane, OSSv4 and libcapi20, which shouldn't make any difference. My guess is that it's the compiler messing up (GCC 4.4.5).

That is if you don't use those features.

What is NOT working on your build but is on the package distribution builds?

James

[jorl17]

Football Manager 2012 crashes, with something related to Berkelium.dll. Berkelium provides offscreen browser rendering via chromium. I can't even get a trace (just like a bug reported on the Demo page)

I read on the AppDB that people were managing to get the app running in Ubuntu. Then I realized (googled) that other people were also managing to get it to run, even though some of us were stuck with this error. After many attempts at many things, I just thought: "hey, let me grab Slackware's package and hack it in here. I was jumping around at 3AM, just about 35 minutes ago, as it worked.

I really think that it is probably related to something that the compiler is doing. These flags don't seem to matter that much, though I can go fetch the libraries anyway. It's also strange, because all other apps run perfectly with Wine. Also, I see this in two similar machines (32-bit and 64-bit, both running Gentoo). My next step will probably be installing Wine from Gentoo's repositories (hence, compiled by the same compiler) and see if that works.

Cheers,

Jorl17

[jorl17]

On a related note, after some tests, simply replacing kernel32.dll with the pre-built own is enough. The first fixme that shows up (where the crash should happen) is related to nls:GetGeoInfoW.

In case it might be of any use!

Thanks,

Jorl17

[vitamin]

How do I know which compile flags (and/or compiler toolkit) were used to build a wine binary that I may have?

Short of asking packager - this is no way. Even source package (ex .srpm) won't tell you about default distro flags for gcc.

[Usurp]

How do I know which compile flags (and/or compiler toolkit) were used to build a wine binary that I may have?

Short of asking packager - this is no way. Even source package (ex .srpm) won't tell you about default distro flags for gcc.

Some programs sum up what compilation flags were used to build them,
see for example gcc -v.

[Martin Gregorie]

On Mon, 2011-12-19 at 21:26 -0600, jorl17 wrote:

How do I know which compile flags (and/or compiler toolkit) were used
to build a wine binary that I may have?

Did you look at the Makefile? Its quite an obvious place to look, though
of course it won't show distro-specific settings, if there are any,
unless an auto-configuration tool added them.

Martin

[vitamin]

Some programs sum up what compilation flags were used to build them

Unfortunately Wine is not one of them... Which is a shame, it would have helped with some troubleshooting.