[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Combining 32-bit and 64-bit suport (was: gcc

From: Tony Theodore
Subject: Re: [Mingw-cross-env-list] Combining 32-bit and 64-bit suport (was: gcc 4.5 error)
Date: Wed, 21 Apr 2010 21:07:05 +1000

On 21 April 2010 02:29, Volker Grabsch <address@hidden> wrote:
> Why do we need different library directories at all? Since we
> have different target prefixes, everything should go into "lib".
> That's it. So we'd have:
>    usr/i686-w64-mingw32/lib/
> and
>    usr/x86_64-w64-mingw32/lib/
> What's the problem?

I think we're saying the same thing, it's better to run each as a
separate target - it's only the multi-lib scenario that needs to have
lib32 or lib64.

> BTW, why does the 64-bit prefix end with "...-mingw32" instead
> of "...-mingw64" or just "...-mingw"?
> And why is the vendor noted as "...-w64-..." instead of the
> more usual "...-pc-..."?
> Is it just a matter of taste of the mingw-w64 people, or are
> there good reasons I should know about?

I'm not sure, it's always struck me as odd but I didn't think too much
about it. There's mixed messages from gcc [1] and mingw-w64 [2],
should we try using the *-pc-* vendor?

>> Another future problem we may have is coditionally patching/excluding
>> packages based on the build type.
> I really hope that we can fix all packages in a way that they
> build successfully on both platforms, 32-bit and 64-bits.

That will be possible eventually, though I imagine there are still a
handful of packages that are 32-bit only. Maybe it's more the ability
to do an unattended build, so you can leave it running and come back
to see what's failed.

Still, I think there will be releases in the future with known
failures more than the current nsis on certain x64 systems. I guess
it's a matter of seeing how many there are.

>> > BTW, this discussion shows the importance of the "i686-pc-mingw32-"
> Okay, so I'll fix that.

I just had a thought that it may be possible to run the current
i686-pc-mingw32 alongside the new *-w64-* targets. Maybe create
$(TARGET)-gcc.mk files and change PKG_DEPS accordingly? One of the
*-w64-* files can simply be a symlink.

I'll move the usr/local to a new thread.



[1] http://gcc.gnu.org/install/specific.html#windows

reply via email to

[Prev in Thread] Current Thread [Next in Thread]