Hello Duncan, Wednesday, May 3, 2006, 10:21:14 PM, you wrote: > Simon suggested that instead of hard-coding these flags into ghc that we put > them in the rts package and that we write a program to re-generate the rts > package configuration. This program would be used at install time and could > be used later to update ghc's gcc settings if the gcc version changes.
may be it is possible to run "gcc -v" at start of each compilation, check the result if gcc version was changed - run this reconfiguration utility? although i may be completely wrong with this suggestion - i don't know unix at all. just for my windows box "installation" of gcc is more like to unpacking archive and changing the PATH - there is no moment when this ghc-autoconf utility will run automatically and user may don't know about it or just forgot, so autochecking seems to more reliable way; it's also better if one sometimes just goes to using other gcc version by changing PATH. although, anyway, in Windows gcc is packed together with ghc itself -- Best regards, Bulat mailto:[EMAIL PROTECTED] _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
