Re: std_limits.h os_defines.h

[Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>]

In article <271270000.997392405@gandalf.codesourcery.com> you write:

> Do you have time to look at the problem Gerald reported with colons
> in path names that is apparently triggered by the staging headers
> work?  That is one of the few regressions from 3.0, and we definitely
> need a solution.

Mark, here is the only solution I found.  It relies on the fact that
the built config.h file is always exactly one level up from
include/Makefile.  I could find no way to quote the use of a colon.
Also, please note that many other makes don't even allow a colon in a
target or dependency.

BTW, if someone puts their gcc source distribution in a path with a
colon, the problem will still appear.

Index: include/Makefile.am
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++-v3/include/Makefile.am,v
retrieving revision 1.2
diff -c -r1.2 Makefile.am
*** Makefile.am	2001/08/08 02:48:59	1.2
--- Makefile.am	2001/08/09 21:53:07
***************
*** 391,397 ****
  	fi
  	echo `date` > stamp-${target_alias}
  
! ${target_builddir}/c++config.h: ${glibcpp_builddir}/config.h \
  				${glibcpp_srcdir}/include/bits/c++config \
  				${target_builddir}
  	@cat ${glibcpp_srcdir}/include/bits/c++config > $@ ;\
--- 391,397 ----
  	fi
  	echo `date` > stamp-${target_alias}
  
! ${target_builddir}/c++config.h: ../config.h \
  				${glibcpp_srcdir}/include/bits/c++config \
  				${target_builddir}
  	@cat ${glibcpp_srcdir}/include/bits/c++config > $@ ;\