Hello All,
as I have stated many times, 'pcc.c' is not in the source tarball - I'm still
waiting for a confirmation.
Now I think I understand the "whole" picture.
'cc' wrapper, according to my observation, doesn't work except maybe with
MSVC - I simply haven't tried it yet with MSVC.
OTOH, there is native 'cc' under Linux:
ls -ltr `which cc`
lrwxrwxrwx 1 root root 7 2008-10-08 02:25 /usr/bin/cc -> gcc-4.2
.
And that native 'cc' pretty much works with UWIN under Linux - quite a lot
of stuff can be built with it, though not everything, and the targets at
least in part fail due to reasons not related to compiler.
Since UWIN and its 'cc' doesn't work with non-MSVC compilers, had UWIN
'cc' been built under Linux, it would have screwed up the rest of the
build - because it doesn't work.
So, it looks it's not in the source tarballs for this reason.
Now, if it's the truth, source tarballs should be organized differently -
there should be a separate one for UWIN 'cc'.
And this truth should be prominently written on the UWIN website - too
much effort has to be spent just to come to this truth, so why should
every newcomer spend this effort ?
Thanks,
Sergei.
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
