From mboxrd@z Thu Jan  1 00:00:00 1970
From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: fixing the c++/f77 circular dependency
Date: Mon, 25 Aug 1997 20:25:15 -0000
Message-id: <m0x35hp-0004ecC@ocean.lucon.org>
In-reply-to: 199708252008.NAA18706@cygnus.com
X-SW-Source: 1997-08/0436.html

> 
> 	Could someone please tell me why we cannot put a target libgcc.a in
> 	cp/Makefile.in? It will resolve that problem. I am willing to
> 	write a patch if people think it is a good idea.
> 
> There is a serious dependency problem which has already been mentioned a few
> times.  If libgcc.a contains C++ code, then libgcc.a depends on cc1plus,
> which means we always build cc1plus even if it is not in languages.  Simply
> moving the rule to cp/Makefile.in does not solve this problem, because
> we still have libgcc.a dependencing on cc1plus.
> 

What I have in mind is

1. In top level Makefile:

libgcc.a: .... cc1 subdir_libgcc
	autolock.sh libgcc.a.lck $(AR) ..

subdir_libgcc: cc1
	for d in  ...
	do
		$(MAKE) libgcc.a
	done

2. In cp/Makefile, we have

libgcc.a: ../cc1 ../cc1plus
	.....
	autolock.sh ../libgcc.a.lck $(AR) ..


H.J.