Dear Martin Köppe,
Perhaps dependencies was not the correct word.
Running configure scripts often check for the presence of
executables and header files.
SFU 3.5 has the files /bin/iconv and /usr/include/iconv.h.
SUA 6.1 has /bin/iconv, /usr/include/iconv.h, /usr/lib/libintl.so,
and /usr/lib/libintl.so.8.
What I was looking at was replacing /bin/iconv and
/usr/include/iconv.h, with the files from a compile of
libiconv-1.11.tar.gz, and on SUA 6.1 also replacing libintl.so and
libintl.so.8 with the files from a compile of GNU gettext-0.16.
I don't want to cause problems for remaining executables which were
shipped with SFU or SUA.
Sincerely,
Eric Lindblad
http://www.nurmi-labs.blogspot.com
--------------------------------------------
On Thu, 2/2/17, Martin Koeppe <mkoeppe@gmx.de> wrote:
Subject: Re: interix question
To: "Eric Lindblad" <geirfuglaps@yahoo.com>
Cc: "debian-interix list" <debian-interix@lists.debian.org>
Date: Thursday, February 2, 2017, 9:34 PM
Hi
Eric,
sorry, I don't
understand your question.
I could understand
it as how MS compiled the binaries they ship, but
I'm not sure, if you really wanted to know
that.
Regards
Martin
On
Thu, 2 Feb 2017, Eric Lindblad wrote:
> Dear Martin Köppe,
>
> Have you any opinion
on what files from an unmodified SFU Interix
> 3.5 installation would have been compiled
using /bin/iconv and
>
/usr/include/iconv.h as dependencies?
>
> Likewise for an
unmodified SUA Interix 6.0/6.1 installation files
> compiled using /usr/lib//libintl.so.8?
>
> Sincerely,
> Eric Lindblad
> http://www.nurmi-labs.blogspot.com
>