wine users - Dec 2011 - Get configuration flags

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.

jorl17 wrote:
> 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

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

Usurp wrote:
> 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.