GNU bug report logs - #10995
am__py_compile dose not get added to Makefile.in's

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 10995 in the body.
You can then email your comments to 10995 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: Steven Drake <sbd <at> NetBSD.org>
To: bug-automake <at> gnu.org
Subject: am__py_compile dose not get added to Makefile.in's
Date: Sun, 11 Mar 2012 20:32:35 +1300 (NZDT)

The variable gets used by install-%DIR%PYTHON: (from lib/am/python.am) but
it definition is not include in the output Makefile.in.

-- 
Steven

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

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Steven Drake <sbd <at> NetBSD.org>
Cc: 10995 <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#10995: am__py_compile dose not get added to Makefile.in's
Date: Mon, 12 Mar 2012 12:22:39 +0100

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

tags 10995 moreinfo
thanks

Hi Steven, thanks for the report.

On 03/11/2012 08:32 AM, Steven Drake wrote:
> The variable gets used by install-%DIR%PYTHON: (from lib/am/python.am) but
> it definition is not include in the output Makefile.in.
> 
I cannot reproduce this bug, sorry.  In fact, I've enhanced the 'python.test'
test case to ensure the bug you're describing is actually not present in the
'maint' branch (see attached patch).  Maybe there is something unusual in your
setup that is causing the problem?  Could send us more information, so that we
can try to reproduce the issue?

Regards,
  Stefano

[0001-coverage-make-sure-am__py_compile-is-defined-when-ne.patch (text/x-diff, attachment)]

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

From: Steven Drake <sbd <at> NetBSD.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 10995 <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#10995: am__py_compile dose not get added to Makefile.in's
Date: Thu, 15 Mar 2012 20:20:56 +1300 (NZDT)

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

On Mon, 12 Mar 2012, Stefano Lattarini wrote:

> Hi Steven, thanks for the report.
> 
> On 03/11/2012 08:32 AM, Steven Drake wrote:
> > The variable gets used by install-%DIR%PYTHON: (from lib/am/python.am) but
> > it definition is not include in the output Makefile.in.
> > 
> I cannot reproduce this bug, sorry.  In fact, I've enhanced the 'python.test'
> test case to ensure the bug you're describing is actually not present in the
> 'maint' branch (see attached patch).  Maybe there is something unusual in your
> setup that is causing the problem?  Could send us more information, so that we
> can try to reproduce the issue?

Running the 'python.test' with the attached patch passes! but I had a look
at the package that had the original problem and the line just isn't there.

For reference the package build log are available at:
http://ftp.netbsd.org/pub/pkgsrc/misc/sbd/reports/Linux-x86_64/20120304.1324/usrp-3.3.0nb4/

The build process rebuilds the autoconf and automake files before running
the configure script.

Its possible to tell that it doesn't get defined by the line in 'install.log':
"/bin/sh: line 15: --destdir: command not found"

The problem goes away if the attached patch is applied.

-- 
Steven

[patch-lib_am_python.am (text/plain, attachment)]

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

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Steven Drake <sbd <at> NetBSD.org>
Cc: 10995 <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#10995: am__py_compile dose not get added to Makefile.in's
Date: Thu, 15 Mar 2012 09:23:20 +0100

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

tags 10995 patch
close 10995
thanks

On 03/15/2012 08:20 AM, Steven Drake wrote:
>
> Its possible to tell that it doesn't get defined by the line in 'install.log':
> "/bin/sh: line 15: --destdir: command not found"
> 
> The problem goes away if the attached patch is applied.
> 
Thanks, I can now reproduce the issue, and I agree yours is the right fix.

I've thus applied (to maint) a patch in my name exposing the bug in the automake
testsuite, and a patch in your name fixing it (see attachements).  I've then
merged maint into branch-1.11 and master.

Best regards, and thanks,
  Stefano

[0001-python-expose-automake-bug-10995.patch (text/x-diff, attachment)]

[0002-python-avoid-failures-due-to-am__py_compile-being-un.patch (text/x-diff, attachment)]

Previous Next

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