Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030243AbVKVXUh (ORCPT ); Tue, 22 Nov 2005 18:20:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030244AbVKVXUh (ORCPT ); Tue, 22 Nov 2005 18:20:37 -0500 Received: from e6.ny.us.ibm.com ([32.97.182.146]:4835 "EHLO e6.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1030243AbVKVXUg (ORCPT ); Tue, 22 Nov 2005 18:20:36 -0500 Message-ID: <4383A790.1090208@us.ibm.com> Date: Tue, 22 Nov 2005 15:19:44 -0800 From: Darren Hart User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "lkml, " CC: Ingo Molnar Subject: 2.6.14-rt13 / minimum gcc version Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 907 Lines: 25 rt13 makes use of the gcc extension: int __builtin_types_compatible_p (type1, type2) which from what I can tell was first introduced to gcc in version 3.1.1 http://gcc.gnu.org/onlinedocs/gcc-3.1.1/gcc/Other-Builtins.html In any case, I am unable to compile rt13 with gcc-2.95. I have tried various -std args as well, but the compiler dies on __builtin_types_compatible_p. 1) Is it acceptable to require >= gcc-3.1.1 to compile a Linux kernel? 2) Would a patch/work-around for gcc-2.95 compatibility be accepted if I provide one? (assuming it is a sane implementation of course :-) Thanks, -- Darren Hart IBM Linux Technology Center Linux Kernel Team - 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/