GNU bug report logs - #14706
automake 1.14 test failure on OS X 10.6.8

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 14706 in the body.
You can then email your comments to 14706 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Diab Jerius <dj <at> head.cfa.harvard.edu>
To: bug-automake <at> gnu.org
Subject: automake 1.14 test failure on OS X 10.6.8
Date: Mon, 24 Jun 2013 10:02:46 -0400

[Message part 1 (text/plain, inline)]

Hi,

I received a test failure of automake 1.14 on OS X 10.6.8.

Attached is the test log.

Diab

[test-suite.log.bz2 (application/x-bzip, attachment)]

Message #8 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Diab Jerius <dj <at> head.cfa.harvard.edu>
Cc: 14706 <at> debbugs.gnu.org
Subject: (was Re: bug#14706: automake 1.14 test failure on OS X 10.6.8
Date: Tue, 25 Jun 2013 00:09:42 +0200

severity 14706 minor
thanks

On 06/24/2013 04:02 PM, Diab Jerius wrote:
> Hi,
>
Hi, and thanks for the report!

> I received a test failure of automake 1.14 on OS X 10.6.8.
> 
> Attached is the test log.
> 
> Diab
>

Here I copy the relevant portion of the log, for easier reference:
> 
> FAIL: t/depcomp2
> ================
>
> Running from installcheck: no
> Test Protocol: none
> PATH = /tmp/automake-1.14/t/wrap:/tmp/automake-1.14/t/ax:<snip>
> ++ pwd
> /tmp/automake-1.14/t/depcomp2.dir
> + cat
> + cat
> + rm -f depcomp
> + mkdir subdir
> + cat
> + :
> + aclocal-1.14 -Werror
> + automake-1.14 --foreign -Werror -Wall --add-missing
> + autoconf
> + ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> checking whether /usr/bin/make sets $(MAKE)... yes
> checking whether /usr/bin/make supports nested variables... yes
> checking for gcc... cc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether cc accepts -g... yes
> checking for cc option to accept ISO C89... none needed
> checking whether cc understands -c and -o together... yes
> checking for style of include used by /usr/bin/make... GNU
> checking dependency style of cc... none
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating subdir/Makefile
> config.status: executing depfiles commands
> + cat stderr
> rm: conftest.dSYM: is a directory
>
Hmm, seems this is an old issue in Autoconf:

 <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
 <http://mail.python.org/pipermail/python-dev/2008-April/078807.html>

I'll add a workaround to the automake testsuite to avoid the spurious
failure (spurious since it's due to a buglet/limitation in autoconf,
not in automake).  I'm about to log off now, so the patch proper should
be poster tomorrow or the day after.

> + test '!' -s stderr
> + am_exit_trap 1
> + exit_status=1
> + set +e
> + cd /tmp/automake-1.14
> + test none = tap
> + case $am_explicit_skips in
> + test 1 -eq 0
> + keep_testdirs=yes
> + am_keeping_testdirs
> + case $keep_testdirs in
> + return 0
> + set +x
> depcomp2: exit 1

Thanks,
  Stefano

Message #13 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Diab Jerius <dj <at> head.cfa.harvard.edu>
Cc: 14706 <at> debbugs.gnu.org, "bug-autoconf <at> gnu.org" <bug-autoconf <at> gnu.org>,
 "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Mac OS X gcc and bogus warnings about *.dSYM directories (was: Re:
 bug#14706: automake 1.14 test failure on OS X 10.6.8)
Date: Thu, 27 Jun 2013 14:45:02 +0200

tags 14706 + patch
thanks

[+cc bug-autoconf]

Reference:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14706>

On 06/25/2013 12:09 AM, Stefano Lattarini wrote:
> severity 14706 minor
> thanks
> 
> On 06/24/2013 04:02 PM, Diab Jerius wrote:
>> Hi,
>>
> Hi, and thanks for the report!
> 
>> I received a test failure of automake 1.14 on OS X 10.6.8.
>>
>> Attached is the test log.
>>
>> Diab
>>
> 
> Here I copy the relevant portion of the log, for easier reference:
>>
>> FAIL: t/depcomp2
>> ================
>>
>> Running from installcheck: no
>> Test Protocol: none
>> PATH = /tmp/automake-1.14/t/wrap:/tmp/automake-1.14/t/ax:<snip>
>> ++ pwd
>> /tmp/automake-1.14/t/depcomp2.dir
>> + cat
>> + cat
>> + rm -f depcomp
>> + mkdir subdir
>> + cat
>> + :
>> + aclocal-1.14 -Werror
>> + automake-1.14 --foreign -Werror -Wall --add-missing
>> + autoconf
>> + ./configure
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... ./install-sh -c -d
>> checking for gawk... no
>> checking for mawk... no
>> checking for nawk... no
>> checking for awk... awk
>> checking whether /usr/bin/make sets $(MAKE)... yes
>> checking whether /usr/bin/make supports nested variables... yes
>> checking for gcc... cc
>> checking whether the C compiler works... yes
>> checking for C compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... no
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether cc accepts -g... yes
>> checking for cc option to accept ISO C89... none needed
>> checking whether cc understands -c and -o together... yes
>> checking for style of include used by /usr/bin/make... GNU
>> checking dependency style of cc... none
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: creating subdir/Makefile
>> config.status: executing depfiles commands
>> + cat stderr
>> rm: conftest.dSYM: is a directory
>>
> Hmm, seems this is an old issue in Autoconf:
> 
>  <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
>  <http://mail.python.org/pipermail/python-dev/2008-April/078807.html>
> 
> I'll add a workaround to the automake testsuite to avoid the spurious
> failure (spurious since it's due to a buglet/limitation in autoconf,
> not in automake).  I'm about to log off now, so the patch proper should
> be poster tomorrow or the day after.
> 
Here is the promised patch.  Can you confirm it works for you?

I'm adding bug-autoconf in CC because, from the first discussion linked
above, it appears the original issue had been fixed, but it must have
been unwittingly reintroduced in the meantime :-(  Maybe some autoconfer
wants to take a fresh look at the problem ...

Thanks,
  Stefano

---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ----

From 3759f24379c98b984a56b52c7d23a2dfbf36efcf Mon Sep 17 00:00:00 2001
Message-Id: <3759f24379c98b984a56b52c7d23a2dfbf36efcf.1372337066.git.stefano.lattarini <at> gmail.com>
From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Date: Thu, 27 Jun 2013 14:43:12 +0200
Subject: [PATCH] tests: avoid a spurious failure on MacOS X 10.6.8

Fixes automake bug#14706.

* t/depcomp2.sh: Strip, from the redirected ./configure stderr, the
possible error message "rm: conftest.dSYM: is a directory", generated
by cleanup code that doesn't cater to the existence of *.dSYM
directories sometimes created by the compiler on MacOS X.  This
"massaging" of ./configure stderr is legitimate, since the spurious
error message is due not to automake-related code, but to a know
buglet/limitation of either Autoconf or Mac OS X bundles gcc:
<http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
Actually, from that link it appears that the original Autoconf issue
had been fixed, but it must have been re-introduced in the meantime :-(

Signed-off-by: Stefano Lattarini <stefano.lattarini <at> gmail.com>
---
 t/depcomp2.sh | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/t/depcomp2.sh b/t/depcomp2.sh
index 2182164..3eba12d 100644
--- a/t/depcomp2.sh
+++ b/t/depcomp2.sh
@@ -45,6 +45,9 @@ $AUTOMAKE --add-missing
 $AUTOCONF
 ./configure 2>stderr || { cat stderr >&2; exit 1; }
 cat stderr >&2
-test ! -s stderr
+# Ignore warning messages sometimes seen on Mac OS X; they are
+# not automake's fault anyway, but either autoconf's or Mac's.
+sed '/rm:.* conftest\.dSYM/d' stderr >stderr2
+test -s stderr2 && { cat stderr2; exit 1; }

 :
-- 
1.8.3.1.448.gfb7dfaa

Message #18 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Diab Jerius <dj <at> head.cfa.harvard.edu>
Cc: 14706 <at> debbugs.gnu.org,
 "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM
 directories
Date: Sun, 07 Jul 2013 10:30:06 +0100

[Removing bug-autoconf from CC]

Reference:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14706>

On 06/27/2013 01:45 PM, Stefano Lattarini wrote:
> tags 14706 + patch
> thanks
> 
> On 06/25/2013 12:09 AM, Stefano Lattarini wrote:
>> severity 14706 minor
>> thanks
>>
>> On 06/24/2013 04:02 PM, Diab Jerius wrote:
>>> Hi,
>>>
>> Hi, and thanks for the report!
>>
>>> I received a test failure of automake 1.14 on OS X 10.6.8.
>>>
>>> Attached is the test log.
>>>
>>> Diab
>>>
>>
>> Here I copy the relevant portion of the log, for easier reference:
>>>
>>> FAIL: t/depcomp2
>>> ================
>>>
>>> Running from installcheck: no
>>> Test Protocol: none
>>> PATH = /tmp/automake-1.14/t/wrap:/tmp/automake-1.14/t/ax:<snip>
>>> ++ pwd
>>> /tmp/automake-1.14/t/depcomp2.dir
>>> + cat
>>> + cat
>>> + rm -f depcomp
>>> + mkdir subdir
>>> + cat
>>> + :
>>> + aclocal-1.14 -Werror
>>> + automake-1.14 --foreign -Werror -Wall --add-missing
>>> + autoconf
>>> + ./configure
>>> checking for a BSD-compatible install... /usr/bin/install -c
>>> checking whether build environment is sane... yes
>>> checking for a thread-safe mkdir -p... ./install-sh -c -d
>>> checking for gawk... no
>>> checking for mawk... no
>>> checking for nawk... no
>>> checking for awk... awk
>>> checking whether /usr/bin/make sets $(MAKE)... yes
>>> checking whether /usr/bin/make supports nested variables... yes
>>> checking for gcc... cc
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables...
>>> checking whether we are cross compiling... no
>>> checking for suffix of object files... o
>>> checking whether we are using the GNU C compiler... yes
>>> checking whether cc accepts -g... yes
>>> checking for cc option to accept ISO C89... none needed
>>> checking whether cc understands -c and -o together... yes
>>> checking for style of include used by /usr/bin/make... GNU
>>> checking dependency style of cc... none
>>> checking that generated files are newer than configure... done
>>> configure: creating ./config.status
>>> config.status: creating Makefile
>>> config.status: creating subdir/Makefile
>>> config.status: executing depfiles commands
>>> + cat stderr
>>> rm: conftest.dSYM: is a directory
>>>
>> Hmm, seems this is an old issue in Autoconf:
>>
>>  <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
>>  <http://mail.python.org/pipermail/python-dev/2008-April/078807.html>
>>
>> I'll add a workaround to the automake testsuite to avoid the spurious
>> failure (spurious since it's due to a buglet/limitation in autoconf,
>> not in automake).  I'm about to log off now, so the patch proper should
>> be poster tomorrow or the day after.
>>
> Here is the promised patch.  Can you confirm it works for you?
> 
> I'm adding bug-autoconf in CC because, from the first discussion linked
> above, it appears the original issue had been fixed, but it must have
> been unwittingly reintroduced in the meantime :-(  Maybe some autoconfer
> wants to take a fresh look at the problem ...
> 
> Thanks,
>   Stefano
> 
> ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ----
> 
> From 3759f24379c98b984a56b52c7d23a2dfbf36efcf Mon Sep 17 00:00:00 2001
> Message-Id: <3759f24379c98b984a56b52c7d23a2dfbf36efcf.1372337066.git.stefano.lattarini <at> gmail.com>
> From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
> Date: Thu, 27 Jun 2013 14:43:12 +0200
> Subject: [PATCH] tests: avoid a spurious failure on MacOS X 10.6.8
> 
> Fixes automake bug#14706.
> 
> * t/depcomp2.sh: Strip, from the redirected ./configure stderr, the
> possible error message "rm: conftest.dSYM: is a directory", generated
> by cleanup code that doesn't cater to the existence of *.dSYM
> directories sometimes created by the compiler on MacOS X.  This
> "massaging" of ./configure stderr is legitimate, since the spurious
> error message is due not to automake-related code, but to a know
> buglet/limitation of either Autoconf or Mac OS X bundles gcc:
> <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
> Actually, from that link it appears that the original Autoconf issue
> had been fixed, but it must have been re-introduced in the meantime :-(
> 
> Signed-off-by: Stefano Lattarini <stefano.lattarini <at> gmail.com>
> ---
>  t/depcomp2.sh | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/t/depcomp2.sh b/t/depcomp2.sh
> index 2182164..3eba12d 100644
> --- a/t/depcomp2.sh
> +++ b/t/depcomp2.sh
> @@ -45,6 +45,9 @@ $AUTOMAKE --add-missing
>  $AUTOCONF
>  ./configure 2>stderr || { cat stderr >&2; exit 1; }
>  cat stderr >&2
> -test ! -s stderr
> +# Ignore warning messages sometimes seen on Mac OS X; they are
> +# not automake's fault anyway, but either autoconf's or Mac's.
> +sed '/rm:.* conftest\.dSYM/d' stderr >stderr2
> +test -s stderr2 && { cat stderr2; exit 1; }
> 
>  :
> 
Ping on this?  Can someone test this patch on Mac OS X and
confirm it actually works?

Thanks,
  Stefano

Message #21 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Diab Jerius <dj <at> head.cfa.harvard.edu>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 14706 <at> debbugs.gnu.org,
 "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM
 directories
Date: Mon, 08 Jul 2013 11:34:11 -0400

On Sun, 2013-07-07 at 10:30 +0100, Stefano Lattarini wrote:
> [Removing bug-autoconf from CC]
> 
> Reference:
> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14706>
> 
> On 06/27/2013 01:45 PM, Stefano Lattarini wrote:
> > tags 14706 + patch
> > thanks
> > 
> > On 06/25/2013 12:09 AM, Stefano Lattarini wrote:
> >> severity 14706 minor
> >> thanks
> >>
> >> On 06/24/2013 04:02 PM, Diab Jerius wrote:
> >>> Hi,
> >>>
> >> Hi, and thanks for the report!
> >>
> >>> I received a test failure of automake 1.14 on OS X 10.6.8.
> >>>
> >>> Attached is the test log.
> >>>
> >>> Diab
> >>>
> >>
> >> Here I copy the relevant portion of the log, for easier reference:
> >>>
> >>> FAIL: t/depcomp2
> >>> ================
> >>>
> >>> Running from installcheck: no
> >>> Test Protocol: none
> >>> PATH = /tmp/automake-1.14/t/wrap:/tmp/automake-1.14/t/ax:<snip>
> >>> ++ pwd
> >>> /tmp/automake-1.14/t/depcomp2.dir
> >>> + cat
> >>> + cat
> >>> + rm -f depcomp
> >>> + mkdir subdir
> >>> + cat
> >>> + :
> >>> + aclocal-1.14 -Werror
> >>> + automake-1.14 --foreign -Werror -Wall --add-missing
> >>> + autoconf
> >>> + ./configure
> >>> checking for a BSD-compatible install... /usr/bin/install -c
> >>> checking whether build environment is sane... yes
> >>> checking for a thread-safe mkdir -p... ./install-sh -c -d
> >>> checking for gawk... no
> >>> checking for mawk... no
> >>> checking for nawk... no
> >>> checking for awk... awk
> >>> checking whether /usr/bin/make sets $(MAKE)... yes
> >>> checking whether /usr/bin/make supports nested variables... yes
> >>> checking for gcc... cc
> >>> checking whether the C compiler works... yes
> >>> checking for C compiler default output file name... a.out
> >>> checking for suffix of executables...
> >>> checking whether we are cross compiling... no
> >>> checking for suffix of object files... o
> >>> checking whether we are using the GNU C compiler... yes
> >>> checking whether cc accepts -g... yes
> >>> checking for cc option to accept ISO C89... none needed
> >>> checking whether cc understands -c and -o together... yes
> >>> checking for style of include used by /usr/bin/make... GNU
> >>> checking dependency style of cc... none
> >>> checking that generated files are newer than configure... done
> >>> configure: creating ./config.status
> >>> config.status: creating Makefile
> >>> config.status: creating subdir/Makefile
> >>> config.status: executing depfiles commands
> >>> + cat stderr
> >>> rm: conftest.dSYM: is a directory
> >>>
> >> Hmm, seems this is an old issue in Autoconf:
> >>
> >>  <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
> >>  <http://mail.python.org/pipermail/python-dev/2008-April/078807.html>
> >>
> >> I'll add a workaround to the automake testsuite to avoid the spurious
> >> failure (spurious since it's due to a buglet/limitation in autoconf,
> >> not in automake).  I'm about to log off now, so the patch proper should
> >> be poster tomorrow or the day after.
> >>
> > Here is the promised patch.  Can you confirm it works for you?
> > 
> > I'm adding bug-autoconf in CC because, from the first discussion linked
> > above, it appears the original issue had been fixed, but it must have
> > been unwittingly reintroduced in the meantime :-(  Maybe some autoconfer
> > wants to take a fresh look at the problem ...
> > 
> > Thanks,
> >   Stefano
> > 
> > ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ----
> > 
> > From 3759f24379c98b984a56b52c7d23a2dfbf36efcf Mon Sep 17 00:00:00 2001
> > Message-Id: <3759f24379c98b984a56b52c7d23a2dfbf36efcf.1372337066.git.stefano.lattarinpcommi <at> gmail.com>
> > From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
> > Date: Thu, 27 Jun 2013 14:43:12 +0200
> > Subject: [PATCH] tests: avoid a spurious failure on MacOS X 10.6.8
> > 
> > Fixes automake bug#14706.
> > 
> > * t/depcomp2.sh: Strip, from the redirected ./configure stderr, the
> > possible error message "rm: conftest.dSYM: is a directory", generated
> > by cleanup code that doesn't cater to the existence of *.dSYM
> > directories sometimes created by the compiler on MacOS X.  This
> > "massaging" of ./configure stderr is legitimate, since the spurious
> > error message is due not to automake-related code, but to a know
> > buglet/limitation of either Autoconf or Mac OS X bundles gcc:
> > <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
> > Actually, from that link it appears that the original Autoconf issue
> > had been fixed, but it must have been re-introduced in the meantime :-(
> > 
> > Signed-off-by: Stefano Lattarini <stefano.lattarini <at> gmail.com>
> > ---
> >  t/depcomp2.sh | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/t/depcomp2.sh b/t/depcomp2.sh
> > index 2182164..3eba12d 100644
> > --- a/t/depcomp2.sh
> > +++ b/t/depcomp2.sh
> > @@ -45,6 +45,9 @@ $AUTOMAKE --add-missing
> >  $AUTOCONF
> >  ./configure 2>stderr || { cat stderr >&2; exit 1; }
> >  cat stderr >&2
> > -test ! -s stderr
> > +# Ignore warning messages sometimes seen on Mac OS X; they are
> > +# not automake's fault anyway, but either autoconf's or Mac's.
> > +sed '/rm:.* conftest\.dSYM/d' stderr >stderr2
> > +test -s stderr2 && { cat stderr2; exit 1; }
> > 
> >  :
> > 
> Ping on this?  Can someone test this patch on Mac OS X and
> confirm it actually works?
> 
> Thanks,
>   Stefano

Sorry, I wasn't able to look at this last week.  I'll try to do that
either today or tomorrow.

Diab

Message #24 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Diab Jerius <dj <at> head.cfa.harvard.edu>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 14706 <at> debbugs.gnu.org,
 "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM
 directories
Date: Wed, 17 Jul 2013 12:02:59 -0400

On Sun, 2013-07-07 at 10:30 +0100, Stefano Lattarini wrote:
> [Removing bug-autoconf from CC]
> 
> Reference:
> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14706>
> 
> On 06/27/2013 01:45 PM, Stefano Lattarini wrote:
> > tags 14706 + patch
> > thanks
> > 
> > On 06/25/2013 12:09 AM, Stefano Lattarini wrote:
> >> severity 14706 minor
> >> thanks
> >>
> >> On 06/24/2013 04:02 PM, Diab Jerius wrote:
> >>> Hi,
> >>>
> >> Hi, and thanks for the report!
> >>
> >>> I received a test failure of automake 1.14 on OS X 10.6.8.
> >>>
> >>> Attached is the test log.
> >>>
> >>> Diab
> >>>
> >>
> >> Here I copy the relevant portion of the log, for easier reference:
> >>>
> >>> FAIL: t/depcomp2
> >>> ================
> >>>
> >>> Running from installcheck: no
> >>> Test Protocol: none
> >>> PATH = /tmp/automake-1.14/t/wrap:/tmp/automake-1.14/t/ax:<snip>
> >>> ++ pwd
> >>> /tmp/automake-1.14/t/depcomp2.dir
> >>> + cat
> >>> + cat
> >>> + rm -f depcomp
> >>> + mkdir subdir
> >>> + cat
> >>> + :
> >>> + aclocal-1.14 -Werror
> >>> + automake-1.14 --foreign -Werror -Wall --add-missing
> >>> + autoconf
> >>> + ./configure
> >>> checking for a BSD-compatible install... /usr/bin/install -c
> >>> checking whether build environment is sane... yes
> >>> checking for a thread-safe mkdir -p... ./install-sh -c -d
> >>> checking for gawk... no
> >>> checking for mawk... no
> >>> checking for nawk... no
> >>> checking for awk... awk
> >>> checking whether /usr/bin/make sets $(MAKE)... yes
> >>> checking whether /usr/bin/make supports nested variables... yes
> >>> checking for gcc... cc
> >>> checking whether the C compiler works... yes
> >>> checking for C compiler default output file name... a.out
> >>> checking for suffix of executables...
> >>> checking whether we are cross compiling... no
> >>> checking for suffix of object files... o
> >>> checking whether we are using the GNU C compiler... yes
> >>> checking whether cc accepts -g... yes
> >>> checking for cc option to accept ISO C89... none needed
> >>> checking whether cc understands -c and -o together... yes
> >>> checking for style of include used by /usr/bin/make... GNU
> >>> checking dependency style of cc... none
> >>> checking that generated files are newer than configure... done
> >>> configure: creating ./config.status
> >>> config.status: creating Makefile
> >>> config.status: creating subdir/Makefile
> >>> config.status: executing depfiles commands
> >>> + cat stderr
> >>> rm: conftest.dSYM: is a directory
> >>>
> >> Hmm, seems this is an old issue in Autoconf:
> >>
> >>  <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
> >>  <http://mail.python.org/pipermail/python-dev/2008-April/078807.html>
> >>
> >> I'll add a workaround to the automake testsuite to avoid the spurious
> >> failure (spurious since it's due to a buglet/limitation in autoconf,
> >> not in automake).  I'm about to log off now, so the patch proper should
> >> be poster tomorrow or the day after.
> >>
> > Here is the promised patch.  Can you confirm it works for you?
> > 
> > I'm adding bug-autoconf in CC because, from the first discussion linked
> > above, it appears the original issue had been fixed, but it must have
> > been unwittingly reintroduced in the meantime :-(  Maybe some autoconfer
> > wants to take a fresh look at the problem ...
> > 
> > Thanks,
> >   Stefano
> > 
> > ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ---- 8< ----
> > 
> > From 3759f24379c98b984a56b52c7d23a2dfbf36efcf Mon Sep 17 00:00:00 2001
> > Message-Id: <3759f24379c98b984a56b52c7d23a2dfbf36efcf.1372337066.git.stefano.lattarini <at> gmail.com>
> > From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
> > Date: Thu, 27 Jun 2013 14:43:12 +0200
> > Subject: [PATCH] tests: avoid a spurious failure on MacOS X 10.6.8
> > 
> > Fixes automake bug#14706.
> > 
> > * t/depcomp2.sh: Strip, from the redirected ./configure stderr, the
> > possible error message "rm: conftest.dSYM: is a directory", generated
> > by cleanup code that doesn't cater to the existence of *.dSYM
> > directories sometimes created by the compiler on MacOS X.  This
> > "massaging" of ./configure stderr is legitimate, since the spurious
> > error message is due not to automake-related code, but to a know
> > buglet/limitation of either Autoconf or Mac OS X bundles gcc:
> > <http://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html>
> > Actually, from that link it appears that the original Autoconf issue
> > had been fixed, but it must have been re-introduced in the meantime :-(
> > 
> > Signed-off-by: Stefano Lattarini <stefano.lattarini <at> gmail.com>
> > ---
> >  t/depcomp2.sh | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/t/depcomp2.sh b/t/depcomp2.sh
> > index 2182164..3eba12d 100644
> > --- a/t/depcomp2.sh
> > +++ b/t/depcomp2.sh
> > @@ -45,6 +45,9 @@ $AUTOMAKE --add-missing
> >  $AUTOCONF
> >  ./configure 2>stderr || { cat stderr >&2; exit 1; }
> >  cat stderr >&2
> > -test ! -s stderr
> > +# Ignore warning messages sometimes seen on Mac OS X; they are
> > +# not automake's fault anyway, but either autoconf's or Mac's.
> > +sed '/rm:.* conftest\.dSYM/d' stderr >stderr2
> > +test -s stderr2 && { cat stderr2; exit 1; }
> > 
> >  :
> > 
> Ping on this?  Can someone test this patch on Mac OS X and
> confirm it actually works?
> 
> Thanks,
>   Stefano

I've tried this on OSX 10.6.8 and 10.7 and t/depcomp2 now passes.

Diab

Message #29 received at 14706-done <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Diab Jerius <dj <at> head.cfa.harvard.edu>
Cc: 14706-done <at> debbugs.gnu.org,
 "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM
 directories
Date: Sun, 21 Jul 2013 13:18:53 +0100

Reference:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14706>

On 07/17/2013 05:02 PM, Diab Jerius wrote:
>
> [SNIP]
> 
> I've tried this on OSX 10.6.8 and 10.7 and t/depcomp2 now passes.
> 
> Diab
> 
> 
Thanks for letting me know; I will push the patch shortly then.
I'm also closing this bug report.

Thank you,
  Stefano

Message #32 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Hanspeter Niederstrasser <fink <at> snaggledworks.com>
To: 14706 <at> debbugs.gnu.org
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM,
 directories
Date: Wed, 24 Jul 2013 09:32:14 -0400

The patch mentioned above does fix the issue about the dSYM directory 
when using Apple's rm.  However, if a user has the GNU coreutils package 
installed, GNU rm generates a different error text and then the test fails.

With Apple's rm, this is the 'rm' feedback which is dealt with correctly:

rm: conftest.dSYM: is a directory

With GNU rm, this is the 'rm' feedback which causes depcomp2.sh to fail:

rm: cannot remove 'conftest.dSYM': Is a directory

Hanspeter

Message #39 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Hanspeter Niederstrasser <fink <at> snaggledworks.com>
Cc: 14706 <at> debbugs.gnu.org
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM,
 directories
Date: Thu, 26 Dec 2013 17:01:17 +0100

[Message part 1 (text/plain, inline)]

everity 14706 minor
tags 14706 + patch
close 14706

On 07/24/2013 03:32 PM, Hanspeter Niederstrasser wrote:
> The patch mentioned above does fix the issue about the dSYM directory when
> using Apple's rm.  However, if a user has the GNU coreutils package
> installed, GNU rm generates a different error text and then the test fails.
>
> With Apple's rm, this is the 'rm' feedback which is dealt with correctly:
>
> rm: conftest.dSYM: is a directory
>
> With GNU rm, this is the 'rm' feedback which causes depcomp2.sh to fail:
>
> rm: cannot remove 'conftest.dSYM': Is a directory
>
> Hanspeter
>
Thanks for the further report (and sorry for the shameful delay).  The
attached patch should finally take care of the issue.  If it doesn't work
for you, feel free to reopen this bug.

Best regards,
  Stefano

[0001-tests-fix-a-spurious-failure-on-Mac-OS-X.patch (text/x-patch, attachment)]

Message #42 received at 14706 <at> debbugs.gnu.org (full text, mbox):

From: Hanspeter Niederstrasser <fink <at> snaggledworks.com>
Cc: 14706 <at> debbugs.gnu.org
Subject: Re: bug#14706: Mac OS X gcc and bogus warnings about *.dSYM,
 directories
Date: Fri, 03 Jan 2014 10:06:40 -0500

Confirming that this final version of the patch applied to automake 
1.14.1 lets all tests pass on OS X with either GNU rm or BSD rm present. 
 Thanks.

Hanspeter

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.