Re: converters/libiconv-1.16

[Greg Troxel <gdt%lexort.com@localhost>]

Martin Husemann <martin%duskware.de@localhost> writes:

> On Fri, Oct 11, 2019 at 11:26:20AM -0400, Greg Troxel wrote:
>> Can you explain how /usr/pkg/include/iconv.h is found?  Regardless of
>> what's in PATH, I don't see how that would be included.  And, there can
>> be arbitrary stuff in /usr/pkg/include, so for robustness build.sh has
>> to by default not look there.
>
> No, it can not explicitly avoid that. This is about the tool build phase,
> which does some autoconfigury - it  absolutely hast to work out of the
> box in any sane posixish environment w/o modifications of the environment.
>
> If gdb autoconfigure is broken and picks up mixed things, it should
> be fixed.

Given that 1) /usr/pkg is not in the default compiler search paths and
2) NetBSD does not have pkg-config by default, I do not understand why
anything in build.sh tools ever looks in /usr/pkg.