symfile.c:symfile_bfd_open()

[Todd Whitesel <toddpw at windriver dot com>]

While merging up to 4.18 (as a stepping stone to devo), I noticed
something that we're doing locally here which seems generally useful
for cross developing folks.

symfile.c:symfile_bfd_open() opens objects/executables using BFD.

It tells openp() to search the $PATH, which is obviously handy for
native, but seems to make no sense whatsoever for cross development.

Our local patch is to add a second argument to symfile_bfd_open,
"use_source_path", which ends up being set to 1 nearly all of the
time, since with our targets we are always cross developing. In
that case, we have openp() search source_path instead of getenv("PATH").

Does the multi-arch stuff provide a clean test for native vs. cross?
That'd be a better decision-maker than the "use_source_path" argument.

-- 
Todd Whitesel
toddpw @ windriver.com