From bcf28ce86fe458a324309e16608eb18639b16597 Mon Sep 17 00:00:00 2001 From: Martijn Dekker Date: Sat, 23 Mar 2024 21:43:53 +0000 Subject: [PATCH] README.md: update --- README.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 9118050ff65d..809c35731554 100644 --- a/README.md +++ b/README.md @@ -80,12 +80,9 @@ outputs the name of this subdirectory. Dynamically linked binaries, if supported for your system, are stored in `dyn/bin` and `dyn/lib` subdirectories of your architecture directory. -To enter a shell environment that automatically adds these to `$PATH` -and to your systems library search path (`LD_LIBRARY_PATH` or similar), -so that you can test the build before installing, enter: -```sh -bin/package use -``` +If built, they are built in addition to the statically linked versions. +Export `AST_NO_DYLIB` to deactivate building dyanmically linked versions. + If you have trouble or want to tune the binaries, you may pass additional compiler and linker flags. It is usually best to export these as environment variables *before* running `bin/package` as they could change the name of @@ -149,6 +146,13 @@ available, is installed in `share/man`. Destination directories with whitespace or shell pattern characters in their pathnames are not yet supported. +If a dynamically linked version of ksh and associated commands has been +built, then the `install` subcommand will prefer that: commands, dynamic +libraries and associated header files will be installed then. To install the +statically linked version instead (and skip the header files), either delete +the `dyn` subdirectory, or export `AST_NO_DYLIB=y` before building to prevent +it from being created in the first place. + ## What is ksh93? The following is the official AT&T description from 1993 that came with the