From: Russell King <rmk@arm.linux.org.uk>
To: Rahul Vaidya <rahulv@csa.iisc.ernet.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux 2.5.53 not compiling
Date: Sun, 16 Feb 2003 17:44:11 +0000 [thread overview]
Message-ID: <20030216174411.B12489@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.SOL.3.96.1030216224235.25827A-100000@osiris.csa.iisc.ernet.in>; from rahulv@csa.iisc.ernet.in on Sun, Feb 16, 2003 at 10:43:01PM +0530
Please copy replies back to lkml.
On Sun, Feb 16, 2003 at 10:43:01PM +0530, Rahul Vaidya wrote:
> the command is giving me the following:
>
> Reading specs from
> /usr/local/gcc-3.2/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
> Configured with: ../gcc-3.2/configure --prefix=/usr/local/gcc-3.2
> Thread model: posix
> gcc version 3.2
> /usr/local/gcc-3.2/lib/gcc-lib/i686-pc-linux-gnu/3.2/cpp0 -lang-c -v
> -iprefix /usr/local/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.2/
^^^^^^^^^^
It looks like gcc 3.2 thinks its compiler prefix is in a place where it
is not. I'd suggest you report this to the gcc people; at a guess, it
may be due to gcc getting confused during its configuration:
../gcc-3.2/configure --prefix=/usr/local/gcc-3.2
^^^
> -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=0
> -D__GXX_ABI_VERSION=102 -D__ELF__ -Dunix -D__gnu_linux__ -Dlinux
> -D__ELF__ -D__unix__ -D__gnu_linux__ -D__linux__ -D__unix
> -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1
> -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i686__
> -D__tune_pentiumpro__ -iwithprefix include -
>
> ignoring nonexistent directory "/usr/local/lib/gcc-lib/
> i686-pc-linux-gnu/3.2/include"
> GNU CPP version 3.2 (cpplib) (i386 Linux/ELF)
> ignoring nonexistent directory "/usr/local/lib/gcc-lib/
> i686-pc-linux-gnu/3.2/include"
> ignoring nonexistent directory "/usr/local/lib/gcc-lib/
> i686-pc-linux-gnu/3.2/../../../../i686-pc-linux-gnu/include"
> ignoring nonexistent directory "/usr/local/gcc-3.2/
> i686-pc-linux-gnu/include"
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/local/include
> /usr/local/gcc-3.2/include
> /usr/local/gcc-3.2/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
> /usr/include
> End of search list.
--
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:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 17:02 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
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 [this message]
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=20030216174411.B12489@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rahulv@csa.iisc.ernet.in \
/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
all inboxes | Powered by JetHome®