configure options to binutils

[DJ Delorie]

> If I understand your explanation correctly, failing to use a
> with-sysroot option will produce an errorneous cross-compiler, but
> without any warning or error generated.  Is that correct?

If you omit the option, you simply get a linker that does not support
the auto-magic fixing of linker scripts within the sysroot.

> Does that make sense?  Is that the way I should be doing it?

Ideally, the sys-root should be exactly what you would find in the
*root* of a native build (except they're target files), at least, all
those files that you'd need when developing new programs.  For
example, you'd put your headers there, libraries, pkg-config files (if
any), etc.

So, if your sysroot is in ${SYSROOT}, I'd expect to find things like
${SYSROOT}/usr/include, ${SYSROOT}/usr/lib/libc.a, etc.