------- Comment #5 from nicolai dot stange at zmaw dot de 2010-09-04 19:31 ------- (In reply to comment #4) > The problem with the configure is the libgcc specs are very target dependent. Yes, and that's the reason why I think that others might benefit from those configure-options.
Another remark that I forgot in my first post: There's already an --with-specs option that sets some specs for something (I don't know for what exactly, but it can't be used to set link options, I already tried it: Some other tools complain about unknown options). If your concern is about the work, not about the additional complexicity: I would do the work to add those options, just tell me - For which specs I should do it (all or just link_libgcc) - How do you want the CPP-Macros for the values of the configure-options to be named? - Should those values override or be appended/prepended to the platform-specific default-specs? * If appended/prepended: How do you want the CPP-macro for the concatenated, final spec string to be named? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45508
