ABI unification

[Dave Korn]

Jay wrote on 07 August 2008 00:07:

> First, I meant a uniform compile time ABI.
> Not an ability to mix and match at runtime.

  This thing ...

> I simply want to compile two .objs with the different
> compilers and headers, and then link them together,
> trafficing in whatever.

... and this thing completely contradict each other.  What's the use of
being able to link them together if they don't work at runtime?

> Anyway, given the errno.h mismatches, it's not possible without a
> breaking change. 

  It's pointless in either case.

> Perhaps this can be "fixed" for any non-x86 Cygwin port?

  The very concept of a non-x86 Cygwin port is meaningless nonsense.  You
need to do a bit more homework.  I suggest you start by reading the first
sentence on the first page at http://cygwin.com/.  It should explain to you
why there's never going to be any "non-x86 Cygwin port".

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/