Bug#835647: python-brainstorm: build path is captured
Great! Thx for the pointer. DS On 28.08.2016 00:48, Chris Lamb wrote: > Hi, > >> python-brainstorm: build path is captured > > Following this through for a few stages, I first see this generated > C code: > > --- ./a/python-brainstorm-0.5/brainstorm/handlers/_cpuop.c2016-08-27 > 23:32:02.362189730 +0100 > +++ ./b/python-brainstorm-0.5/brainstorm/handlers/_cpuop.c2016-08-27 > 23:32:57.834818195 +0100 > @@ -2029,7 +2029,7 @@ > static const char __pyx_k_Expected_at_least_d_arguments[] = "Expected at > least %d arguments"; > static const char __pyx_k_unable_to_allocate_array_data[] = "unable to > allocate array data."; > static const char __pyx_k_strided_and_direct_or_indirect[] = " direct or indirect>"; > -static const char __pyx_k_home_lamby_temp_cdt_20160827233[] = > "/home/lamby/temp/cdt.20160827233114.crIlYLxW7D.repro.python-brainstorm/build-a/python-brainstorm-0.5/brainstorm/handlers/_cpuop.pyx"; > +static const char __pyx_k_home_lamby_temp_cdt_20160827233[] = > "/home/lamby/temp/cdt.20160827233114.crIlYLxW7D.repro.python-brainstorm/build-b/python-brainstorm-0.5/brainstorm/handlers/_cpuop.pyx"; > static const char __pyx_k_unknown_dtype_code_in_numpy_pxd[] = "unknown dtype > code in numpy.pxd (%d)"; > static const char __pyx_k_Buffer_view_does_not_expose_stri[] = "Buffer view > does not expose strides"; > static const char __pyx_k_Can_only_create_a_buffer_that_is[] = "Can only > create a buffer that is contiguous in memory."; > > (NB. the variable *name*, not only its value) > > .. which is generated from the corresponding .pyc. I believe it > is caused by cython pulling in memoryview via: > >from cython.view cimport array as cvarray > > Hope that helps jumpstart you... > > > Regards, -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Bug#835647: python-brainstorm: build path is captured
Hi, > python-brainstorm: build path is captured Following this through for a few stages, I first see this generated C code: --- ./a/python-brainstorm-0.5/brainstorm/handlers/_cpuop.c 2016-08-27 23:32:02.362189730 +0100 +++ ./b/python-brainstorm-0.5/brainstorm/handlers/_cpuop.c 2016-08-27 23:32:57.834818195 +0100 @@ -2029,7 +2029,7 @@ static const char __pyx_k_Expected_at_least_d_arguments[] = "Expected at least %d arguments"; static const char __pyx_k_unable_to_allocate_array_data[] = "unable to allocate array data."; static const char __pyx_k_strided_and_direct_or_indirect[] = ""; -static const char __pyx_k_home_lamby_temp_cdt_20160827233[] = "/home/lamby/temp/cdt.20160827233114.crIlYLxW7D.repro.python-brainstorm/build-a/python-brainstorm-0.5/brainstorm/handlers/_cpuop.pyx"; +static const char __pyx_k_home_lamby_temp_cdt_20160827233[] = "/home/lamby/temp/cdt.20160827233114.crIlYLxW7D.repro.python-brainstorm/build-b/python-brainstorm-0.5/brainstorm/handlers/_cpuop.pyx"; static const char __pyx_k_unknown_dtype_code_in_numpy_pxd[] = "unknown dtype code in numpy.pxd (%d)"; static const char __pyx_k_Buffer_view_does_not_expose_stri[] = "Buffer view does not expose strides"; static const char __pyx_k_Can_only_create_a_buffer_that_is[] = "Can only create a buffer that is contiguous in memory."; (NB. the variable *name*, not only its value) .. which is generated from the corresponding .pyc. I believe it is caused by cython pulling in memoryview via: from cython.view cimport array as cvarray Hope that helps jumpstart you... Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#835647: python-brainstorm: build path is captured
Source: python-brainstorm Version: 0.5-2 Severity: normal User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath brainstorm doesn't build reproducibly on i386, the build path is captured in the dbgsym package. I'll get into this, soon. DS -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
