[Numpy-discussion] profiling line by line

[Ondrej Certik]

On Fri, Sep 19, 2008 at 10:37 AM, Robert Cimrman <cimrman3 at ntc.zcu.cz> wrote:
> Ondrej Certik wrote:
>> On Thu, Sep 18, 2008 at 4:12 PM, Ryan May <rmay31 at gmail.com> wrote:
>>> Ondrej Certik wrote:
>>>> On Thu, Sep 18, 2008 at 1:01 PM, Robert Cimrman <cimrman3 at ntc.zcu.cz> wrote:
>>>>>> It requires Cython and a C compiler to build. I'm still debating
>>>>>> myself about the desired workflow for using it, but for now, it only
>>>>>> profiles functions which you have registered with it. I have made the
>>>>>> profiler work as a decorator to make this easy. E.g.,
>>>>> many thanks for this! I have wanted to try out the profiler but failed
>>>>> to build it (changeset 6 0de294aa75bf):
>>>>>
>>>>> $ python setup.py install --root=/home/share/software/
>>>>> running install
>>>>> running build
>>>>> running build_py
>>>>> creating build
>>>>> creating build/lib.linux-i686-2.4
>>>>> copying line_profiler.py -> build/lib.linux-i686-2.4
>>>>> running build_ext
>>>>> cythoning _line_profiler.pyx to _line_profiler.c
>>>>> building '_line_profiler' extension
>>>>> creating build/temp.linux-i686-2.4
>>>>> i486-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -fPIC
>>>>> -I/usr/include/python2.4 -c -I/usr/include/python2.4 -c _line_profiler.c
>>>>> -o build/temp.linux-i686-2.4/_line_profiler.o
>>>>> _line_profiler.c:1614: error: 'T_LONGLONG' undeclared here (not in a
>>>>> function)
>>>>> error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1
>>>>>
>>>>> I have cython-0.9.8.1 and GCC 4.1.2, 32-bit machine.
>>>> I am telling you all the time Robert to use Debian that it just works
>>>> and you say, no no, gentoo is the best. :)
>>> And what's wrong with that? :)  Once you get over the learning curve,
>>> Gentoo works just fine.  Must be Robert K.'s fault. :)
>>
>> Well, I think if Robert C. hasn't yet get over the learning curve
>> after so many years of hard work, maybe the learning curve is too
>> steep. :)
>
> This is most probably not related to Gentoo at all and certainly not
> related to me knowing Gentoo or not :) (and no, learning Gentoo is not
> that hard.)

Let us know where the problem was. :) I am just using common sense, if
something works on Debian and macosx and doesn't work on gentoo, I
thought it was safe to say it was gentoo related, but I may well be
wrong. :))

Ondrej