[Bug other/704] --help and --version
egallager at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Sat Feb 23 16:31:00 GMT 2019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=704
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #21 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #20)
> (In reply to Eric Gallager from comment #19)
> > (In reply to joseph@codesourcery.com from comment #18)
> > > Whether this is fixed may be determined by running all of the programs
> > > installed in $exec_prefix/bin by current mainline with the --help and
> > > --version options (and confirming the GCC version number is properly shown
> > > in the --version output).
> >
> > looks like gcc-nm and gcc-ranlib still fail with --help:
>
> That's not a fault with the GCC wrappers, it's because the "upstream"
> cctools nm and ranlib don't respond to "--help" (or --version). I have
> amended versions of them that handle --help and --version (available on
> github***) that work:
>
> $ ./gcc/gcc-ar --help
> usage: ar -d [-TLsv] archive file ...
> ar -m [-TLsv] archive file ...
> <snip>
>
> $ ./gcc/gcc-ar --version
> xtools-1.1.0 ar
>
> - the point is that this is not a problem with the GCC wrappers, the
> intention of them is to pass the --help and --version onto the underlying
> commands.
>
> From the point of view of Darwin, I'd say this could be closed, of course it
> might not be completely clean for other platforms.
>
> *** Note: the versions published on github are quite old - on the TODO to
> provide some updates.
OK, closing then.
More information about the Gcc-bugs
mailing list