This is the mail archive of the gcc@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]

Re: odd Makefile construct - anyone know why?


  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
myself.

jeff


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