On Thu, 10 Aug 2006 17:53:54 +0200 "[LoN]Kamikaze" <[EMAIL PROTECTED]> mentioned:
> Ports that do not set CC in their configure target don't get informed about > the value of CC because it is only appended to MAKE_ENV for the configure > target. I think it doesn't present a big problem for i don't know a single port that sets up value of CC variable in it's Makefile. Thus, we have only 3 scenarios: 1) CC is set up on make commandline (e.g. make CC=xxx). In that case make program will export value of CC to enviropment and every make program executed will receive it 2) CC is exported to sheel enviropment. This case is obvious. 3) CC was defined in make.conf. In that case if GNU make isn't used in do-build stage make will re-read make.conf and, thus, honor CC's value. I think we should not consider GNU make's case - it's used much less often, than our original make program. -- Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]> Россия, Москва http://mbsd.msk.ru -------------------------------------------------------------------- If the facts don't fit the theory, change the facts. -- A. Einstein -------------------------------------------------------------------- PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581
signature.asc
Description: PGP signature
