------- Additional Comments From corsepiu at gcc dot gnu dot org 2004-11-25 04:41 ------- (In reply to comment #3) >> So the actual question is: >>What has set LIMITS_H_TEST to "true" before, and why isn't it set true >> anymore?
I believe to have found the cause (testing is still in progress). LIMITS_H_TEST is being set true in config/t-rtems, but a typo in my patch has prevented config/t-rtems from being picked up (cf. below). > Is fixproto being set to yes somehow in > config.gcc for avr-rtems? Yes, there is a second, bogus use_fixproto for avr-*-* in config.gcc. I'll propose it to be removed, soon. > Do you have a special stanza > in your config.gcc for that target that is not checked in? No, the versions I was comparing actually were my local version before having commited the patch and the version after I commited the patch. However, this hint was the key to the cause: A typo had crept into the patch I had checked in (tmake_files= instead of tmake_file=), probably having crept in when having transferred the patch from my testing cvs-tree (with further patche s applied) to my submission cvs-tree. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |corsepiu at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED GCC target triplet|*-rtems* |avr-*-rtems* http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18643