Le 29 janv. 09 à 19:22, Ralf Wildenhues a écrit :
- nuke warnings in the wrappers
The patch at the end of
http://lists.gnu.org/archive/html/libtool/2008-12/msg00069.html
For this one I'd prefer if Charles and/or Peter took care of it, they
have a bunch of changes in this area and some discussion going on.
Actually, I'd prefer to just be able to say "go!" once y'all have
agreed
on a common set of changes. :-)
Maybe there are other means to address these warnings. At some
other place of our project, it seems that #defining
_CRT_SECURE_NO_DEPRECATE, _CRT_NONSTDC_NO_DEPRECATE,
_AFX_SECURE_NO_WARNINGS, and _ATL_SECURE_NO_WARNINGS might
suffice.
Whatever the choice, this (msvc) is a real nuisance.
- Bootstrap failures
http://lists.gnu.org/archive/html/bug-libtool/2008-11/msg00098.html
I suggest adding the following macros to lt~obsolete.m4 to stop
the boostrap nightmare.
I agree that this needs fixing, and in fact this is the single most
important issue to be addressed before 2.2.8. However, I really want
to be able to reproduce it and thus understand the failure, and I
haven't so far. I want to ensure that we cannot make this mistake
again.
My aclocal log seems to be clear about the issue.
I have also the following patch that I don't remember if I
sent it.
I don't remember you having sent it.
Subject: [PATCH] Fix func_exec_init.
* tests/defs.m4sh (func_exec_init): Instead of using the undefined
my_dir, call func_dirname_and_basename and use its result.
(func_make): For consistency, don't use the useless local variable
my_dir.
This is ok, please push.
In the make-check-then-git-push pipe.
