[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [platform-testers] verification instructions for groff 1.23.0.rc2

From: Dagobert Michelsen
Subject: Re: [platform-testers] verification instructions for groff 1.23.0.rc2
Date: Thu, 16 Feb 2023 07:22:51 +0100

Hi Branden,

Am 15.02.2023 um 19:12 schrieb G. Branden Robinson 
> At 2023-02-07T14:50:38+0100, Dagobert Michelsen wrote:
>>> Am 06.02.2023 um 23:03 schrieb G. Branden Robinson 
>>> <>:
>>> Can you update your $PATH, re-run "make check", and let me know if that
>>> changes your result?
>> This will not work because the shellscripts have an explicit shebang
>>  #!/bin/sh
>> and are called as executables.
> [...]
>> Indeed. I see two solutions:
>> - use a wrapper like „runtest“ which executes the shellscripts with 
>> something like
>>  which avoids the shebang.
>> - use autoconf with the scripts renamed to <script>.in and use @SHELL@
> I feel the latter is too disruptive, in part because we are close to a
> final release and also because Solaris 11 has a POSIX-conformant shell
> and Solaris 10 is supposed to be end-of-lifed in 1 year.
> I have the following change pending to the "INSTALL.extra" file, which
> distribution archive users are directed to read.
> Do you feel this is accurate and adequate, even if not maximally
> convenient for Solaris 10 users?
> diff --git a/INSTALL.extra b/INSTALL.extra
> index e0bcbeb40..60c0f815a 100644
> --- a/INSTALL.extra
> +++ b/INSTALL.extra
> @@ -226,11 +226,23 @@ directory) will have a log file called
> To re-run a test, change to the top of the build directory (if
> necessary) and run the test by name from the shell prompt.
> +[Solaris 10 users _must_ run the test scripts by hand since the /bin/sh
> +and utilities on that system are not conformant to the POSIX standard.]
> +
> For example, to rerun the test mentioned above from a "build" directory
> I created as a subdirectory in the source tree, I would do this.
>   (cd build && ../tmac/tests/
> +[Solaris 10 users will need to put /usr/xpg4/bin or /usr/xpg6/bin in the
> +$PATH and pass the test scripts as arguments to a POSIX-conforming
> +shell.
> +
> +  (cd build && PATH=/usr/xpg4/bin:$PATH /usr/xpg4/bin/sh \
> +   ../tmac/tests/
> +
> +You might wish to write a small shell script to facilitate the process.]
> +
> I can view the test log as follows.
>   cat build/tmac/tests/
> I'm happy to try out my prescription myself if someone can offer me a
> shell account on a Solaris 10 system.  No special privileges are
> necessary to perform and test a build and installation.

This sounds reasonable to me. While I would prefer an automatic solution
I fully understand the ongoing obsolesence of Solaris 10. If you want I
can set up an account on the OpenCSW buildfarm for you. Alternatively
you may already have an account on GCC tetaneutral where I also sponsored
machines for Solaris 10 and 11:

Best regards

  — Dago

"You don't become great by trying to be great, you become great by wanting to 
do something,
and then doing it so hard that you become great in the process." - xkcd #896

Attachment: signature.asc
Description: Message signed with OpenPGP

reply via email to

[Prev in Thread] Current Thread [Next in Thread]