Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754455AbbFKOPK (ORCPT ); Thu, 11 Jun 2015 10:15:10 -0400 Received: from mail.kernel.org ([198.145.29.136]:36855 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751162AbbFKOPI (ORCPT ); Thu, 11 Jun 2015 10:15:08 -0400 Date: Thu, 11 Jun 2015 11:14:59 -0300 From: Arnaldo Carvalho de Melo To: He Kuang Cc: a.p.zijlstra@chello.nl, mingo@redhat.com, jolsa@kernel.org, kan.liang@intel.com, wangnan0@huawei.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] perf tools: Fix build failure on 32-bit arch Message-ID: <20150611141459.GD2696@kernel.org> References: <1434026664-71642-1-git-send-email-hekuang@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1434026664-71642-1-git-send-email-hekuang@huawei.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1084 Lines: 23 Em Thu, Jun 11, 2015 at 12:44:24PM +0000, He Kuang escreveu: > Failed in 32bit arch build like this: > > CC /opt/h00206996/output/perf/arm32/builtin-record.o > util/session.c: In function ‘perf_session__warn_about_errors’: > util/session.c:1304:9: error: format ‘%lu’ expects argument of type ‘long unsigned int’, > but argument 2 has type ‘long long unsigned int’ [-Werror=format=] > > builtin-report.c: In function ‘perf_evlist__tty_browse_hists’: > builtin-report.c:323:2: error: format ‘%lu’ expects argument of type ‘long unsigned int’, > but argument 3 has type ‘u64’ [-Werror=format=] > > Replace %lu format strings in warning message with PRIu64 for u64 > 'total_lost_samples' to fix this problem. Thanks, applied. - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/