From: Jared Young <headgeek@li.nu-x.net>
To: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: Small bug in linux-2.4.20/include/linux/kernel.h
Date: Fri, 31 Jan 2003 00:25:33 -0500 [thread overview]
Message-ID: <20030131002533.35562d87.headgeek@li.nu-x.net> (raw)
In-Reply-To: <20030130211305.5127a678.akpm@digeo.com>
On Thu, 30 Jan 2003 21:13:05 -0800
Andrew Morton <akpm@digeo.com> wrote:
> I was bitten by this when I built up gcc-3.2.1.
>
> In earlier gcc's you could have
>
> ln -s /usr/local/gcc-3.0/bin/gcc /usr/local/bin/gcc
>
> and it would all work OK.
>
> But in recent gcc's, that does not work. You actually have to add
> /usr/local/gcc-3.2.1/bin to your $PATH, and execute gcc from there.
>
> The problem also goes away when you remove -notsdinc from the kernel
> makefiles. So it seems that something changed in the way in which gcc
> locates the compiler-provided headers.
>
> In short: check your compiler setup.
That was exactly it, thank you very much. Bloody GCC-3.2.1, luckily I have GCC-2.95.3 still on this box..
--
?
???
?????
????????????????????????????????????????????????????????????????????
????????????????????????????????????????????????????????????????????
????? Jared A, Young 602 Crown Point Drive (757)246-1060 ?????
????? SC-Inetworks, Inc. Newport News, Virginia 23602-7009 ?????
????? ???????????????????????????????????????????????????????? ?????
????? Headgeek@sc-inetworks.net General Inquiries ?????
????? Admin@sc-inetworks.net Administrative Contact ?????
????? Support@sc-inetworks.net Technical Support ?????
????????????????????????????????????????????????????????????????????
????????????????????????????????????????????????????????????????????
?????
???
?
next prev parent reply other threads:[~2003-01-31 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 4:58 Jared Young
2003-01-31 5:13 ` Andrew Morton
2003-01-31 5:25 ` Jared Young [this message]
2003-01-31 9:32 ` Horst von Brand
2003-02-04 7:36 ` Denis Vlasenko
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=20030131002533.35562d87.headgeek@li.nu-x.net \
--to=headgeek@li.nu-x.net \
--cc=akpm@digeo.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
all inboxes | Powered by JetHome®