From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: freebsd gcc cross compiler creates binaries that crash when using c++ exceptions
Date: Thu, 12 Jan 2012 19:25:00 -0000 [thread overview]
Message-ID: <4F0F2E4B.8030305@redhat.com> (raw)
In-Reply-To: <B6A6EF22B0D16146BD127139E7667DDB1625D0179A@hermes.corp.yager.de>
On 01/12/2012 06:55 PM, Markus Henschel wrote:
> Is there some flaw in the way I built this toolchain? Where could I try to start looking for the source of the problem? I can add all sorts of other outputs from the created toolchains if it helps.
I wouldn't put the installed compiler (i.e. the prefix=) into the
same directory as the sysroot. The sysroot should be a clean &
pristine copy of the root directories on your target. It isn't
written to, only read from. Once you have done your make install
you should have a set of target libraries that work in your
prefix/lib.
You can't mix the c++ and libgcc libraries you just built with the
versions on your target system. It should be possible to install
the newly-created ones side by side with the versions on your target
system.
If that still doesn't work, time to start gdb.
Andrew.
next prev parent reply other threads:[~2012-01-12 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 19:22 Markus Henschel
2012-01-12 19:25 ` Andrew Haley [this message]
2012-01-12 20:06 ` Markus Henschel
2012-01-13 15:34 ` Andrew Haley
2012-01-16 10:47 ` Markus Henschel
2012-01-16 10:54 ` Andrew Haley
2012-01-16 10:59 ` Andrew Haley
2012-01-17 10:14 ` Markus Henschel
2012-01-16 15:37 ` Kai Ruottu
2012-01-18 7:34 ` Markus Henschel
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=4F0F2E4B.8030305@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@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).