From owner-freebsd-current@FreeBSD.ORG Wed Dec 21 06:06:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5DE6106566B for ; Wed, 21 Dec 2011 06:06:13 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by mx1.freebsd.org (Postfix) with ESMTP id 857F18FC15 for ; Wed, 21 Dec 2011 06:06:13 +0000 (UTC) X-AuditID: 1209190e-b7f8f6d0000008fc-1d-4ef17754c818 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id E9.0A.02300.45771FE4; Wed, 21 Dec 2011 01:06:12 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id pBL66CsC010657; Wed, 21 Dec 2011 01:06:12 -0500 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id pBL669gg024767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Dec 2011 01:06:11 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id pBL669hY023718; Wed, 21 Dec 2011 01:06:09 -0500 (EST) Date: Wed, 21 Dec 2011 01:06:08 -0500 (EST) From: Benjamin Kaduk To: Larry Rosenman In-Reply-To: <4EF0CCC6.6060606@lerctr.org> Message-ID: References: <4EF0CCC6.6060606@lerctr.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGIsWRmVeSWpSXmKPExsUixG6nohtS/tHPoHePhsWcNx+YLJY/mMXq wOQx49N8Fo/9e7eyBDBFcdmkpOZklqUW6dslcGXcm6ZRMJW7YuvUD2wNjFc4uhg5OSQETCQe Lelgh7DFJC7cW88GYgsJ7GOUWNqq0sXIBWRvYJQ4/fMtO0TiAJPExisZEIkGRonVjQdYQBIs AtoSU2ZNZgWx2QRUJGa+2Qg2SURAWWLN1D/MIDazgLzE/yuXmUBsYQFrifbzk4CGcnBwCmhJ nOmpBAnzCthLTHyynRVil6bEvQWzwfaKCuhIrN4/hQWiRlDi5MwnLBAjLSXO/bnONoFRcBaS 1CwkqQWMTKsYZVNyq3RzEzNzilOTdYuTE/PyUot0jfVyM0v0UlNKNzGCgpRTkm8H49eDSocY BTgYlXh4hfd/8BNiTSwrrsw9xCjJwaQkyltU9tFPiC8pP6UyI7E4I76oNCe1+BCjBAezkggv Sx5QjjclsbIqtSgfJiXNwaIkzqum9c5PSCA9sSQ1OzW1ILUIJivDwaEkwbsbZKhgUWp6akVa Zk4JQpqJgxNkOA/Q8HUgNbzFBYm5xZnpEPlTjLocez9/P8MoxJKXn5cqJc67A6RIAKQoozQP bg4subxiFAd6S5j3MkgVDzAxwU16BbSECWjJNucPIEtKEhFSUg2MZcfXy2fPOx0ac5clStnw kP+DL69XWi/a6X/g6NzgOXV1mqlrdf+/zdAqv9O4e/5lgzr+v1Pi7bLEUg1bViX+PM1y/PEb G84nRau0nLlu1Ne847/7w4T9MteezVc7FYVddy/sePJz8u6iT680dyyNWL3l7V4DB8Yd5lU5 6upfJorVbNi6bMuuHiWW4oxEQy3mouJEANzxEt0JAwAA Cc: freebsd-current@freebsd.org Subject: Re: clang (__builtin_ffs) vs /usr/include/string.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 06:06:14 -0000 Hi Larry, On Tue, 20 Dec 2011, Larry Rosenman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Is anyone going to fix the following in the clang or FreeBSD system? I haven't seen any mention of __builtin_ffs on any freebsd lists since your thread in october, "system headers with clang?". That rather makes me suspect that no one else is seeing this "problem". It's hard to fix something you don't know about. > > In file included from /usr/include/string.h:45: > /usr/include/strings.h:47:6: error: conflicting types for '__builtin_ffs' > int ffs(int) __pure2; > ^ > /usr/include/machine/cpufunc.h:140:24: note: expanded from: > #define ffs(x) __builtin_ffs(x) > ^ > /usr/include/strings.h:47:6: note: '__builtin_ffs' is a builtin with > type 'int (unsigned int)' > 7 warnings and 1 error generated. > *** Error code 1 > As such, since we don't know what the "problem" is, some context for what is going on here would be useful -- what are you trying to compile? Still lsof? > > This looks like something that needs to change in clang/FreeBSD headers. Not necessarily -- things from the machine/ hierarchy are pretty uncommon, and I wouldn't be surprised if they had dependencies and ordering requirements involved. It could well be an application error, but we can't tell, since there is no context. -Ben Kaduk