2015-05-16 11:19 GMT+03:00, [email protected] <[email protected]>: >>> We know (modulo my laziness to express the knowhow in a "traditional" >>> notation) how to get a well working cfront-3.0. >> There is a problem with build system (makefiles defines) which are not >> friendly. > Attaching the description which should be sufficient to build 3.0.3.
Nice :-) >>> An easier but much less certain way would be to try to talk to someone >>> at AT&T - this would be certainly a lot more efficient, _if_ it could >>> work. >> Easiest way to start this process is to place cfront project on the >> github (for example). > Sounds reasonable > Go ahead and let's see what AT&T says to github (especially if you > do not prominently state "computer history research" in the README, > I guess you will want to). README with "computer history research" mention? No problem. What more? Allowing to do so on current linux distribution? But a some usefull job need be done before doing so. Related to the changes history. For example, I want to start with c++ files which have .C extension and not .c Or this can be done later? PS: there are many good compilers (languages) which compiles to plain c. But not having such for c++ is not so good. _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
