libopcode endian and subarch inconsistencies?

[Maciej W. Rozycki]

On Sun, 10 Jun 2012, Dr. David Alan Gilbert wrote:

> 2) The 'binary' target
>   The 'binary' target has it's flags set as BFD_ENDIAN_UNKNOWN;
> but there again there is a comment that says it's only for
> use as output not by input; so other than ignoring that
> comment (as I did) - what's the right way to use libopcode
> to disassemble from a byte stream?

 See how `objdump' drives opcodes -- it has -EB/-EL options to select the 
endianness regardless of the target chosen.  It can disassemble from the 
"binary" target just fine.

  Maciej