On Mon, 10 Jun 2013 13:27:23 +0200 Lionel Cons wrote: > On 17 April 2013 15:02, Cedric Blancher <[email protected]> > wrote: > > On 2 April 2013 17:58, Glenn Fowler <[email protected]> wrote: > >> > >> we have no reason to believe ast would have trouble building and running > >> on arm64 > >> a while back we built on arm32, directly and cross-compiled, with no > >> problems > >> > >> anyone with access to arm64 hw or an emulator can try to build ast-open and > >> report what happens > >> > >> if space is an issue try building with > >> export PACKAGE_OPTIONS=optimize-space > >> this will link ksh with ast .so's instead of .a's > >> and also hard link all libcmd commands to one a.out > > > > Why aren't the libcmd commands always hardlinked to one a.out? Roland > > Mainz did this for Solaris 11 with great effect and good space savings > > and (compared to old Solaris's utilities) a major performance gain.
> Is there a reason why only ast-open ships with the a.out to access the > commands in libcmd directly? yes the ast-ksh package is ksh + its builtins so the expectation is that only ksh and maybe shcomp get installed in bin packages > ast-ksh provide more than that and the expectation is that many things will go into bin _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
