From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Massive breakage with your libgcc patches
Date: Thu, 03 Nov 2011 15:42:00 -0000 [thread overview]
Message-ID: <ydd1utp443h.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <201111031525.pA3FP8WJ015742@ignucius.se.axis.com> (Hans-Peter Nilsson's message of "Thu, 3 Nov 2011 16:25:08 +0100")
Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:
>> From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
>> Date: Thu, 3 Nov 2011 14:10:50 +0100
>
>> Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:
>> > For cris-elf, a patch in the range 180770:180778 supposedly
>> > yours, cause massive testsuite failures on the form of not
>> > finding functions in libgcc at link-time.
>
> It seems it was just a missing t-fdpbit for cris-*-elf.
> I'll test the obvious fix (fingers crossed).
I'm glad if it's that easy (though stupid ;-) Thanks for the detective
work.
> The testing issue aside, thanks for doing this work and staying
> on it.
Thanks. I had been looking into crosstool-NG for easily setting up a
cross environment, but several issues got in the way.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-11-03 15:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 17:53 CFT: [build] Move crtstuff support to toplevel libgcc Rainer Orth
2011-08-15 21:00 ` Hans-Peter Nilsson
2011-08-16 17:13 ` Rainer Orth
2011-11-02 12:49 ` Rainer Orth
2011-11-02 20:16 ` Massive breakage with your libgcc patches Hans-Peter Nilsson
2011-11-02 20:26 ` Bernd Schmidt
2011-11-03 13:17 ` Rainer Orth
2011-11-03 13:58 ` Bernd Schmidt
2011-11-03 17:28 ` Rainer Orth
2011-11-03 17:54 ` Bernd Schmidt
2011-11-03 18:15 ` Rainer Orth
2011-11-03 18:48 ` Bernd Schmidt
2011-11-03 19:31 ` Rainer Orth
2011-11-04 12:01 ` Bernd Schmidt
2011-11-07 13:46 ` Bernd Schmidt
2011-11-07 18:38 ` Rainer Orth
2011-11-08 13:27 ` Paolo Bonzini
2011-11-21 16:41 ` Rainer Orth
2011-11-21 16:46 ` Paolo Bonzini
2011-11-08 16:56 ` Bernd Schmidt
2011-11-08 18:02 ` Rainer Orth
2011-11-29 16:22 ` Bernd Schmidt
2011-11-29 16:28 ` Paolo Bonzini
2011-11-03 13:14 ` Rainer Orth
2011-11-03 14:46 ` Hans-Peter Nilsson
2011-11-03 15:42 ` Hans-Peter Nilsson
2011-11-03 15:42 ` Rainer Orth [this message]
2011-11-02 21:29 ` CFT: [build] Move crtstuff support to toplevel libgcc Jason Merrill
2011-11-02 21:47 ` Jason Merrill
2011-11-03 13:07 ` Rainer Orth
2011-11-03 13:12 ` Paolo Bonzini
2011-11-03 16:09 ` Jason Merrill
2011-11-03 11:01 ` Andreas Schwab
2011-11-03 11:37 ` Matthew Gretton-Dann
2011-11-03 16:42 ` Rainer Orth
2011-11-04 13:43 ` Andreas Krebbel
2011-11-04 14:34 ` Rainer Orth
2011-11-04 14:38 ` Andreas Krebbel
2011-11-04 14:54 ` Rainer Orth
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=ydd1utp443h.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hans-peter.nilsson@axis.com \
/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).