[Top][All Lists]

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

DejaGnu 1.6.3 release candidate 4

From: Jacob Bachmeyer
Subject: DejaGnu 1.6.3 release candidate 4
Date: Wed, 28 Apr 2021 23:07:10 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090807 MultiZilla/ SeaMonkey/1.1.17 Mnenhy/

Release candidate 4 for DejaGnu 1.6.3 has been uploaded to
at <URL:>.

Release candidate 4 continues efforts to address issues reported by
Rainer Orth on Solaris systems:

PR47382 should be (mostly) resolved in this release candidate, as additional non-portable constructs have been corrected in the dejagnu(1) launcher.

The previous experimental code to patch the #! line in the installed copy of config.guess has been withdrawn and the main DejaGnu framework now uses the CONFIG_SHELL or SHELL environment variables to choose a shell for running config.guess if needed. If neither variable is set in the environment, the original code path is used.

Release candidate 4 also now builds the release tarball in the ancient and universal v7 format and ensures that all files in distribution tarballs are recorded as being owned by root to prevent possible surprises when unpacking the tarball.

Known Bugs

Two bugs were reported after the 1.6.3 code freeze and will be present
in the 1.6.3 release; both are expected to be fixed in 1.6.4:
   - PR44462
      - get_multilibs blindly assumes that the target compiler is GCC
   - PR44602
      - loading files fails if the full name contains spaces

One bug was reported in release candidate 1 and will be partially fixed
in 1.6.3, with more extensive work planned for 1.6.4:
   - PR47385
      - framework code can incorrectly accept directories as executable

While PR47382 is expected to be resolved before the 1.6.3 release, a related issue will remain and is expected to be fixed in 1.6.4: the build/host/target triplets given to configure are not propagated to site.exp. This is ultimately a limitation in Automake, for which 1.6.4 is expected to carry a workaround, with efforts made to upstream a solution to add this information to site.exp files by default. Note that GCC (and probably others) will not be affected by the future Automake change, as they currently override Automake's site.exp rule.

Other known bugs include the incorrect handling of libdirs and
thread-safety issues with the C unit testing support in dejagnu.h.

Future Directions

There are no changes to the future directions previously announced with
earlier 1.6.3 release candidates at this time.

-- Jacob

reply via email to

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