This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] rebuild libgcc properly

From: Andreas Schwab <schwab at suse dot de>
To: Mike Stump <mrs at apple dot com>
Cc: Ben Elliston <bje at au1 dot ibm dot com>, gcc-patches at gcc dot gnu dot org
Date: Fri, 07 Oct 2005 18:29:33 +0200
Subject: Re: [PATCH] rebuild libgcc properly
References: <4345C213.2080707@au.ibm.com><B6F6D4CC-942F-4969-AD8C-0F6B254BD0A0@apple.com>

Mike Stump <mrs@apple.com> writes:

> On Oct 6, 2005, at 5:32 PM, Ben Elliston wrote:
>> I have a habit of running rm -r libgcc (or `make clean-target- 
>> libgcc' from the top-level) to delete all of libgcc when I want to
>> force a rebuild due to compiler mods.
>
> :-)  I do rm libgcc/*.{o,vis} libgcc/*/*.{o,vis} which is  
> annoying...  I'd rather rm -rf libgcc...  :-)

rm -f stmp-dirs should fix it, doesn't it?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: [PATCH] rebuild libgcc properly
  - From: Mike Stump

References:
- [PATCH] rebuild libgcc properly
  - From: Ben Elliston
- Re: [PATCH] rebuild libgcc properly
  - From: Mike Stump

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]