Hi Sergei, UWIN won't build without AST. It is AST that includes the pcc.c you seek. You should find a copy of this file when you have unpacked the correct tar bundle at /opt/ast/src/cmd/cc/pcc.c.
Just to clarify matters, the UWIN website FAQ at http://www.research.att.com/sw/tools/uwin/ does mention a number of times that the "cc" provided by UWIN is simply a wrapper for your platform's compiler. It also prominently states that the actual platform-specific working compiler is not provided by UWIN in any form. The UWIN "cc" is provided merely to simplify and unify the various compiler-specific command line options into a compiler-independent common denominator so that the same build scripts will work with any of the supported compilers on any of the supported platforms. Trying to use your platform-specific cc as a replacement for UWIN cc will not work -- at all. My attempts to bootstrap an earlier version of UWIN without already having a working, running UWIN environment to begin with (under Windows Vista, no less) are documented in the archives of the UWIN mailing list. Suffice it to say, I was rather unsuccessful at getting compiling AST/UWIN from scratch using *any* compiler without having an already working AST/UWIN to build with. For additional information about AST, UWIN, and the sophisticated build & packaging system (including iffe, nmake [No, Not The Microsoft NMAKE - the ATT nmake.], ksh, the 3D file system, the package script, etc.), you need to do a fair amount of reading on the website, and also in the mailing-list archives. Be sure to look at the mailing lists for both AST and UWIN, user and developer. In my opinion, you need to compare your goals and expectations for UWIN against the copious amounts of documentation available for AST/UWIN/KSH/the ATT Build System and see whether or not UWIN matches up better than CYGWIN or MinGW/MSYS for your needs. Good Luck, - - - Philip Mason -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergei Steshenko Sent: Friday, May 22, 2009 4:03 PM To: [email protected] Subject: [uwin-users] a wild guess on 'cc', 'pcc', MSVC,UNIXish OSes and Windows 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 _______________________________________________ uwin-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/uwin-users
