On Tue, 16 Apr 2013 13:32:08 -0700, David Ahern wrote:
> On 4/16/13 10:08 AM, Michael Witten wrote:
>> You should probably disable python support more directly:
>>
>>make NO_LIBPYTHON=1
>
> sure, but I should not have to do anything. The intent of the existing
> auto-probing code is to figur
On 4/16/13 10:08 AM, Michael Witten wrote:
You should probably disable python support more directly:
make NO_LIBPYTHON=1
sure, but I should not have to do anything. The intent of the existing
auto-probing code is to figure out what is installed and build a binary
with those capabilities.
Hello,
On Tue, Apr 16, 2013 at 5:14 AM, Namhyung Kim wrote:
>> The problem is that I didn't have python-devel package installed and
>> get-executable-or-default decides to error out instead of letting the
>> Makefile disable Python support.
>
> Right. I think the get-executable-or-default should
On Mon, 15 Apr 2013 21:26:40 -0700, David Ahern wrote:
> On 4/15/13 7:14 PM, Namhyung Kim wrote:
>>> Makefile:755: The path '/usr/bin/python-config' is not executable.
>>> Makefile:755: *** Please set 'PYTHON_CONFIG' appropriately. Stop.
>>>
>>> The problem is that I didn't have python-devel pack
On 4/15/13 7:14 PM, Namhyung Kim wrote:
Makefile:755: The path '/usr/bin/python-config' is not executable.
Makefile:755: *** Please set 'PYTHON_CONFIG' appropriately. Stop.
The problem is that I didn't have python-devel package installed and
get-executable-or-default decides to error out instea
Hi Pekka,
On Mon, 15 Apr 2013 13:58:50 +0300, Pekka Enberg wrote:
> Hello,
>
> I'm seeing this when I try to build perf in v3.9-rc7:
>
> [penberg@golgotha perf]$ make
> CHK -fstack-protector-all
> CHK -Wstack-protector
> CHK -Wvolatile-register-var
> CHK -D_FORTIFY_SOURCE=2
> C
Hello,
I'm seeing this when I try to build perf in v3.9-rc7:
[penberg@golgotha perf]$ make
CHK -fstack-protector-all
CHK -Wstack-protector
CHK -Wvolatile-register-var
CHK -D_FORTIFY_SOURCE=2
CHK bionic
CHK libelf
CHK libdw
Makefile:584: No libdw.h found or old libdw.h
7 matches
Mail list logo