Re: lynx2.9.1 build issues
Thomas Dickey <[email protected]>
| Newsgroups | gmane.comp.web.lynx.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Apr 16, 2024 at 09:26:12PM +0200, Steffen Nurpmeso wrote: > Thomas Dickey wrote in > <[email protected]>: > |On Tue, Apr 16, 2024 at 08:43:20AM -0600, Nelson H. F. Beebe wrote: > |> At Utah, I ran build attempts of lynx2.9.1 in more than 70 systems in > |> our test farm. Of those, 59 built and validated successfully, and > |> 2.9.1 is now the default version of lynx on all of our physical > |> servers. > |> > |> The remaining failures are traced to just two issues: > |> > |> (1) On Solaris systems, configure fails like this: > |> > |> checking for DESTDIR... ./configure: syntax error at line 1343: `(' > |> unexpected > |> > |> The fix was simple: use a newer shell than /bin/sh: > |> > |> ksh ./configure .... > | > |That's been my recommendation for several years (actually, for tin, > |I provided Urs with a script to alter the configure script, but don't > |recall anyone else commenting on it) - I posted a copy here: > | > | https://lists.gnu.org/archive/html/lynx-dev/2019-02/msg00033.html > | > |Either way, I've been building with Solaris 10 and 11.4 :-) > > Fwiw i use variants of > > # For heaven's sake auto-redirect on SunOS/Solaris > if [ -z "${__DKIM_KEY_CREATE_UP}" ] && [ -d /usr/xpg4 ]; then > if [ "x${SHELL}" = x ] || [ "${SHELL}" = /bin/sh ]; then > echo >&2 'SunOS/Solaris, redirecting through $SHELL=/usr/xpg4/bin/sh' > __DKIM_KEY_CREATE_UP=y PATH=/usr/xpg4/bin:${PATH} SHELL=/usr/xpg4/bin/sh > export __DKIM_KEY_CREATE_UP PATH SHELL > exec /usr/xpg4/bin/sh "${0}" "${@}" > fi > fi I use this (at the moment, only recall that CONFIG_SHELL is needed for the configure script): case .$SHELL in .*/sh) ;; *) SHELL=/bin/sh test -f /usr/xpg4/bin/sh && SHELL=/usr/xpg4/bin/sh ;; esac export SHELL CONFIG_SHELL=$SHELL export CONFIG_SHELL -- Thomas E. Dickey <[email protected]> https://invisible-island.net
signature.asc
(application/pgp-signature, 659 B)
-----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGYgtkt2kxADCLA1WzCr0RyFnvgMFAmYfgd4ACgkQzCr0RyFn vgMeNAwAiZ1a/57HcGCg7xJXVVEgZs6t38e64vgK8CLpC8UAMLSxWKiAw716767m sWgEW3C7RGbDphEgqg0Nt/QMGbVO6DlJIYmuOwm5l+oKTSIpbnx4iZTcJ3NNxeQ/ JJSEfLEpiuCtp27ckTuPgKVoiEXiJR6WNYsJQcXoV+mmty+fv4A6aajYT8YqhJ+Q rErYN59wAH6RLLCa4vKBNkDbDvKpcff1JycCgcpCZzNTRPUQZ9i2MoyPY5ZMFPxC pC9cDsVYUVFX6dSEWHbRZ9/FxdFQ37I+xbSe8IVAoKVxXVvC+RRTbqWGRJxr7u4N DfbX7tG1/LDWYbgnPez/ymL8UFVxDpnkYNcvrJ2LhLc+Srqh71wF9ySy39JcHDlM t5/YVE/qIjHcqFF3zMctR5PLM8PwZRX8420EatP301LLOk+/Z/Ul6k2FvgTw1/Xe O/cexlinBdAwa4I7GJUGmWv7WnpBOPMeZhcLs+WIqtoEoBXf9Ita2hM/VRDaJRyn amA6GUQ2 =pSn9 -----END PGP SIGNATURE-----