Re: [ANN] m4-1.4.17 released [stable]

[Dagobert Michelsen]

Hi Erik,

Am 23.09.2013 um 16:27 schrieb Paul Eggert <address@hidden>:
> Eric Blake wrote:
>> On 09/22/2013 07:08 AM, Dagobert Michelsen wrote:
>> 
>>>> 
>>>> The latest release is no longer compilable with Sun Studio 12.3 compiler 
>>>> as it
>>>> automatically uses GCC-specific flags:
> 
> I don't observe this behavior on my host (Sun Studio 12.3,
> Solaris 10 sparc).  I get the bad behavior only if I run
> 'configure' with the --enable-gcc-warnings option, and
> a simple workaround is to not use that option.

I didn't enable gcc-warnings, but as it turns out this flag is automatically
enabled when $srcdir/.git is present:

AC_ARG_ENABLE([gcc-warnings],
  [AS_HELP_STRING([--enable-gcc-warnings],
                  [turn on lots of GCC warnings (for developers)])],
  [case $enableval in
     yes|no) ;;
     *)      AC_MSG_ERROR([bad value $enableval for gcc-warnings option]) ;;
   esac
   gl_gcc_warnings=$enableval],
  [if test -d "$srcdir"/.git; then
     gl_gcc_warnings=yes
   else
     gl_gcc_warnings=no
   fi]
)


However, when I browse git the automatic detection of .git is not in there:
  
http://git.savannah.gnu.org/gitweb/?p=m4.git;a=blob;f=configure.ac;h=2fe6d9e8189d4083b58ba10bfbbe558da15f393b;hb=c09a187c50f2f74e89d4d0991bdbd2c6846cc707
By coincidence we use git to apply patches in our build system
to upstream sources if necessary, so this is the thing that
confuses the build. When I disable using git in our buildsystem
the compilation works fine. I would prefer a system that enabled flags
explicitly and not by inspecting side effects but I can understand the
current behaviour.


Best regards

  -- Dago

smime.p7s
Description: S/MIME cryptographic signature