public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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, 15 Jul 2011 09:38:00 -0000	[thread overview]
Message-ID: <ydd39i7q5fd.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <1310594583.10986.2819.camel@hpsje.cup.hp.com> (Steve Ellcey's	message of "Wed, 13 Jul 2011 15:03:03 -0700")

Steve,

> I have successfully bootstrapped and tested the toplevel libgcc patch on
> IA64 HP-UX.  When trying to build IA64 Linux the bootstrap failed with:

great, thanks.

> /bin/sh /wsp/sje/gcc_git/src/gcc/libgcc/../mkinstalldirs ./wsp/sje/gcc_git/build-ia64-debian-linux-gnu-gcc/obj_gcc/./gcc/xgcc -B/wsp/sje/gcc_git/build-ia64-debian-linux-gnu-gcc/obj_gcc/./gcc/ -B/wsp/sje/gcc_git/gcc-ia64-debian-linux-gnu-gcc/ia64-debian-linux-gnu/bin/ -B/wsp/sje/gcc_git/gcc-ia64-debian-linux-gnu-gcc/ia64-debian-linux-gnu/lib/ -isystem /wsp/sje/gcc_git/gcc-ia64-debian-linux-gnu-gcc/ia64-debian-linux-gnu/include -isystem /wsp/sje/gcc_git/gcc-ia64-debian-linux-gnu-gcc/ia64-debian-linux-gnu/sys-include    -O2  -g -O2 -DIN_GCC   -DUSE_LIBUNWIND_EXCEPTIONS -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -fPIC -DUSE_GAS_SYMVER -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector  -shared -nodefaultlibs -Wl,-h,libunwind.so.7 -Wl,-z,text -Wl,-z,defs -o /libunwind.so.7.tmp -g -O2 -B./  -lc && rm -f / && if [ -f /libunwind.so.7 ]; then mv -f /libunwind.so.7 /libunwind.so.7.backup; else true; fi && mv /libunwind.so.7.tmp /libunwind.so.7 && ln -s libunwind.so.7 /
> /wsp/sje/gcc_git/gcc-ia64-debian-linux-gnu-gcc/ia64-debian-linux-gnu/bin/ld: cannot open output file /libunwind.so.7.tmp: Permission denied
> collect2: error: ld returned 1 exit status
[...]
> It looks like a prefix is missing somewhere since it is trying to access /libunwind.so.  This
> may be something messed up in my build area again but I did run autoconf in libgcc so I am
> not sure what is going on.  I'll dig around some more but I thought I would see if this looks
> familiar to you.

It didn't, but I now see what's going on: gcc/config.gcc has

*-*-linux* | frv-*-*linux* | *-*-kfreebsd*-gnu | *-*-knetbsd*-gnu | *-*-gnu* | *-*-kopensolaris*-gnu)
[...]
  tmake_file="t-slibgcc-elf-ver t-linux"

t-slibgcc-elf-ver has the whole shebang necessary to build versioned ELF
shared libraries, among others SHLIB_DIR which is missing above.  This
should be dealt with by using

tmake_file="$tmake_file t-slibgcc t-slibgcc-elf-ver"

in libgcc/config.host.

t-linux adds

SHLIB_MAPFILES += $(srcdir)/config/libgcc-glibc.ver

but there's more SHLIB_* related stuff in the regular gcc/config ia64
t-* files used on ia64*-*-linux*:

ia64/t-ia64:SHLIB_MAPFILES += $(srcdir)/config/ia64/libgcc-ia64.ver
t-libunwind:SHLIB_LC = -lunwind -lc
ia64/t-glibc:SHLIB_MAPFILES += $(srcdir)/config/ia64/libgcc-glibc.ver

This seems all so involved and entangled with the t-slibgcc* stuff that
it's probably best to keep out of this patch.  I'll try to come up with
something over the week, either fixing up this patch that it should
handle things correctly or splitting it out into its own, either
together with the rest of SHLIB_* handling or separate and on top of
that.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2011-07-15  9:06 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
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 [this message]
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=ydd39i7q5fd.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).