This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: SUN make and gcc 3.0: committed changes to branch
- To: pedwards at disaster dot jaj dot com
- Subject: Re: SUN make and gcc 3.0: committed changes to branch
- From: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Date: Thu, 31 May 2001 23:25:10 +0200
- CC: hans-peter dot nilsson at axis dot com, aoliva at redhat dot com, bkoz at redhat dot com, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
> Date: Thu, 31 May 2001 15:41:00 -0400
> From: Phil Edwards <pedwards@disaster.jaj.com>
> On Thu, May 31, 2001 at 10:46:38PM +0200, Hans-Peter Nilsson wrote:
> > Easy now; a patch with explicit-and-fixed header install rules
> > I'm bootstrapping and checking (on one of the slowest machines I
> > have access to) looks like it will make it through the needles
> > eye.
>
> This is good to hear. But what gives me a headache every time I think
> about it (thus, brain exploding) is: how is this supposed to work in the
> general case? Is it just a situation of, "automake-generated installation,
> separate objdir, non-GNU make. Picking any two rules out the third."
I see it mainly as a workaround for a shortcoming (dare I say
bug without getting flamed) of automake. Again, automake *does*
explicitly support SUN make VPATHisms for some of its generated
rules, and does not document otherwise. It's just that the
generated rule for installing headers does not support SUN make
VPATH.
brgds, H-P