at the macro generates) is not supposed to be done. I
think it should work (did not check yet)...
Regards,
Christophe.
AC_CACHE_CHECK macro at the appropriate place, so
now the check will not be re-run if the user enabled autoconf's cache.
Signed-off-by: Christophe CURIS
---
m4/ld-version-script.m4 | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/m4/ld-ve
Hello,
Apparently this patch did not make it to the repository, any feedback about it?
I personally have no push permission to do it myself.
I'm re-sending the patch, because with the recent copyright year updates the old
one would not apply anymore.
Regards,
Christophe.
Hello,
Please find here a new version of the patch, the original one unintentionally
broke the function when detecting error on invalid map file.
My apologies for the noise,
Best regards,
Christophe.
m4/ld-version-script.m4 | 36 ++--
1 file changed, 18
AC_CACHE_CHECK macro at the appropriate place, so
now the check will not be re-run if the user enabled autoconf's cache.
Signed-off-by: Christophe CURIS
---
m4/ld-version-script.m4 | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/m4/ld-ve
AC_CACHE_CHECK macro at the appropriate place, so
now the check will not be re-run if the user enabled autoconf's cache.
Signed-off-by: Christophe CURIS
---
m4/ld-version-script.m4 | 34 +-
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/m4/ld-ve
Hey,
On Wed, Aug 14, 2013 at 05:33:07PM -0600, Eric Blake wrote:
> As reported by Christophe Fergeau and others, use of the
> warnings modules is awkward when probing for negative
> warning flags. For example, clang recognizes
> -Wno-unused-command-line-argument, but gcc does not;
&g
On Wed, Aug 14, 2013 at 06:29:14AM -0600, Eric Blake wrote:
> On 08/14/2013 01:58 AM, Christophe Fergeau wrote:
> > Hi,
> >
> > gcc handling of -Wno- flags is different from its handling of -W
> > flags as described in
> > http://gcc.gnu.org/onlinedocs/g
to issues like
http://www.redhat.com/archives/libvir-list/2012-April/msg0.html
I guess that when gl_WARN_ADD is used with -Wno-unknown-warning, it should
test as well the corresponding -Wunknown-warning flag, though I don't know
how well this will work with non-gcc compile
