winegcc: Fix compiling of 32-bit Winelib Apps on shared 32/64-bit setups
Hin-Tak Leung
hintak_leung at yahoo.co.uk
Fri Apr 16 17:47:21 CDT 2010
--- On Fri, 16/4/10, Marcus Meissner <marcus at jet.franken.de> wrote:
> On Fri, Apr 16, 2010 at 10:51:29PM
> +0200, André Hentschel wrote:
> > ---
> > tools/winegcc/winegcc.c | 8
> ++++++++
> > 1 files changed, 8 insertions(+), 0
> deletions(-)
> >
> > diff --git a/tools/winegcc/winegcc.c
> b/tools/winegcc/winegcc.c
> > index 7023ff4..f780a69 100644
> > --- a/tools/winegcc/winegcc.c
> > +++ b/tools/winegcc/winegcc.c
> > @@ -1252,6 +1252,14 @@ int main(int argc, char
> **argv)
> >
> opts.unicode_app = 1;
> >
> else if (strcmp("-m32", argv[i]) == 0)
> >
> {
> > +
> if (opts.target_cpu ==
> CPU_x86_64)
> > +
> {
> > +
> const char
> *stdlib32path[] = { "/usr/lib32/wine",
> "/usr/local/lib32/wine", "/lib32/wine" };
>
> lib32 is almost never used in the Linux distros though
I think I read it somewhere that it is a debian-ism. on x86_64 debian, 64-bits libraries are in /lib, and 32-bits are in /lib32 .
>
> e.g. for SUSE:
> /usr/lib is the 32bit path on x86, ppc, s390
> /usr/lib64 the 64bit path on x86_64, ppc64, s390x
>
> Just ia64 is an exception and has /usr/lib (and the compat
> libs somewhere weird).
>
> Ciao, Marcus
>
>
>
More information about the wine-devel
mailing list