From: Steve Ellcey <sje@cup.hp.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
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: Tue, 12 Jul 2011 17:24:00 -0000 [thread overview]
Message-ID: <1310491090.10986.2693.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <yddpqlky6x8.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
Rainer,
I did another GCC build with your libgcc patch and with fixes for the
two problems I already mentioned to you and got another failure:
libtool: compile: /wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/./gcc/xgcc -shared-libgcc -B/wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/./gcc -nostdinc++ -L/wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/src -L/wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/src/.libs -B/wsp/sje/gcc_git/gcc-ia64-hp-hpux11.23-gcc/ia64-hp-hpux11.23/bin/ -B/wsp/sje/gcc_git/gcc-ia64-hp-hpux11.23-gcc/ia64-hp-hpux11.23/lib/ -isystem /wsp/sje/gcc_git/gcc-ia64-hp-hpux11.23-gcc/ia64-hp-hpux11.23/include -isystem /wsp/sje/gcc_git/gcc-ia64-hp-hpux11.23-gcc/ia64-hp-hpux11.23/sys-include -I/wsp/sje/gcc_git/src/gcc/libstdc++-v3/../gcc -I/wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/include/ia64-hp-hpux11.23 -I/wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/include -I/wsp/sje/gcc_git/src/gcc/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -O2 -c /wsp/sje/gcc_git/src/gcc/libstdc++-v3/libsupc++/eh_call.cc -fPIC -DPIC -o eh_call.o
/wsp/sje/gcc_git/src/gcc/libstdc++-v3/libsupc++/eh_call.cc:34:23: fatal error: unwind-pe.h: No such file or directory
compilation terminated.
make[4]: *** [eh_call.lo] Error 1
make[4]: Leaving directory `/wsp/sje/gcc_git/build-ia64-hp-hpux11.23-gcc/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/libsupc++'
make[3]: *** [all-recursive] Error 1
I think in my earlier build I was building C only (or maybe the compiler only) and that is why I didn't
see this problem.
I think the libstdc++ Makefile needs to add
-I/wsp/sje/gcc_git/src/gcc/libstdc++-v3/../libgcc
in addition (or instead of)
-I/wsp/sje/gcc_git/src/gcc/libstdc++-v3/../gcc
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2011-07-12 17:18 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
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 [this message]
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=1310491090.10986.2693.camel@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=rupp@gnat.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).