From: Kai Ruottu <kai.ruottu@wippies.com>
To: Andrew Haley <aph@redhat.com>
Cc: Martin Guy <martinwguy@yahoo.it>,
Henrik Grindal Bakken <hgb@ifi.uio.no>,
gcc-help@gcc.gnu.org
Subject: Re: Problem with exceptions on arm
Date: Tue, 01 Apr 2008 10:32:00 -0000 [thread overview]
Message-ID: <47F20D74.8060405@wippies.com> (raw)
In-Reply-To: <47F207C7.2070903@redhat.com>
Andrew Haley wrote:
> Is there something weird going on here, like different libraries
> in x-host and target?
Nice to see someone else suspecting weirdness in the current ideas.
The first message in this thread told :
"This is part of a larger script setting up a cross-compiling
toolchain. binutils, glibc and a first-stage gcc for arm is already
built at this point. I have tried gcc-4.2.2 and gcc-4.2.3. Our
codebase isn't quite ready for 4.3 yet...
When I run on target, a simple test program with exceptions fail:"
The weird thing here is that installing the produced glibc runtime
onto the target isn't mentioned. People produce glibc when the target
yet hasn't it, if it has it then there is no reason to try to create
that "byte-by-byte identical" target C library...
next prev parent reply other threads:[~2008-04-01 10:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 10:10 Henrik Grindal Bakken
2008-03-29 18:54 ` Martin Guy
2008-03-31 6:41 ` Henrik Grindal Bakken
2008-03-31 12:09 ` Andrew Haley
2008-03-31 12:21 ` Henrik Grindal Bakken
2008-03-31 12:40 ` Martin Guy
2008-03-31 12:45 ` Henrik Grindal Bakken
2008-04-01 8:25 ` Henrik Grindal Bakken
2008-04-01 10:01 ` Martin Guy
2008-04-01 10:13 ` Andrew Haley
2008-04-01 10:32 ` Kai Ruottu [this message]
2008-04-01 11:04 ` Henrik Grindal Bakken
2008-04-01 16:30 ` Andrew Haley
2008-04-01 10:51 ` Henrik Grindal Bakken
2008-04-01 12:16 ` Henrik Grindal Bakken
2008-04-01 10:21 ` Henrik Grindal Bakken
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=47F20D74.8060405@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=hgb@ifi.uio.no \
--cc=martinwguy@yahoo.it \
/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).