This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] fastjar documentation


Joseph S. Myers writes:
> On Tue, 27 Aug 2002, Matthias Klose wrote:
> 
> > hmm, I've been told, that the fastjar diretory should be self
> > contained, so the fastjar docs can be used upstream as well. Therfore
> > the duplicated macros. same reason for including the two texi files.
> 
> Is fastjar actually being maintained upstream?  If so, it might be more
> appropriate to include a fastjar version number (0.92-gcc is what jar
> --version says at present) in the manual, and not a GCC version number at
> all.  If not, questions of what should be different between fastjar
> upstream and GCC can be resolved when fastjar upstream is maintained - but
> I think that the GCC version should not include duplicates of the gpl.texi
> and fdl.texi files in any case, even though upstream may include its own
> copies.
> 
> That this patch got the GCC version number wrong (for mainline) should be 
> reason enough to show that the number should not be duplicated here.

Is there a recommended way to include the version number?

> > How? using the automake generated Makefile ...
> > 
> > I need to add an -I option to MAKEINFO, but MAKEINFO and MAKEINFO are
> > overridden from the toplevel make.
> 
> AM_MAKEINFOFLAGS, according to the Automake manual.

the automake manual doesn't say anything about AM_MAKEINFOFLAGS, at
least the 1.4 version. Assigning a value to it simply puts it into
Makefile.in, but nothing more.


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