From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264588AbTL0UzG (ORCPT ); Sat, 27 Dec 2003 15:55:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264591AbTL0UzG (ORCPT ); Sat, 27 Dec 2003 15:55:06 -0500 Received: from fiberbit.xs4all.nl ([213.84.224.214]:53391 "EHLO fiberbit.xs4all.nl") by vger.kernel.org with ESMTP id S264588AbTL0Uy6 (ORCPT ); Sat, 27 Dec 2003 15:54:58 -0500 Date: Sat, 27 Dec 2003 21:54:41 +0100 From: Marco Roeland To: Stefano Rosellini Cc: linux-kernel@vger.kernel.org Subject: Re: PROBLEM: Kernel 2.6.0 has a compilation error on "fs/proc/array.c" Message-ID: <20031227205441.GA27994@localhost> References: <20031227184639.84BD652B35@athlon.casamia> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20031227184639.84BD652B35@athlon.casamia> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Saturday December 27th 2003 Stefano Rosellini wrote: > [1.] Kernel 2.6.0 has a compilation error on "fs/proc/array.c" > [7.1.] ver_linux output: > Gnu C 2.96 This is due to a known compiler bug in RedHat's gcc 2.96! It is recommended that you upgrade gcc. However if you insist on trying with that particular compiler you can use the following workaround: --- linux-2.6.0-test8/fs/proc/array.c.orig 2003-10-21 16:18:40.000000000 +0200 +++ linux-2.6.0-test8/fs/proc/array.c 2003-10-23 09:30:27.000000000 +0200 @@ -302,6 +302,7 @@ pid_t ppid; int num_threads = 0; struct mm_struct *mm; + unsigned long long starttime; state = *get_task_state(task); vsize = eip = esp = 0; @@ -343,9 +344,7 @@ read_lock(&tasklist_lock); ppid = task->pid ? task->real_parent->pid : 0; read_unlock(&tasklist_lock); - res = sprintf(buffer,"%d (%s) %c %d %d %d %d %d %lu %lu \ -%lu %lu %lu %lu %lu %ld %ld %ld %ld %d %ld %llu %lu %ld %lu %lu %lu %lu %lu \ -%lu %lu %lu %lu %lu %lu %lu %lu %d %d %lu %lu\n", + res = sprintf(buffer,"%d (%s) %c %d %d %d %d %d %lu %lu ", task->pid, task->comm, state, @@ -355,7 +354,9 @@ tty_nr, tty_pgrp, task->flags, - task->min_flt, + task->min_flt); + starttime = jiffies_64_to_clock_t(task->start_time - INITIAL_JIFFIES); + res += sprintf(buffer + res,"%lu %lu %lu %lu %lu %ld %ld %ld %ld %d %ld %llu %lu %ld %lu %lu %lu %lu %lu ", task->cmin_flt, task->maj_flt, task->cmaj_flt, @@ -367,15 +368,15 @@ nice, num_threads, jiffies_to_clock_t(task->it_real_value), - (unsigned long long) - jiffies_64_to_clock_t(task->start_time - INITIAL_JIFFIES), + starttime, vsize, mm ? mm->rss : 0, /* you might want to shift this left 3 */ task->rlim[RLIMIT_RSS].rlim_cur, mm ? mm->start_code : 0, mm ? mm->end_code : 0, mm ? mm->start_stack : 0, - esp, + esp); + res += sprintf(buffer + res,"%lu %lu %lu %lu %lu %lu %lu %lu %d %d %lu %lu\n", eip, /* The signal information here is obsolete. * It must be decimal for Linux 2.0 compatibility.