From: Mo D. <md...@cy...> - 2000-08-26 20:08:47
|
On Fri, 25 Aug 2000, Brent Welch wrote: > Urk - I think the correct change to make is to add --disable-gcc, Then why not add a --enable-cc and --disable-cc. You would also need a --enable-cl and --disable-cl by that logic. > or alter the --enable-gcc rule to honor the CC variable. I did that already. It was a reasonable solution for 8.3, but for 8.4 there is no reason to keep --enable-gcc in the code. > It seems easy > to come up with a solution that handles both without breaking all the > CONFIG > scripts that I have. I'm sure we are not the only company with build > environments > that have --enable-gcc embedded somewhere. Why break it? Your scripts probably wont break. If you passed --enable-gcc before, it will just get silently ignored and gcc will be picked as the default if it can be found on the path. Mo DeJong Red Hat Inc -- The TclCore mailing list is sponsored by Ajuba Solutions To unsubscribe: email tcl...@aj... with the word UNSUBSCRIBE as the subject. |