From: "Kaz Kylheku" <kaz@zeugmasystems.com>
To: <gdb@sourceware.org>
Subject: How to coerce gdb into pseudo-cross-compiling when build == host?
Date: Tue, 03 Oct 2006 22:39:00 -0000 [thread overview]
Message-ID: <66910A579C9312469A7DF9ADB54A8B7D3E6E61@exchange.ZeugmaSystems.local> (raw)
I'm building a Linux system from scratch. Everything builds for MIPS and
i686 using the same script, except for gdb.
The problem is that it thinks it's not being cross-compiled and starts
using plain "gcc" for compiling and linking, which brings in the build
system's local header files and libraries.
I want it to use the toolchain that my script built for it, which will
use the header files that I installed into the target filesystem tree,
and the libraries that the script built earlier: glibc, ncurses, etc.
I fooled gcc's configure into using "i686-linux-gcc" by lying to it
using --build=i686-bsd.
Everything worked.
But what's the a better way to do this, without lying about the OS?
Basically, the --build is totally irrelevant. It seem that I could put
in some nonsense like "mk68-solaris" and it would still work. Anything
/but/ the actual architecture and OS that I'm actually building on.
next reply other threads:[~2006-10-03 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 22:39 Kaz Kylheku [this message]
2006-10-03 22:57 ` David Daney
2006-10-03 23:16 Kaz Kylheku
2006-10-03 23:44 ` Daniel Jacobowitz
2006-10-03 23:51 Kaz Kylheku
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=66910A579C9312469A7DF9ADB54A8B7D3E6E61@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