Hi, I am using dev-libs/libxslt-1.1.8 (+python) in my own projects, too. Since today, I noticed that I just can't ./configure my own packages - that are written in C++, because lbixslt.m4 does only define CFLAGS="..." and not CXXFLAGS="..." I do not know how they handled it before, but it worked before, now *not*. So, here's my proposal: --- libxslt.m4 2004-07-21 02:57:20.487121647 +0200 +++ libxslt.m4-new 2004-07-21 02:57:11.331886595 +0200 @@ -54,6 +54,7 @@ ac_save_CFLAGS="$CFLAGS" ac_save_LIBS="$LIBS" CFLAGS="$CFLAGS $XSLT_CFLAGS" + CXXFLAGS="$CFLAGS" LIBS="$XSLT_LIBS $LIBS" dnl dnl Now check if the installed libxslt is sufficiently new. @@ -158,6 +159,7 @@ else echo "*** Could not run libxslt test program, checking why..." CFLAGS="$CFLAGS $XSLT_CFLAGS" + CXXFLAGS="$CFLAGS" LIBS="$LIBS $XSLT_LIBS" AC_TRY_LINK([ #include <libxslt/xslt.h> Otherwise, *NO* automake'd C++ package is able to use this .m4 script. I think, this is a "major" severity, since it affects any c++ package directly depending on libxslt (and using libxslt.m4 config script). I did *NOT* report this BUG (as it definitely is one) to the original developer due lag of time. I'd be happy, if someone of you feed them a mail. Greets, Christian Parpart.
Created attachment 36447 [details, diff] libxslt.m4 patch um, sorry, there must be some more *CXXFLAGS-lines to be inserted, see the patch attached. regards, Christian Parpart.
please file this upstream as well, patch in ~on 1.1.8-r1
