Re: prefer in-tree libiconv over the system libiconv?

[Tom Tromey <tromey@redhat.com>]

Joel> But, on the other hand, for a distributer like AdaCore (and maybe CS),
Joel> it makes it harder to make sure which libiconv gets linked in.
Joel> I suggest we change the logic a bit so that, if the libiconv sources
Joel> are in-tree, then use this libiconv over the system one.  The
Joel> alternative is to have a configure switch that would allow us to
Joel> specify the location of the libiconv install from the in-tree build.

Joel> Thoughts?

I think the relevant scenario is something like the old Cygnus "devo"
tree, where you would have libiconv always present and also use the
single soruce tree on all hosts.  In this situation, would you prefer
to pick up the system iconv on Linux?  Or would you prefer to always
use libiconv and have identical behavior across hosts (at some cost; I
think the native glibc iconv probably handles more charsets).

I guess specifying the libiconv prefix in the build tree might work.
Something like --with-build-libiconv or --with-system-iconv would be
simpler and less error-prone, though.

Anyway, I'm happy to implement whatever approach you want here, just
let me know.

Tom