[2003-01-09] David Abrahams wrote: >Toon Knapen <[EMAIL PROTECTED]> writes: > >> On Thursday 09 January 2003 12:12, Rene Rivera wrote: >>> It's doesn't because I haven't had time to add it since the toolset >>> appeared in Boost.Build ;-) I'll try and add ASAP. ... Question on this... >>> Is it a possibility to install only the C compiler (cc) without the C++ >>> compiler (aCC)? I'm asking to see if I can use the presense of "aCC" as an >>> indicator that it's all installed. >> >> I guess cc is installed by default (like on all unices) and aCC is a >> commerical product. So cc is always there and aCC is'nt. >> >> Anyway, to compile jam_src you can use cc (with the -Ae option though) as >> you can see in the Jambase. > >Yeah, I think on Unix, defaulting to cc unless the script knows better >is a god idea. It would've prevented this issue with getting aCC to >build it in the first place. That's what the Perforce makefile does, >too.
OK that seems like a good idea. I'll add generic Unix cc toolset for building bjam. But for aCC, can one of you tell what the output of 'uname' is. At least I can test that in this case. -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
