GNU bug report logs -
#24507
noinst_PYTHON breaks uninstall of Python files
Previous Next
Reported by: Akim Demaille <akim <at> lrde.epita.fr>
Date: Thu, 22 Sep 2016 09:49:01 UTC
Severity: normal
Tags: confirmed
Done: Karl Berry <karl <at> freefriends.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Hi, Automakers.
The attached patch fixes bug#24507.
I don't fully understand the cause, but I guess that the "if
%?INSTALL%" block gets ignored when "noinst" is present, including the
"?FIRST?" it contains, which defines the missing "am__pep3147_tweak".
Anyway, moving the "?FIRST?" block with the declaration of
"am__pep3147_tweak" outside the "if %?INSTALL%" block fixes the issue.
All tests with "py" in the name pass.
This isn't the first time either. The test I've updated was for a
similar case - bug#10995 ("am__py_compile doesn't get correctly
defined when there a 'noinst_PYTHON' declaration precedes a
'foo_PYTHON' declaration"), that's probably why "am__py_compile" is in
its own "?FIRST?" block at the top now.
No other language XX.am files seem to have "?FIRST?" inside an "if"
block.
--
Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
X86 assembly (DOS, GNU/Linux): http://bogdro.evai.pl/index-en.php
Soft(EN): http://bogdro.evai.pl/soft http://bogdro.evai.pl/soft4asm
www.Xiph.org www.TorProject.org www.LibreOffice.org www.GnuPG.org
[automake-fix-py-uninst-mail.diff (text/x-patch, attachment)]
This bug report was last modified 2 years and 13 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.