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

java/1021: fastjar files not in gcc_update



>Number:         1021
>Category:       java
>Synopsis:       fastjar files not in gcc_update
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 09 08:16:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        2.97 20001209 (experimental)
>Organization:
none
>Environment:
System: Linux decomino 2.2.17 #1 Mon Sep 4 20:22:16 UTC 2000 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:

Bootstrapping a checked out GCC tree can modify fastjar/Makefile.in,
depending on timestamps.  To avoid this, the appropriate dependencies
should be added to contrib/gcc_update.

>How-To-Repeat:

Check out a GCC CVS tree, run contrib/gcc_update --touch, then
bootstrap and find (depending on exact software versions installed)
that fastjar/Makefile.in has been modified.

>Fix:

Add generated files in fastjar to contrib/gcc_update; or, if they
shouldn't be in the CVS repository, remove them.  (For example, it may
be a mistake that Makefile and install-defs.sh are in the repository,
as both claim or appear to be generated by configure and files
generated by configure shouldn't be checked in.)
>Release-Note:
>Audit-Trail:
>Unformatted:

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