chromatic wrote: > In a freshly-configured Parrot, config_lib.pasm is 18k. Part of the build > process turns this file into a frozen PMC. During global initialization, > Parrot thaws this into a Hash PMC used in the root set -- the Parrot > configuration Hash. > > This Hash contains such useless information as which warning flags the > compiler > used to build Parrot supports (61 per my count), ExtUtils::MakeMaker commands > used in Makefiles on platforms which do not have native commands for touch or > chmod (for example), and system library symbols (86 per my count).
Okay. The information might be redundant, but it was still being used. In r38830, I reverted your r38804 patch because it caused build failures on darwin/OSX; apparently pbc_to_exe is compiled by a tool written in PIR which was relying on the "ccflags" variable from config_lib.pasm. When your patch made that variable go poof, it tried to run gcc with very mimimal arguments, and we were relying on an -I option to find system headers, so the build broke. See TT #675. I've since made a patch that reapplies r38804 with a whitelist for a small group of useful-looking items, but... > Note that all of this information is also available from config.pir. So instead of the patch I mentioned above, I guess we should convert tools/dev/pbc_to_exe.pir to use config.pir instead of config_lib.pasm. That seems reasonable to me, I'll see what I can do. Mark _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
