From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KwwZq-0002ye-Hm for garchives@archives.gentoo.org; Mon, 03 Nov 2008 10:22:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4130EE03FD; Mon, 3 Nov 2008 10:22:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 1637BE03FD for ; Mon, 3 Nov 2008 10:22:29 +0000 (UTC) Received: from [192.168.1.33] (unknown [77.246.104.171]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 32B6F647E2 for ; Mon, 3 Nov 2008 10:22:23 +0000 (UTC) Subject: Re: [gentoo-dev] [PMS] Add RESTRICT="distcc" capability From: Peter Volkov To: gentoo-dev@lists.gentoo.org In-Reply-To: <200811021111.10124.gengor@gentoo.org> References: <200811011357.17258.gengor@gentoo.org> <200811011829.03758.gengor@gentoo.org> <20081102112614.00851d36@snowmobile> <200811021111.10124.gengor@gentoo.org> Content-Type: text/plain; charset=utf-8 Date: Mon, 03 Nov 2008 13:22:12 +0300 Message-Id: <1225707732.1775.46.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b907e37c-bfa5-448d-af87-2c5d345d5ef3 X-Archives-Hash: 85de2fe6c2254ab0689539a57225cfde =D0=92 =D0=92=D1=81=D0=BA, 02/11/2008 =D0=B2 12:11 -0700, Gordon Malm =D0= =BF=D0=B8=D1=88=D0=B5=D1=82: > You can cry "abuse" all you want. You FAIL to offer any alternatives o= r=20 > solutions. I'll ask again, how do you detect that you are compiling co= de=20 > destined to be run in-kernel from within gcc without checking for the=20 > __KERNEL__ macro? I think we both know the answer. Gordon, as far as I see our linux-mod.eclass builds each kernel module separately and it is possible to modify it to pass CFLAGS you wish for kernel modules only and as such avoid using __KERNEL__ macro for this... --=20 Peter.