[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Dagobert Michelsen
Subject: Re: [ANN] m4-1.4.17 released [stable]
Date: Mon, 23 Sep 2013 17:07:59 +0200

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:

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

However, when I browse git the automatic detection of .git is not in there:
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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]