mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Kevin Douglas <kevindouglas@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Compiler error for 2.6.0 in fs/proc/array.c
Date: Fri, 19 Dec 2003 06:26:54 -0800	[thread overview]
Message-ID: <20031219142654.GQ31393@holomorphy.com> (raw)
In-Reply-To: <20031219141531.13031.qmail@web40809.mail.yahoo.com>

On Fri, Dec 19, 2003 at 06:15:31AM -0800, Kevin Douglas wrote:
> Compiler error for 2.6.0 in fs/proc/array.c with gcc-2.95 and binutils
> 2.13.
> I received the following error while trying to compile the new 2.6.0
> (no -test anything) on my RH 7.3 box.  I have gcc version 2.95.3
> installed in addion to the yuckie 2.96 from RH.  While search the
> mailing list archives, I found some patches for the -test7 and/or
> -test8 series that claim they fix a gcc 2.96 bug.  I applied the patch
> on the original 2.6.0 source tree and the compile went through.  The
> patch I'm talking about involved making the tty_nr variable into a
> volatile int in the file fs/proc/array.c line number 298.  There are
> other patches that attempt to break up the huge sprintf() statement on
> line 347 into smaller chucks.  I'm not sure which would be preferable
> to the maintainer.
> The point of this email is to hopefully bring to your attention a
> compilation bug in the 2.6.0 source.  If I made a mistake and don't
> have my environment set up correctly, please accept my appologies.
> Hope this helps,
> -kevin

What you have found is actually a gcc bug. Upgrade gcc!

-- wli

      reply	other threads:[~2003-12-19 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 14:15 Kevin Douglas
2003-12-19 14:26 ` William Lee Irwin III [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031219142654.GQ31393@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=kevindouglas@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome