From: Brent W. <we...@aj...> - 2000-08-26 04:11:47
|
Urk - I think the correct change to make is to add --disable-gcc, or alter the --enable-gcc rule to honor the CC variable. 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? >>>Mo DeJong said: > There has been a lot of talk lately about the --enable-gcc option. > > Some people loved it, some folks hated it. Well, for those > of you that hated it, you can rejoice as I just did a commit > of a patch that removes all trace of the --enable-gcc flag! > > If you loved --enable-gcc, feel free to flame me :) > I hope this did not break anyones build, but this > was a big change so I might have broken something. > > The new rule is to set the CC env var to tell configure > what compiler you want to use. > (actually this is the old rule, Tcl just did not follow it). > > 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. > -- Brent Welch <we...@aj...> http://www.ajubasolutions.com Scriptics changes to Ajuba Solutions scriptics.com => ajubasolutions.com -- The TclCore mailing list is sponsored by Ajuba Solutions To unsubscribe: email tcl...@aj... with the word UNSUBSCRIBE as the subject. |