Red Hat Bugzilla – Bug 484892
sdiff does not recognize -E option
Last modified: 2013-02-22 08:06:15 EST
Description of problem:
The help message claims that "-E" option is recognized, but the utility does not know it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# sdiff --help | grep -- "-E"
-E --ignore-tab-expansion Ignore changes due to tab expansion.
# sdiff -E
sdiff: invalid option -- E
sdiff: Try `sdiff --help' for more information.
# echo $?
unrecognized option in help message
all options in help message are recognized
# ./guess-options.sh -b /usr/bin/sdiff
==== binary analysis -- enabled
==== The program recognizes 14 short options:
==== The program recognizes 18 long options:
==== The program recognizes 14 equivalent options:
==== -B --ignore-blank-lines
==== -H --speed-large-files
==== -I --ignore-matching-lines
==== -W --ignore-all-space
==== -a --text
==== -b --ignore-space-change
==== -d --minimal
==== -i --ignore-case
==== -l --left-column
==== -o --output
==== -s --suppress-common-lines
==== -t --expand-tabs
==== -v --version
==== -w --width
==== The fake library issued following warnings:
==== -E is not processed by getopt_long()
# rpm -q diffutils
Created attachment 331849 [details]
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The -E option for the sdiff command was not accepted because of an accidental omission in the list of accepted options. This has now been fixed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.