[Bug bootstrap/10996] Do not create files in the source directory
pinskia@physics.uc.edu
gcc-bugzilla@gcc.gnu.org
Tue May 27 19:45:00 GMT 2003
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10996
pinskia@physics.uc.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2003-05-27 19:31:52
date| |
------- Additional Comments From pinskia@physics.uc.edu 2003-05-27 19:31 -------
Some of these have been semi-fixed on the mainline with the following patch, meaning
that you have to change where parsedir/docobjdir is:
2003-01-10 Geoffrey Keating <geoffk@apple.com>
* Makefile.in (parsedir): New variable.
(docobjdir): New variable.
(c-parse.o, c-parse.c, c-parse.y, gengtype-lex.o, gengtype-yacc.o,
gengtype-lex.c, gengtype-yacc.c): Use parsedir.
(info, cpp.info, gcc.info, gccint.info, gccinstall.info,
cppinternals.info, generated-manpages, gcov.1, cpp.1, gcc.1, gfdl.7,
gpl.7, fsf-funding.7, maintainer-clean, install-info, install-man):
Use docobjdir.
* objc/Make-lang.in (objc/objc-parse.c, objc/objc-parse.y,
objc.maintainer-clean): Use parsedir.
2003-01-30 Loren James Rittle <ljrittle@acm.org>
* Make-lang.in (po-generated): Find the targets in $(parsedir).
Propagate change to all other rules as required.
(java/parse-scan.o): Add explicit dependency on
$(parsedir)/java/parse-scan.c .
Here is the updated ones that need to be fixed still:
gcc/fastjar/fastjar.info
gcc/fastjar/jar.1
gcc/fastjar/grepjar.1
gcc/gcc/f/g77.1
gcc/gcc/java/gcj.1
gcc/gcc/java/gcjh.1
gcc/gcc/java/gij.1
gcc/gcc/java/jcf-dump.1
gcc/gcc/java/jv-convert.1
gcc/gcc/java/jv-scan.1
gcc/gcc/java/parse.c
gcc/gcc/java/parse-scan.c
gcc/gcc/java/rmic.1
gcc/gcc/java/rmiregistry.1
all the ones in gcc/gcc/{f,java} should be easy to fix and even the ones in fastjar are easy
too.
(note since gcc/gcc/cp/parse.{c,h} is no longer generated it does need fixing)
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Gcc-bugs
mailing list