Then, it looks like you simply need a static version of libiconv. Do
you have it? In fact, a static build of ksh won't help you if you don't
have a static libiconv. If you do have it, then where you specify
-liconv in the ksh build, specify /usr/local/lib/libiconv.a instead.
Terrence Doyle
On 2/7/15 9:01 PM, Russell Cannon wrote:
> Further research shows that ONLY libiconv is missing on the target
> servers. All other required libraries are present. Here is an ldd
> listing of the dependencies:
>
> /usr/lib/libc.2 => /usr/lib/libc.2
> /usr/lib/libdld.2 => /usr/lib/libdld.2
> /usr/lib/libc.2 => /usr/lib/libc.2
> /usr/lib/libdld.2 => /usr/lib/libdld.2
> /usr/local/lib/libiconv.sl <http://libiconv.sl> =>
> /usr/local/lib/libiconv.sl <http://libiconv.sl>
> /usr/lib/libc.2 => /usr/lib/libc.2
> /usr/lib/libm.2 => /usr/lib/libm.2
>
> All are present except /usr/local/lib/libiconv.sl <http://libiconv.sl>.
>
> Cheers,
> Russ
>
> On Feb 7, 2015, at 05:47, Russell Cannon <russell.t.can...@gmail.com
> <mailto:russell.t.can...@gmail.com>> wrote:
>
> After resolving our previous build issues, we ran into another
> problem. Some of the servers on which we must install the new
> Kornshell binary are missing some required libraries. The servers
> we control have all the necessary components, but many other servers
> belong to another agency and are outside our control. The process
> for gaining approval for installation of new software requires
> months of political wrangling among inter-agency security
> authorities, and sometimes approvals are denied. What we need to do
> is produce a static build of KSH so that we can provide a single,
> monolithic binary. Since Kornshell is already installed on all the
> servers, we are allowed to upgrade it without additional authorizations.
>
> We have been searching for a way to build a static binary but have
> not been successful. Based on a message in the archives, we tried
> setting SHOPT_DYNAMIC to 0 in the Kornshell makefile, but this had
> no effect on the result. The compiled program was the exact same
> size as previous builds and would still not run on the problem servers.
>
> There is also this statement by Dave Korn from a message posted in
> ast-users on June 28, 2008:
>
> "if you build a dynamic [later corrected to "static"] version of
> ksh93, then you will not be able to load built-ins at run time."
>
> Can someone explain what this means?
>
> These are old, HP PA-RISC servers running HP-UX 11.11. We have been
> entirely successful with the binary on our own servers, but the DOD
> servers belonging to another agency, which are of the same type and
> O/S, cannot run the software. We know at the very least that they
> are missing libiconv.sl <http://libiconv.sl> and may be missing
> other libraries as well. Can anyone be of any assistance with this?
>
> Cheers,
> Russ Cannon, Oracle DBA
> HQ AFLCMC/HIBD USAF
>
>
>
> _______________________________________________
> ast-developers mailing list
> ast-developers@lists.research.att.com
> http://lists.research.att.com/mailman/listinfo/ast-developers
_______________________________________________
ast-developers mailing list
ast-developers@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-developers
