Re: RFC: x86_64-pc-mingw64 and getting it mapped out

On Sun, Jul 28, 2013 at 4:12 AM, Keith Marshall wrote:
> On 27/07/13 12:51, Earnie Boyd wrote:
>> I would like to suggest the following patch to the config maintainer,
>>> any objection?  I need something better than "It will break my current
>>> environment."; such is the life of programming in an "improving"
>>> world.
>
> I do not support this; I think it is a terrible idea.  It was wrong when
> Kai did something similar; it is still wrong today.  I've made my POV
> clear; I am not going to continually repeat myself.
>

I do not know what you mean by "Kai did something similar".

> What we have today is clean, simple and effective.  If you want to
> ignore the KISS principle, and so make it complicated and ultimately
> unworkable, then perhaps it is time for me to bid you adieu.

I do not know what you mean by "What we have today is clean, simple
and effective."

I am not seeing "unworkable" nor am I seeing that I'm ignoring the
KISS principle.

In fact I'm trying to work a KISS principle for providing libraries
with varying bitness and architecture to be used by a cross compiler.
Keeping the mingw32/mingw64 in the triplet is just a misnomer and can
be misleading.

What we have today is /mingw/mingw32 for the hosted libraries.  Are
you stating that you want to keep that over /mingw/i686-pc-mingw?
Here's the harm in it, the i686 could be i486 or i586 but the
libraries i'm building are hosted for i686.  Now someone thinking they
can build software for i586 with the libraries in /mingw/mingw32 will
be out of luck.

And I can imagine that there could be a 64bit Windows OS on some other
chip set than x86_64.  So I want ot have /mingw/x86_64-pc-mingw for
that instead of /mingw/mingw64 for the same harm reason for mingw32.

Can you debunk what I'm saying about the architecture variance being
harmful in using /mingw/mingw32 and /mingw/mingw64?  If so then I'll
be fine with leaving it.  However, I will suggest changing the default
guess from i386 to i686 since that is where most of the world is.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk