From: Russell King <rmk@arm.linux.org.uk>
To: John Levon <levon@movementarian.org>
Cc: Rahul Vaidya <rahulv@csa.iisc.ernet.in>,
Zwane Mwaikambo <zwane@holomorphy.com>,
linux-kernel@vger.kernel.org
Subject: Re: linux 2.5.53 not compiling
Date: Sun, 16 Feb 2003 17:46:37 +0000 [thread overview]
Message-ID: <20030216174637.C12489@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030216174118.GA63890@compsoc.man.ac.uk>; from levon@movementarian.org on Sun, Feb 16, 2003 at 05:41:18PM +0000
On Sun, Feb 16, 2003 at 05:41:18PM +0000, John Levon wrote:
> On Sun, Feb 16, 2003 at 10:57:50PM +0530, Rahul Vaidya wrote:
>
> > I am getting the same error even for 2.5.61
> >
> > Please cc any replies to rahulv@csa.iisc.ernet.in
>
> Have you made a softlink for gcc ? Apparently that doesn't work well
> with recent gcc versions finding the headers...
It looks like buggy gcc configuration scripts - some parts of the compiler
seems to believe its internal headers are one place, whereas other parts
believe they're elsewhere.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-02-16 17:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 17:02 linux 2.5.53 not compiling Rahul Vaidya
2003-02-16 17:06 ` Zwane Mwaikambo
2003-02-16 17:27 ` Rahul Vaidya
2003-02-16 17:41 ` John Levon
2003-02-16 17:46 ` Russell King [this message]
2003-02-16 18:11 ` Rahul Vaidya
2003-02-16 18:10 ` Rahul Vaidya
2003-02-16 18:21 ` Daniel Jacobowitz
2003-02-16 17:10 ` Russell King
[not found] ` <Pine.SOL.3.96.1030216224235.25827A-100000@osiris.csa.iisc.ernet.in>
2003-02-16 17:44 ` Russell King
2003-02-16 18:25 ` Daniel Jacobowitz
2003-02-17 3:33 ` Rahul Vaidya
2003-02-17 3:46 ` Daniel Jacobowitz
2003-02-17 3:54 ` Rahul Vaidya
2003-02-17 3:58 ` Daniel Jacobowitz
2003-02-17 4:03 ` Rahul Vaidya
2003-02-17 4:09 ` Daniel Jacobowitz
2003-02-17 5:08 ` Rahul Vaidya
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=20030216174637.C12489@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rahulv@csa.iisc.ernet.in \
--cc=zwane@holomorphy.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.