public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc-patches@gcc.gnu.org, dave.anglin@nrc-cnrc.gc.ca
Subject: Re: libgcc move to the top level
Date: Mon, 08 Jan 2007 22:51:00 -0000	[thread overview]
Message-ID: <20070108225119.GA29520@nevyn.them.org> (raw)
In-Reply-To: <200701082231.OAA03151@hpsje.cup.hp.com>

On Mon, Jan 08, 2007 at 02:31:30PM -0800, Steve Ellcey wrote:
> > It ought to have some $(T)s in it.  Does this help?
> > 
> > $(T)libgcc_stub.a: $(LIBGCCSTUB_OBJS)
> >         -rm -rf $(T)libgcc_stub.a
> >         $(AR) rc $(T)libgcc_stub.a $(LIBGCCSTUB_OBJS)
> >         $(RANLIB) $(T)libgcc_stub.a
> > 
> > -- 
> > Daniel Jacobowitz
> > CodeSourcery
> 
> Yup, that fixed it and I successfully bootstrapped hppa64-hp-hpux11.11.
> Are you going to check it in?

OK, done.  You might want to check that "make install" installs
everything it's supposed to - I think it will, but I had more
trouble with installation than I expected from these changes.

-- 
Daniel Jacobowitz
CodeSourcery

2007-01-08  Daniel Jacobowitz  <dan@codesourcery.com>

	* config/pa/t-pa64 (libgcc_stub.a): Use $(T).

Index: config/pa/t-pa64
===================================================================
--- config/pa/t-pa64	(revision 120594)
+++ config/pa/t-pa64	(working copy)
@@ -22,7 +22,7 @@ jvrc-stub.o: stublib.c $(GCC_PASSES)
 	$(GCC_FOR_TARGET) -c -O2 -DL_Jv_RegisterClasses stublib.c \
 	  -o jvrc-stub.o
 
-libgcc_stub.a: $(LIBGCCSTUB_OBJS)
-	-rm -rf libgcc_stub.a
-	$(AR) rc libgcc_stub.a $(LIBGCCSTUB_OBJS)
-	$(RANLIB) libgcc_stub.a
+$(T)libgcc_stub.a: $(LIBGCCSTUB_OBJS)
+	-rm -rf $(T)libgcc_stub.a
+	$(AR) rc $(T)libgcc_stub.a $(LIBGCCSTUB_OBJS)
+	$(RANLIB) $(T)libgcc_stub.a

  reply	other threads:[~2007-01-08 22:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-17  3:15 Daniel Jacobowitz
2006-12-17  3:48 ` Daniel Jacobowitz
2006-12-19 16:09 ` Paolo Bonzini
2006-12-19 19:18   ` Daniel Jacobowitz
2006-12-19 20:06     ` Paolo Bonzini
2006-12-19 20:26       ` Daniel Jacobowitz
2006-12-20  7:56         ` Paolo Bonzini
2006-12-29  2:09           ` Daniel Jacobowitz
2006-12-29 10:55             ` Paolo Bonzini
2006-12-20  0:23       ` Mike Stump
2006-12-20  0:35         ` Daniel Jacobowitz
2006-12-29 11:27     ` Paolo Bonzini
2006-12-29 14:50       ` Daniel Jacobowitz
2006-12-29 15:29         ` Paolo Bonzini
2006-12-29 16:13           ` Daniel Jacobowitz
2006-12-29 16:31             ` Paolo Bonzini
2006-12-29 16:36               ` Daniel Jacobowitz
2006-12-29 16:42                 ` Paolo Bonzini
2006-12-29 18:01             ` Daniel Jacobowitz
2006-12-30  8:20               ` Paolo Bonzini
2006-12-30 20:19                 ` Daniel Jacobowitz
2006-12-31 18:43                   ` Paolo Bonzini
2006-12-31 19:56                     ` Daniel Jacobowitz
2007-01-01 18:10                       ` Paolo Bonzini
2007-01-01 21:14                         ` Mike Stump
2007-01-08 18:17                         ` Steve Ellcey
2007-01-08 18:47                           ` Daniel Jacobowitz
2007-01-08 22:32                             ` Steve Ellcey
2007-01-08 22:51                               ` Daniel Jacobowitz [this message]
2007-01-04 12:32                       ` Andreas Schwab
2007-01-04 14:05                         ` Daniel Jacobowitz
2007-01-04 14:57                           ` Marcin Dalecki
2007-01-04 15:02                             ` Daniel Jacobowitz
2007-01-04 15:09                               ` Paolo Bonzini
2007-01-04 15:32                                 ` Marcin Dalecki
2007-01-04 15:39                                   ` Paolo Bonzini
2007-01-04 18:05                                     ` Marcin Dalecki
2007-01-04 16:13                               ` Marcin Dalecki
2007-01-04 16:34                                 ` Daniel Jacobowitz
2007-01-04 17:13                                   ` Marcin Dalecki
2007-01-04 16:52                           ` Daniel Jacobowitz

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=20070108225119.GA29520@nevyn.them.org \
    --to=drow@false.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=gcc-patches@gcc.gnu.org \
    --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).