On 11/07/2016 10:48 AM, Mike Stump wrote:
On Nov 6, 2016, at 11:39 AM, Iain Sandoe <iain_san...@mentor.com> wrote:
This is an initial patch in a series that converts Darwin's configury to detect
ld64 features, rather than the current process of hard-coding them on target
system version.
So, I really do hate to ask, but does this have to be a config option?
Normally, we'd just have configure examine things by itself. For canadian
crosses, there should be enough state present to key off of directly, specially
if they are wired up to work.
I've rather have the thing that doesn't just work without that config flag,
just work. I'd like to think I can figure how how to make it just work, if
given an idea of what doesn't actually work.
Essentially, you do the operation that doesn't work, detect it failed to work,
then the you know it didn't work.
But how is that supposed to work in a cross environment when he can't
directly query the linker's behavior?
In an ideal world we could trivially query the linker's behavior prior
to invocation. But we don't have that kind of infrastructure in place.
ISTM the way to go is to have a configure test to try and DTRT
automatically for native builds and a flag to set for crosses (or
potentially override the configure test).
Jeff
