I was able to build a static version of ast-open on Mac OS X with
"package make debug=1". The resulting executables are not optimized
since they are compiled with the -g option instead of -O.
Run-time built-ins are added with the ksh builtin command. If you
simply type "builtin" you'll get a list of built-in commands, both
intrinsic and run-time. If I'm not mistaken, the commands that begin
with /, i.e. grep, ls, cp, etc., are run-time built-ins. However, these
are present in both my static (debug) and my dynamic versions of ksh.
Terrence Doyle
On 2/7/15 5:47 AM, Russell Cannon 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
