Paul Eggert wrote: > > However if I change it to use "" inclusion it works. > > OK, thanks, then we might as well try using "" everywhere. I'm more > comfortable with "///..." anyway; the <///...> gave me the willies, > since a compiler might think it was a C99 comment.
Ew, yes, that does seem disconcerting. > I installed this into gnulib and coreutils: > ... > - [<AS_VAR_GET(gl_absolute_header)>], > + ["AS_VAR_GET(gl_absolute_header)"], I definitely have that in CVS but I am still failing compile with the same problem. The generated stdint.h file still has the old <///data>. Looking in the Makefile I still see the <///usr...> path listed there which is part of the sed that builds that file. This is with a clean checkout. Is there another location where this needs to be changed but got missed? I think there must be. This command yields interesting results: find . -name CVS -prune -o -type f -print0 | xargs -r0 grep '///usr'| less Here are some highlights: ./lib/Makefile:ABSOLUTE_STDINT_H = <///usr/include/stdint.h> ./lib/stdint.h:# include <///usr/include/stdint.h> ./config.status:s,@ABSOLUTE_STDINT_H@,|#_!!_#|<///usr/include/stdint.h>,g ./config.status:s,^\([ #]*\)[^ ]*\([ ]*ABSOLUTE_STDINT_H\)[ (].*,\1define\2 "///usr/include/stdint.h" , ... ./config.log:gl_cv_absolute_stdint_h=///usr/include/stdint.h ./config.log:ABSOLUTE_STDINT_H='<///usr/include/stdint.h>' ./config.log:#define ABSOLUTE_STDINT_H "///usr/include/stdint.h" ./config.h:#define ABSOLUTE_STDINT_H "///usr/include/stdint.h" Thanks Bob
