Re: FYI: compensate compiler warnings and boilerplate (branch-1-5)

2005-06-09 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Mon, Apr 18, 2005 at 07:07:54PM CEST: * Gary V. Vaughan wrote on Mon, Apr 11, 2005 at 05:08:06PM CEST: Ralf Wildenhues wrote: _LT_TAGVAR(lt_simple_*_test_code, $1)=foo;\n Which implies: # _LT_*_BOILERPLATE([TAG]) I don't have any idea how to proceed

FYI: compensate compiler warnings and boilerplate (branch-1-5)

2005-04-18 Thread Ralf Wildenhues
Hi Gary, * Gary V. Vaughan wrote on Mon, Apr 11, 2005 at 05:08:06PM CEST: Ralf Wildenhues wrote: Ah, you mean using _LT_TAGVAR without also using _LT_TAGDECL, right? Yes, _LT_TAGVAR abstracts per language variables, _LT_TAGDECL pushes them through config.status. Thanks.

Re: compensate compiler warnings and boilerplate

2005-04-11 Thread Ralf Wildenhues
Hi Gary, * Gary V. Vaughan wrote on Mon, Apr 11, 2005 at 10:33:25AM CEST: Ralf Wildenhues wrote: Two problems I want to kill with this patch: - picky compiler(s|flags) warn about innocuous code and thus make the `-c -o' and the pic_flag tests (among others) spuriously fail. - some

Re: compensate compiler warnings and boilerplate

2005-04-11 Thread Gary V. Vaughan
Hallo Ralf! Ralf Wildenhues wrote: Ah, you mean using _LT_TAGVAR without also using _LT_TAGDECL, right? Yes, _LT_TAGVAR abstracts per language variables, _LT_TAGDECL pushes them through config.status. Anyway, the changes you want me to make make more other changes necessary. Will look into

compensate compiler warnings and boilerplate

2005-04-10 Thread Ralf Wildenhues
Two problems I want to kill with this patch: - picky compiler(s|flags) warn about innocuous code and thus make the `-c -o' and the pic_flag tests (among others) spuriously fail. - some proprietary compilers output boilerplate every time. Same effect on libtool tests. A third, similar problem