public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/14147] Cross-Compilation fails
Date: Sun, 15 Feb 2004 17:15:00 -0000 [thread overview]
Message-ID: <20040215171516.7894.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040214151005.14147.joachim.eibl@gmx.de>
------- Additional Comments From dhazeghi at yahoo dot com 2004-02-15 17:15 -------
Do a google search for building a linux cross-compiler. You need headers (and libraries) from the
system you're targetting. See <http://bytesex.org/cross-compiler.html> for general info. See --with-
sysroot or --with-libs and --with-headers option in the install docs too (you will need them) <http://
gcc.gnu.org/install/configure.html>. Bottom line is that cross-compiling most definitely does work, but
you need a bit of setup before hand to make it happy... Dan Kegel's crosstool may also be helpful. We
already have another open bug for the out-of-date/missing documentation on all this.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14147
next prev parent reply other threads:[~2004-02-15 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 15:10 [Bug c/14147] New: " joachim dot eibl at gmx dot de
2004-02-14 15:16 ` [Bug other/14147] " ebotcazou at gcc dot gnu dot org
2004-02-14 19:12 ` pinskia at gcc dot gnu dot org
2004-02-15 12:13 ` joachim dot eibl at gmx dot de
2004-02-15 12:21 ` joachim dot eibl at gmx dot de
2004-02-15 14:17 ` joachim dot eibl at gmx dot de
2004-02-15 17:15 ` dhazeghi at yahoo dot com [this message]
2004-02-15 22:52 ` joachim dot eibl at gmx dot de
2004-02-16 0:53 ` dhazeghi at yahoo dot com
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=20040215171516.7894.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).