[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Kernel build fails with GCC 4.3



On 02/01/2008 11:32 AM, Chuck Ebbert wrote:
> On 02/01/2008 03:46 AM, Jakub Jelinek wrote:
>> On Thu, Jan 31, 2008 at 07:50:42PM -0500, Kyle McMartin wrote:
>>> On Thu, Jan 31, 2008 at 04:47:55PM -0800, Roland McGrath wrote:
>>>>> Why are we building kernels with this broken compiler?
>>>>>
>>>>> http://bugzilla.kernel.org/show_bug.cgi?id=8501
>>>>>
>>>>> http://koji.fedoraproject.org/koji/getfile?taskID=388196&name=build.log
>>>> Why are we building these broken kernels with our shiny new compiler?
>>>>
>>> Does using -ffreestanding fix these references to libgcc? I notice
>>> we're not using it when we build x86 or powerpc kernels, where we see
>>> this...
>> No, even -ffreestanding assumes libgcc is used.  libgcc.a is mostly[1]
>> self-contained and assumed to be present in both -fhosted and -ffreestanding
>> linking.  This is nothing new, has been like that for many years.
>> AFAIK kernel on several architectures uses libgcc.a, on those where it
>> intentionally decides not to do that, it either needs to supply its own
>> implementation of the needed entrypoints, or make sure they are not needed.
>> In this case you should put in an asm optimization barrier into the loop
>> to avoid optimizing the loop into modulo.  See the gcc PR opened for it.
>>
> 
> 
> drivers/input/mouse/psmouse-base.c:45: error: __param_proto causes a section type conflict
> 

And, after fixing that one we get (on ppc):

*** ERROR: same build ID in nonidentical files!
        /usr/lib/debug/lib/modules/2.6.24-14.fc9/vmlinux
   and  /boot/vmlinuz-2.6.24-14.fc9


Where before it just said:

*** WARNING: identical binaries are copied, not linked:
        /usr/lib/debug/lib/modules/2.6.24-9.fc9/vmlinux
   and  /boot/vmlinuz-2.6.24-9.fc9


I don't think I can fix that one...


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]