Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp7143792ybi; Thu, 13 Jun 2019 10:17:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqyX0EcMI7ufjMD+6RPJ8xFzEZN8O8XrmNvlAE+ODzNmn82cvBmyZwXSTXqt/5zNAse+wHsE X-Received: by 2002:a17:902:e211:: with SMTP id ce17mr7521480plb.193.1560446235704; Thu, 13 Jun 2019 10:17:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560446235; cv=none; d=google.com; s=arc-20160816; b=ZgEtUCp4YKPgKIjxbDMJwZHFufAHNFManDPF0/WjLl0BKa+08Pc0HMAJTVIPeJMkp5 8QVd8F1+tYCQqpOcUc1a8ZJZv1uMLitCbKMOou2qoLgptVikKiI+p+yd6EAzTq4ekuMm ZOMN2STq0Ntv6izxFm8Vx6NrjsxHz3NhxuofUqKKNxibHIwZCq4yy1Sloq/owDcOT7kj Nic32sqEMdMxG6WOYFD8wo8kdP0opa//rnZ6SquhFJUQf8YToTBP92+eo/xHgBCuPyY9 seFOxQMKad5qLpvUt5bqYBuYaukCDtw10A3YjiGPv3L8l5JCWa1fih6j1G2F621Eg5Af ZFww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=xhV5IK6SRvgTkUcOw3h17mhwvaMmDLGvhkYdlYX39Zk=; b=xEDkvZNX5bNU1czHK1zNbOnH8f09YOLl2QCWCezPob1+ce/NX59AjvLADnXLmoVBu8 CzF35P688M3wXPVvVZnjj8OxsQBEVLZrwkLNRbmvbTSAENjzWlbIKBmLUeNCRmfH0aqd 1HcOnjSse2Oj98m+yVvkAOybjUH8BC3DC0AU5HH80aRNDZsLwmyhdwmez5SVsn1TEQ9W ck2rOXWhkTYjIHTum8YkKhcVMT6AEAyUGwXEavisY/VZeCgv5ASBHEkR8MT4D4zHvCla VgCrVOuKxQcYEjwq8HuJHM40v92u6VD6W0nsSL9+XZfNfO5ZD+B0jvD9ljtSaXLS708q ug0Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f6si266904pgk.120.2019.06.13.10.16.59; Thu, 13 Jun 2019 10:17:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729061AbfFMRQz (ORCPT + 99 others); Thu, 13 Jun 2019 13:16:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57880 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725819AbfFLV1f (ORCPT ); Wed, 12 Jun 2019 17:27:35 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F2171C18B2E4; Wed, 12 Jun 2019 21:27:34 +0000 (UTC) Received: from krava (ovpn-204-42.brq.redhat.com [10.40.204.42]) by smtp.corp.redhat.com (Postfix) with SMTP id 4F68F5D9D5; Wed, 12 Jun 2019 21:27:33 +0000 (UTC) Date: Wed, 12 Jun 2019 23:27:32 +0200 From: Jiri Olsa To: Laura Abbott Cc: Jiri Olsa , Arnaldo Carvalho de Melo , Stephane Eranian , Florian Weimer , Linux Kernel Mailing List Subject: Re: perf build failure with newer glibc headers Message-ID: <20190612212732.GA14171@krava> References: <4c0a4264-7142-2e6d-540d-aa354700e0bb@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4c0a4264-7142-2e6d-540d-aa354700e0bb@redhat.com> User-Agent: Mutt/1.11.4 (2019-03-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 12 Jun 2019 21:27:35 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 12, 2019 at 03:23:12PM -0400, Laura Abbott wrote: > Hi, > > While doing some build experiments, I found a compile failure with perf and jvmti: > > BUILDSTDERR: gcc -Wp,-MD,./.xsk.o.d -Wp,-MT,xsk.o -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-jvmti/jvmti_agent.c:48:21: error: static declaration of 'gettid' follows non-static declaration > BUILDSTDERR: 48 | static inline pid_t gettid(void) > BUILDSTDERR: | ^~~~~~ > BUILDSTDERR: In file included from /usr/include/unistd.h:1170, > BUILDSTDERR: from jvmti/jvmti_agent.c:33: > BUILDSTDERR: /usr/include/bits/unistd_ext.h:40:16: note: previous declaration of 'gettid' was here > BUILDSTDERR: 40 | extern __pid_t gettid (void) __THROW; > BUILDSTDERR: | ^~~~~~ > > > This is with the newer glibc headers that came into Fedora earlier this week > (glibc-2.29.9000-27.fc31) It looks like the newer headers now define gettid > so the in file gettid no longer works. Note this was a custom build with > jvmti enabled as regular Fedora doesn't have it enabled which is why this > wasn't reported elsewhere. hum, I guess we need some version macro conditions if that's the case so this glibc version is available on rawhide now? I'll try to get some server with it thanks, jirka > > I don't know enough about either the glibc headers or perf to make a suggestion > on how to fix this but I'm happy to test. > > Thanks, > Laura