Re: [Lynx-dev] lynx2.9.1 build issues

2024-04-17 Thread Steffen Nurpmeso
Thomas Dickey wrote in : |On Tue, Apr 16, 2024 at 09:26:12PM +0200, Steffen Nurpmeso wrote: |> Thomas Dickey wrote in |> : |>|On Tue, Apr 16, 2024 at 08:43:20AM -0600, Nelson H. F. Beebe wrote: ... |>|> (1) On Solaris systems, configure fails like this: |>|> |>|> checking for

Re: [Lynx-dev] lynx2.9.1 build issues

2024-04-17 Thread Thorsten Glaser
Thomas Dickey dixit: >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

Re: [Lynx-dev] lynx2.9.1 build issues

2024-04-17 Thread Thomas Dickey
On Tue, Apr 16, 2024 at 09:26:12PM +0200, Steffen Nurpmeso wrote: > Thomas Dickey wrote in > : > |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

Re: [Lynx-dev] lynx2.9.1 build issues

2024-04-16 Thread Steffen Nurpmeso
Thomas Dickey wrote in : |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

Re: [Lynx-dev] lynx2.9.1 build issues

2024-04-16 Thread Thomas Dickey
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

[Lynx-dev] lynx2.9.1 build issues

2024-04-16 Thread Nelson H. F. Beebe
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