From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757204AbcIGOGW (ORCPT ); Wed, 7 Sep 2016 10:06:22 -0400 Received: from mga04.intel.com ([192.55.52.120]:28175 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753833AbcIGOGT (ORCPT ); Wed, 7 Sep 2016 10:06:19 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,296,1470726000"; d="scan'208";a="1052597110" From: Jani Nikula To: Geert Uytterhoeven Cc: Jonathan Corbet , Markus Heiser , "linux-doc\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" Subject: Re: pyc files in source dir with O= In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <87oa3zx2jg.fsf@intel.com> User-Agent: Notmuch/0.22.1+63~g648dcc7 (https://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Wed, 07 Sep 2016 17:05:55 +0300 Message-ID: <87lgz3x0sc.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 07 Sep 2016, Geert Uytterhoeven wrote: > Hi Jani, > > On Wed, Sep 7, 2016 at 3:28 PM, Jani Nikula wrote: >> On Wed, 07 Sep 2016, Geert Uytterhoeven wrote: >>> When running "make htmldocs O=/path/to/somewhere", *.pyc files end up >>> in the source tree instead of in the build tree: >>> >>> $ git ls-files -o >>> Documentation/sphinx/kernel-doc.pyc >>> Documentation/sphinx/kernel_include.pyc >>> Documentation/sphinx/rstFlatTable.pyc >>> $ >>> >>> This is with v4.8-rc5. >>> >>> With next-20160907, two more files appear: >>> >>> Documentation/sphinx/cdomain.pyc >>> Documentation/sphinx/load_config.pyc >> >> This should help >> >> diff --git a/Documentation/Makefile.sphinx b/Documentation/Makefile.sphinx >> index 92deea30b183..a4cba2d1aaf1 100644 >> --- a/Documentation/Makefile.sphinx >> +++ b/Documentation/Makefile.sphinx >> @@ -53,6 +53,7 @@ loop_cmd = $(echo-cmd) $(cmd_$(1)) >> >> quiet_cmd_sphinx = SPHINX $@ --> file://$(abspath $(BUILDDIR)/$3/$4); >> cmd_sphinx = $(MAKE) BUILDDIR=$(abspath $(BUILDDIR)) $(build)=Documentation/media all;\ >> + PYTHONDONTWRITEBYTECODE=1 \ >> BUILDDIR=$(abspath $(BUILDDIR)) SPHINX_CONF=$(abspath $(srctree)/$(src)/$5/$(SPHINX_CONF)) \ >> $(SPHINXBUILD) \ >> -b $2 \ > > Thanks, that works (on next-20160907, doesn't apply to v4.8-rc5). > But IMHO it's a bit drastic. There's no way to let python create them in the > build directory instead? I'm no expert, but the short answer appears to be no [1]. You'd have to copy the .py files over to the build directory, which is a bit meh. BR, Jani. [1] http://stackoverflow.com/questions/3522079/changing-the-directory-where-pyc-files-are-created > > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds -- Jani Nikula, Intel Open Source Technology Center