From: Marco Roeland <marco.roeland@xs4all.nl>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Cc: Norman Diamond <ndiamond@wta.att.ne.jp>
Subject: Re: RH7.3 can't compile 2.6.0-test8
Date: Tue, 21 Oct 2003 15:52:21 +0200 [thread overview]
Message-ID: <20031021135221.GA22633@localhost> (raw)
In-Reply-To: <20031021131915.GA4436@rushmore>
Op dinsdag 21 oktober 2003 om 09:19 uur schreef rwhron@earthlink.net het volgende:
> > The Readme for 2.6.0-test6 still said that gcc 2.95 is required
>
> test8 Changes still says gcc-2.95.3. I saw the same compile error
> on RedHat 7.2. I ended up using gcc-3.3.1. Later I saw this patch:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106651554401143&w=2
>
> It's supposed to fix test8 compile with gcc-2.96 for RedHat 7.x.
It seems an odd fix though, the variable tty_nr is at most set once
inside the function, and is inaccessible to other functions so why it
should be volatile seems unclear to me. It might solve the compilation
(now that I look again the original error messages mention gcc internal
representation, so the suggestion of binutils at fault seems unwarranted)
but that seems by accident, not by design?
Perhaps if the huge sprintf with 40+ arguments (fs/proc/array.c, line 346)
amongst which several trinary operators, were to be split up into several
parts, might that not solve the problem more elegantly?
--
Marco Roeland
next prev parent reply other threads:[~2003-10-21 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 13:19 RH7.3 can't compile 2.6.0-test8 rwhron
2003-10-21 13:52 ` Marco Roeland [this message]
2003-10-21 14:37 ` [PATCH] RH7.3 can't compile 2.6.0-test8 (fs/proc/array.c) Marco Roeland
2003-10-21 20:12 ` Paul Larson
2003-10-21 20:46 ` bill davidsen
2003-10-22 10:36 ` Norman Diamond
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 12:14 RH7.3 can't compile 2.6.0-test8 Norman Diamond
2003-10-20 10:21 Norman Diamond
2003-10-20 14:01 ` Christian Kujau
2003-10-20 16:43 ` Marco Roeland
2003-10-20 20:58 ` Paul Larson
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=20031021135221.GA22633@localhost \
--to=marco.roeland@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/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