From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Nicu Popovici <octavp@isratech.ro>, linux-mips@oss.sgi.com
Subject: Re: MIPS kernel!
Date: Wed, 8 Nov 2000 15:10:48 +0100 [thread overview]
Message-ID: <20001108151048.A13841@bacchus.dhis.org> (raw)
In-Reply-To: <004101c04969$b744b160$0323c0d8@Ulysses>; from kevink@mips.com on Wed, Nov 08, 2000 at 10:53:14AM +0100
On Wed, Nov 08, 2000 at 10:53:14AM +0100, Kevin D. Kissell wrote:
> In general, at MIPS, we generally build native or semi-native
> (mipsel on mipseb machines and vice versa). In cross-builds
> of other components, however, I have observed that problems
> such as those you describe can result from include files
> on the host platform being erroneously pulled in to the cross-build.
> Cross-gcc and the makefiles have been known to be set up such
> that, if the needed include file can be found neither in the explicitly
> requested directories nor in the cross-compiler's default includes,
> it will silently search the host /usr/include directories.
This is either a bug in the version that you're using, a wrongly installed
compiled or simply wrong -I directives passed to the compiler. The
crosscompiler rpms as distributed on oss will only search:
/usr/lib/gcc-lib/mips-linux/egcs-2.91.66/include
/usr/mips-linux/include
by default. I just tried, egcs-1.1.2-2 also doesn't search silently in
other directories. So it's not a problem of gcc itself which leaves the
makefiles. If you find any instance of the wrong directories being
searched, please tell me. Or better, include a patch :-)
Ralf
next prev parent reply other threads:[~2000-11-08 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 15:46 MIPS kernel! Nicu Popovici
2000-11-08 9:53 ` Kevin D. Kissell
2000-11-08 9:53 ` Kevin D. Kissell
2000-11-08 14:10 ` Ralf Baechle [this message]
2000-11-08 20:07 ` Kevin D. Kissell
2000-11-08 20:11 ` Ralf Baechle
[not found] ` <3A09D68C.AF1D5AAA@isratech.ro>
[not found] ` <20001108205319.A870@bacchus.dhis.org>
2000-11-09 14:57 ` Nicu Popovici
2000-11-09 8:24 ` Klaus Naumann
2000-11-09 8:29 ` Carsten Langgaard
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=20001108151048.A13841@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=octavp@isratech.ro \
/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