public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/25035] [4.1/4.2 regression] libssp causes a failure with cross compilers with unified trees
Date: Wed, 30 Aug 2006 03:32:00 -0000 [thread overview]
Message-ID: <20060830033222.9928.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25035-283@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from pinskia at gcc dot gnu dot org 2006-08-30 03:32 -------
(In reply to comment #15)
> (In reply to comment #14)
> > This works for me with a cross (and sysroot) to powerpc-linux-gnu from a
> > i686-linux-gnu.
> >
> Is that a unified tree build with newlib?
No it is not, it is a non unified tree at all, I have glibc and binutils
already built before compiling the cross compiler.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC target triplet|host != target |host != target and unified
| |build
Summary|[4.1/4.2 regression] libssp |[4.1/4.2 regression] libssp
|causes a failure with cross |causes a failure with cross
|compilers |compilers with unified trees
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25035
next prev parent reply other threads:[~2006-08-30 3:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 18:22 [Bug target/25035] New: Building an avr cross compiler fails berndtrog at yahoo dot com
2005-11-25 20:28 ` [Bug other/25035] " pinskia at gcc dot gnu dot org
2005-12-05 19:06 ` [Bug other/25035] [4.1/4.2 regression] Building an avr cross compiler fails (libssp) berndtrog at yahoo dot com
2006-01-03 15:33 ` bjoern dot m dot haase at web dot de
2006-01-19 16:22 ` eweddington at cso dot atmel dot com
2006-05-07 8:51 ` [Bug other/25035] [4.1/4.2 regression] libssp causes a failure with cross compilers pinskia at gcc dot gnu dot org
2006-05-14 22:26 ` mmitchel at gcc dot gnu dot org
2006-05-15 17:25 ` bjoern dot m dot haase at web dot de
2006-05-25 2:39 ` mmitchel at gcc dot gnu dot org
2006-06-23 12:28 ` info at yourkit dot com
2006-06-28 21:18 ` pinskia at gcc dot gnu dot org
2006-07-24 5:51 ` echristo at apple dot com
2006-07-24 5:54 ` pinskia at gcc dot gnu dot org
2006-08-05 3:36 ` dje at gcc dot gnu dot org
2006-08-18 4:19 ` pinskia at gcc dot gnu dot org
2006-08-29 15:30 ` amylaar at gcc dot gnu dot org
2006-08-30 3:32 ` pinskia at gcc dot gnu dot org [this message]
2006-08-30 21:13 ` [Bug other/25035] [4.1/4.2 regression] libssp causes a failure with cross compilers with unified trees eweddington at cso dot atmel dot com
2006-09-29 21:19 ` jsm28 at gcc dot gnu dot org
2006-09-29 21:27 ` jsm28 at gcc dot gnu dot org
2006-09-30 8:27 ` pinskia at gcc dot gnu dot org
2008-02-12 18:27 ` Rudolf dot Leitgeb at gmx dot at
2008-02-12 19:39 ` eric dot weddington at atmel dot com
2008-02-12 19:44 ` eric dot weddington at atmel dot com
2008-02-12 23:27 ` eric dot weddington at atmel dot com
2008-02-13 8:46 ` Rudolf dot Leitgeb at gmx dot at
2008-03-30 20:09 ` pinskia at gcc dot gnu dot org
2008-05-26 22:48 ` eric dot weddington at atmel dot com
[not found] <bug-25035-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:17 ` jackie.rosen at hushmail 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=20060830033222.9928.qmail@sourceware.org \
--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).