This is the mail archive of the
mailing list for the GCC project.
Re: odd Makefile construct - anyone know why?
- To: "Zack Weinberg" <zackw at stanford dot edu>
- Subject: Re: odd Makefile construct - anyone know why?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 01 Nov 2000 09:58:26 -0700
- cc: gcc at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <20001021153119.J16750@wolery.stanford.edu>you write:
> In a large number of places we have Makefile constructs such as
> $(CC) -c $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) $(BIG_SWITCHFLAG) \
> `echo $(PARSE_C) | sed 's,^\./,,'`
> Does anyone know the reason for the `echo | sed` bit? I know it
> deletes a './' from the beginning of whatever $(PARSE_C) is, but I
> cannot figure out why that would be necessary. This is done whenever
> we override the suffix rule for compiling a file.
Possibly for the debugger? I've always wondered about this braindamage