From: "Kaz Kylheku" <kaz@zeugmasystems.com>
To: <gdb@sourceware.org>
Subject: RE: How to coerce gdb into pseudo-cross-compiling when build == host?
Date: Tue, 03 Oct 2006 23:16:00 -0000 [thread overview]
Message-ID: <66910A579C9312469A7DF9ADB54A8B7D3E6E82@exchange.ZeugmaSystems.local> (raw)
David Daney wrote:
> Kaz Kylheku wrote:
> > I'm building a Linux system from scratch. Everything builds
> for MIPS and
> > i686 using the same script, except for gdb.
>
> 'path_to_gdb/configure --build=i686-pc-linux-gnu
> --target=mipsel-linux
> --host=mipsel-linux' does not work for you?
Oops, I didn't make myself perfectly clear. The MIPS cross-compile
works fine. It's when I have
--build=i686-linux
--target=i686-linux
--host=i686-linux
that it decides that there is no cross-compiling, and starts
just using plain gcc for compiling and linking. So gdb ends
up picking up my local /lib/libncurses.so.5.
I lied to it by doing this:
--build=i686-bsd
--target=i686-linux
--host=i686-linux
But there has to be a better way.
next reply other threads:[~2006-10-03 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 23:16 Kaz Kylheku [this message]
2006-10-03 23:44 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 23:51 Kaz Kylheku
2006-10-03 22:39 Kaz Kylheku
2006-10-03 22:57 ` David Daney
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=66910A579C9312469A7DF9ADB54A8B7D3E6E82@exchange.ZeugmaSystems.local \
--to=kaz@zeugmasystems.com \
--cc=gdb@sourceware.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