From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: sje@cup.hp.com
Cc: Tristan Gingold <gingold@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Douglas Rupp <rupp@gnat.com>
Subject: Re: CFT: Move unwinder to toplevel libgcc
Date: Fri, 08 Jul 2011 18:24:00 -0000 [thread overview]
Message-ID: <yddtyawy78z.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <1310057170.10986.2613.camel@hpsje.cup.hp.com> (Steve Ellcey's message of "Thu, 07 Jul 2011 09:46:10 -0700")
Steve,
> It looks like the GCC build is trying to compile unwind-ia64.c on IA64
> HP-UX even though it should not use or need this file. Using
> --with-system-libunwind doesn't seem to help. I am not sure where this
> should be handled under the new setup. Previously config.gcc would
> either include or not include t-glibc-libunwind in the Makefile to build
> or not build this file. This might be coming from t-eh-ia64 rather
> then t-glibc-libunwind. Both of these include unwind-ia64.c.
I see what's going on: before my patch, ia64*-*-hpux* would use
tmake_file="ia64/t-ia64 ia64/t-hpux"
The former has
LIB2ADDEH = $(srcdir)/config/ia64/unwind-ia64.c $(srcdir)/unwind-sjlj.c \
$(srcdir)/unwind-c.c
the latter
LIB2ADDEH = $(srcdir)/unwind-c.c
overriding the ia64 default.
Unfortunately, I got the ordering wrong in libgcc:
tmake_file="ia64/t-hpux ia64/t-eh-ia64"
To fix this, ia64/t-eh-ia64 can go completely. This should restore
things as they were before.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-07-08 18:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 12:44 [build] " Rainer Orth
2011-06-20 15:21 ` Joseph S. Myers
2011-06-20 15:23 ` Rainer Orth
2011-06-20 15:37 ` Joseph S. Myers
2011-06-20 15:47 ` Rainer Orth
2011-07-04 18:10 ` CFT: " Rainer Orth
2011-07-05 9:35 ` Tristan Gingold
2011-07-07 13:11 ` Rainer Orth
2011-07-07 15:53 ` Steve Ellcey
2011-07-08 18:16 ` Rainer Orth
2011-07-07 16:48 ` Steve Ellcey
2011-07-08 18:24 ` Rainer Orth [this message]
2011-07-07 17:08 ` Steve Ellcey
2011-07-07 22:55 ` Steve Ellcey
2011-07-08 18:55 ` Rainer Orth
2011-07-08 20:18 ` Steve Ellcey
2011-07-12 17:24 ` Steve Ellcey
2011-07-12 17:40 ` Rainer Orth
2011-07-12 17:42 ` Steve Ellcey
2011-07-14 1:47 ` Steve Ellcey
2011-07-15 9:38 ` Rainer Orth
2011-07-18 12:07 ` Rainer Orth
2011-07-18 17:50 ` Steve Ellcey
2011-07-19 11:43 ` Rainer Orth
2011-07-20 23:03 ` Steve Ellcey
2011-07-22 15:36 ` Rainer Orth
2011-07-22 18:56 ` Steve Ellcey
2011-07-22 19:03 ` Rainer Orth
2011-07-22 22:20 ` Steve Ellcey
2011-07-25 17:07 ` Rainer Orth
2011-06-29 10:05 ` [build] " Paolo Bonzini
2011-06-29 10:06 ` Rainer Orth
2011-06-29 11:29 ` Joseph S. Myers
2011-06-29 11:33 ` Paolo Bonzini
2011-06-29 12:40 ` Rainer Orth
2011-06-29 12:17 ` 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=yddtyawy78z.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=rupp@gnat.com \
--cc=sje@cup.hp.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).