> I have read the thread in full, and I do not see the problem with
> keeping that info in a seperate manual; GCC has so many options
> for various architectures and systems that I think it makes
> technical sense to have a "Invoking GCC" manual.
And what about libstdc++ API docs, which are currently quite
difficult to cross-reference with the libstdc++ manual, and cannot
be included in it? The API docs come from C++ sources and the
manual from docbook sources, so texinfo has nothing to do with it.
For a API reference listing document, it would make more sense to
license the work under the GPL, is that possible?
There is no rule in the GNU project that all types of documentation
must be licensed under the GFDL. Sometimes it makes sense, good
examples are the gccint, gcc and the emacs manual, and sometimes it
might not like for API reference listings.