Artistic
Jamey Sharp
jamey at gabe.freedesktop.org
Mon Oct 31 15:09:08 PST 2005
Update of /cvs/xtest/xtest
In directory gabe:/tmp/cvs-serv27930
Added Files:
Artistic CHANGES Licence README.FIRST RELEASE configure
Log Message:
Importing TET 3.3h (unsupported) sources from http://tetworks.opengroup.org/tet/tet3.3h-unsup.src.tgz.
Omitted the contrib directory: we don't care, and the license situation wasn't entirely clear.
--- NEW FILE: configure ---
:
# SCCS: @(#)configure 1.9 (99/04/21)
#
# UniSoft Ltd., London, England
#
# Copyright (c) 1998 The Open Group
# All rights reserved.
#
# No part of this source code may be reproduced, stored in a retrieval
# system, or transmitted, in any form or by any means, electronic,
# mechanical, photocopying, recording or otherwise, except as stated in
# the end-user licence agreement, without the prior permission of the
# copyright owners.
# A copy of the end-user licence agreement is contained in the file
# Licence which accompanies this distribution.
#
# Motif, OSF/1, UNIX and the "X" device are registered trademarks and
# IT DialTone and The Open Group are trademarks of The Open Group in
# the US and other countries.
#
# X/Open is a trademark of X/Open Company Limited in the UK and other
# countries.
#
# ************************************************************************
#
# SCCS: @(#)configure 1.9 99/04/21 TETware release 3.3
# NAME: configure
# PRODUCT: TETware
# AUTHOR: Andrew Josey, The Open Group
# DATE CREATED: September 1997
#
# DESCRIPTION:
# This simple script will auto configure the known operating
# systems which have defines.mk files included in the src/defines
# directory.
#
# MODIFICATIONS:
# Andrew Dingwall, UniSoft Ltd., September 1998
# integrated into the TETware distribution
#
# Andrew Dingwall, UniSoft Ltd., November 1998
# added support for FreeBSD
#
# Andrew Dingwall, UniSoft Ltd., March 1999
# integrated some enhancements received from Andrew Josey -
# added support for DYNIX/ptx, Solaris 2.7, BSDI
#
# Andrew Josey, March 2000
# Add in Solaris 8 support.
# ************************************************************************
# functions
badusage()
{
echo "Usage: $0 -t transport" 1>&2
echo "To fix: specify \"-t xti\", \"-t inet\", or \"-t lite\"" 1>&2
exit 2
}
unknown_os()
{
echo "$0: Unable to determine the OS type."
echo "Please configure manually, refer to TETware Installation Guide."
echo "Upon successful configuration please send the output of"
echo "src/helpers/GuessOS and the corresponding makefile for your platform"
echo "(edited from src/defines/template.mk) to tet_support at opengroup.org."
exit 1
}
# parse the command line
args=`getopt t: $*`
if test $? -ne 0
then
badusage
else
set -- $args
fi
tplib=
while test $# -gt 0
do
case "$1" in
-t)
tplib="$2"
shift
;;
--)
shift
break
;;
-*)
badusage
;;
esac
shift
done
case "$tplib" in
inet|xti|lite)
;;
*)
badusage
;;
esac
# change to the source directory
cd src
if test $? -ne 0
then
echo "$0: Unable to find src directory, aborting"
exit 1
fi
# determine the OS type
case `uname -s` in
Windows_NT|Windows_95|DOS)
os=win32
if test "$tplib" = xti
then
echo "$0: Win32 systems do not support XTI networking" 1>&2
exit 1
fi
;;
*DYNIX/ptx*)
os=dynix
;;
*)
os=`sh ./helpers/GuessOS`
;;
esac
# decide whether we should link or copy the defines.mk file
case $os:$tplib in
win32:*)
cpln=cp
;;
*:inet)
cpln="ln -s"
;;
*)
cpln=cp
;;
esac
# determine which defines.mk file to use
fname=
case "$os" in
win32)
fname=msc+mks.mk
;;
dynix)
fname=dynix.mk
;;
*-unixware2*|*-unixware7)
fname=svr42mp.mk
;;
*-unixware1*)
fname=svr4.mk
;;
*-ibm-aix4.[12])
fname=aix41.mk
;;
*-ibm-aix4.3)
fname=aix43.mk
;;
*-ibm-aix3*)
fname=aix32.mk
;;
*-hi-hiux*)
fname=hiux9.mk
;;
*-hp-hpux10*)
fname=hpux10.mk
;;
*-hp-hpux*)
fname=hpux9.mk
;;
*-linux*)
fname=linux.mk
;;
*-dec-osf)
fname=osf1.mk
;;
*-dec-osf4)
fname=decux4.mk
;;
*-sun-solaris2*)
case `uname -r` in
5.[0-5]*)
fname=sunos5.mk
;;
5.[67]*)
fname=sunos56.mk
;;
*)
unknown_os
;;
esac
;;
*-sun-solaris8)
fname=solaris7.mk
cpln=cp
echo "$0: Solaris 8 detected. (using solaris7.mk)"
echo "The default configuration assumes 32-bit, with POSIX Threads,"
echo "Sun Workshop C compiler and no C++ compiler."
echo "Edit the defines.mk file if you need to enable 64-bit mode,"
echo "or change other configuration as per the comments."
;;
*-sun-solaris7)
fname=solaris7.mk
cpln=cp
echo "$0: Solaris 7 detected."
echo "The default configuration assumes 32-bit, with POSIX Threads,"
echo "Sun Workshop C compiler and no C++ compiler."
echo "Edit the defines.mk file if you need to enable 64-bit mode,"
echo "or change other configuration as per the comments."
;;
*-sun-sunos4*)
fname=sunos41.mk
;;
CRAY*)
fname=cray.mk
;;
*-sgi-irix*)
fname=irix.mk
;;
*-freebsd)
fname=freebsd.mk
;;
*-bsdi)
fname=bsdi.mk
;;
# these two had to be left out of the distribution for now
# *-qnx*)
# fname=qnx4.mk
# ;;
# MPE/iX-*)
# fname=mpeix.mk
# ;;
*)
unknown_os
;;
esac
# locate the chosen defines.mk file
if test ! -d defines
then
echo "$0: no defines directory - aborting" 1>&2
exit 1
fi
mkfile=`find defines -name ${fname:?} -print | head -1`
if test -z "$mkfile"
then
echo "$0: can't find $fname in the defines directory" 1>&2
exit 1
fi
# link/copy the chosen defines.mk file in place
echo "$0: using $mkfile"
rm -f defines.mk
eval ${cpln:?} ${mkfile:?} defines.mk
# configure TETware to use the chosen network transport
sh tetconfig -t $tplib
echo "OS=$os Configured"
# emit informational messages if we are not building Distributed TETware
# to use sockets
if test "$tplib" != inet
then
chmod u+w defines.mk
echo
echo "$0: the selected defines.mk file has been designed to build"
echo "Distributed TETware to use the socket network interface."
echo "If you are building a different version of TETware you may need"
echo "to edit the defines.mk file before building TETware."
fi
if test "$tplib" = lite
then
echo "For example: if network libraries have been specified in the"
echo "SYSLIBS assignment, you don't need these when building TETware-Lite."
fi
if test "$tplib" = xti
then
echo "For example: you will need to add something to DTET_CDEFS to specify"
echo "which transport provider(s) you want to use (-DTCPTPI and/or -DOSITPI),"
echo "and you will probably want to specify -DSVID3_POLL as well."
echo "Also, you may need to specify different network libraries using"
echo "the SYSLIBS variable."
echo "Refer to the TETware Installation Guide for details."
fi
# what to do next
echo
echo "To build TETware:"
echo " cd src; make; make install"
--- NEW FILE: README.FIRST ---
SCCS: @(#)README.FIRST 1.3 99/09/07 TET release 3.3
TET3 is the latest version of the Test Environment Toolkit.
This is an UNSUPPORTED source release.
See http://tetworks.opengroup.org for more information
For quick installation instructions see below.
For full documentation refer to the TETware 3.3 documentation
available on http://tetworks.opengroup.org/docs.html
Please note that TET3.3 does not include support
for Microsoft Windows NT, Windows 95 or Java - that support
is only included in the supported TETware releases.
Quick Start for Installation.
-----------------------------
Typical installation is as follows:
Install a .profile for the test suite user
Example:
TET_ROOT=/home/tet
PATH=$PATH:$TET_ROOT/bin
export TET_ROOT PATH
To configure TET3
cd $TET_ROOT
sh configure -t lite # for TETware lite
cd src
make install
(the final command below is not necessary)
make compat # for backwards compatibility for include directories
If the build fails check the makefiles in src/defines
Note: some Make utilities may have trouble with the include directive,
this is a known problem on BSDI systems. In this case use GNU Make
(gmake). Version 3.75 and higher is known to work.
New features in this release
----------------------------
The following features appear for the first time in this release of TETware:
+ Support is provided to enable shared versions of the C API libraries to
be built. The shared library schemes that are supported on UNIX systems
are described in the chapter entitled ``Support for shared API
libraries'' in the TETware Installation Guide for UNIX Operating Systems.
Information regarding the use of shared API libraries is presented in the
chapter entitled ``Using shared API libraries'' in the TETware
Programmers Guide.
+ A document has been added to the TETware document set; its title is
TETware Knowledge Base. It contains information extracted from replies
to requests that have been handled by the TETware support service. An
HTML version of this document is included in the distribution in addition
to the usual PostScript version.
+ A shell script exec tool has been added to the distribution which enables
user interaction with test cases when Distributed TETware is used. The
name of this tool is tet_start and it is described in the chapter
entitled ``Interacting with test cases in Distributed TETware'' in the
TETware User Guide.
+ It is now possible to specify tccd's well-known port number in the
systems file when Distributed TETware is built to use the socket network
interface. Thus it is possible to have tccd listening on different port
numbers on different systems, or to have several instances of tccd
running with different options on a particular system.
+ Support for multiple network interfaces has been added when Distributed
TETware is built to use the socket interface. This support is provided
through the TET_LOCALHOST distributed configuration variable.
Note: The circumstances under which you might need to specify
TET_LOCALHOST are rare when Distributed TETware is built to use the
socket interface. Do not specify this variable unless you really
need it.
+ A keyword %include has been added to the scenario language. This keyword
can be used in a scenario file in much the same way as #include is used
in a C program.
Note that the %include keyword provides different functionality from that
provided by the :include: scenario directive.
+ A configuration variable expansion mechanism has been added to tcc. This
feature is described in the section entitled ``Configuration variable
expansion'' in the TETware Programmers Guide.
+ It is now possible to specify a number range with the :remote: and
:distributed: scenario directives.
+ The maximum number of test cases that tcc can process in parallel has
been increased from 26 to 676.
+ New makefile variables have been introduced to provide a finer degree of
control over the specification of compiler options when the Thread-safe
APIs are built. The names of these variables are TET_THR_CDEFS and
DTET_THR_CDEFS, and they are described in the section entitled ``Support
for Threads'' in the TETware Installation Guide for UNIX Operating
Systems.
+ A command-line option has been added to tcc. When tcc is invoked with
the -V option, it prints out version information and exits.
+ A shell script called configure has been added to the distribution in the
tet-root directory. On platforms for which a suitable defines.mk file is
provided in the distribution this script automates the tasks that must be
performed before TETware can be built.
+ A shell script called sigtool has been added to the distribution in the
tet-root/src/helpers directory. This script is useful when preparing to
build TETware on a platform for which no defines.mk file is provided in
the distribution. The function of this script is to generate values for
makefile variables that must be specified for use when the Shell APIs are
built.
+ The header files inc/tet3/tet_api.h and inc/tet3/tet_jrnl.h are now
protected against multiple inclusion.
+ The Korn Shell API has been updated to work with ksh93.
+ A number of problems reported after the previous TETware release have
been fixed. All the source code patches issued since the last TETware
release have been incorporated into this release.
+ The documentation has been revised and updated.
===========================================================================
Problems fixed since the last release
The following problems have been fixed since the last TETware release:
+ When a test purpose failed to register a result in Distributed TETware,
the result generated by the API was UNRESOLVED instead of NORESULT.
+ When the underlying call to execve() failed in a call to tet_spawn() on a
UNIX system, the error condition was not returned to the process that
called tet_spawn().
+ When remote (non-distributed) test cases were processed on more than one
system, the test cases on the second and subsequent systems did not print
TCM Start, IC Start and IC End messages to the journal, and a call to
tet_result() failed with an ER_DONE error.
+ When a ^scenario-name appeared within the scope of a :distributed:
scenario directive, test cases in the scenario referenced by scenario-
name were unable to synchronise with each other.
+ Under certain circumstances it was possible for tcc to terminate with a
memory fault when removing the temporary directory after processing a
test case in execute mode.
+ When the TET_RUN environment variable was specified, tcc attempted to
create a file with a garbage name on some platforms.
+ When tcc processed a test case in execute mode with TET_EXEC_IN_PLACE set
to False, the test case was copied to a location immediately below the
temporary directory and executed from there rather than to a location
below the temporary directory which included the path name of the test
case relative to the test suite root directory. Thus it was not possible
for a test case to use the tet_pname variable in the C API to determine
its full path name relative to the test suite root directory.
+ The thread cleanup code in the Thread-safe API assumed that a thread ID
would not be re-used by the implementation immediately after the
corresponding thread had been joined. This caused problems on threads
implementations where this assumption is not true.
+ If none of the test cases within the scope of a :timed_loop: directive
can be built, the loop is effectively empty during execute mode. Under
these circumstances, tcc -be would thrash when in execute mode (possibly
generating huge volumes of journal output).
+ There was a name space clash when building the Thread-safe APIs on some
platforms which support both UI threads and POSIX threads.
+ If a locking failure prevented tcc -be from building a test case, tcc
still attempted to execute the test case that could not be built.
+ There were a few references in the code to the non-standard interfaces
sys_errlist and sys_nerr. The functions that referred to these symbols
have been re-written to make calls to strerror() instead.
+ Descriptions of compiler options used when building Distributed TETware
to use XTI were missing from the TETware Installation Guide for UNIX
Operating Systems.
+ In Distributed TETware, if a configuration variable exchange between the
local system and a remote system failed because the related configuration
file was missing on the remote system, the error message printed by tcc
was not particularly useful. The error message now states that the
remote configuration file could not be opened.
+ A feature of the Linux implementation of getopt() caused tcc to terminate
with a memory fault when tcc was invoked in rerun or resume mode. The
code that calls getopt() has been changed to work around this feature.
+ The -I option was missing in tcc's usage message.
Other problems fixed:
Problem:
When TET_EXEC_IN_PLACE=false, tcc/tccd copies the contents of the test
case execution directory to a location below the temporary directory.
During this processing the code attempts to detect a recursive copy.
This code incorrectly reports a recursive copy when the source directory
name is an initial substring of the destination directory name.
Fixed.
Files changed:
src/tet3/dtet2lib/fcopy.c 1.14
------------------------------------------------------------------------
Problem:
On UNIX systems, tet_eaccess() doesn't check group access permissions
w.r.t. the supplementary groups list.
Fixed.
Files changed:
src/tet3/dtet2lib/eaccess.c 1.12
src/tet3/dtet2lib/shared.mk 1.14
------------------------------------------------------------------------
Problem:
tccd dies on RedHat Linux while performing a configuration variable
exchange with tcc.
Analysis:
When tcc sends the result code file to tccd, the file gets closed twice
in tccd.
It seems that the glibc version of fclose(fp) frees the area at *fp.
This causes problems with the malloc subsystem when fclose() is called a
second time.
Fixed.
Files changed:
src/tet3/servlib/fio.c 1.7
------------------------------------------------------------------------
Problem:
If a test case changes the system time, this can sometimes confuse the
timeout mechanism in tcc's execution engine.
When this happens, tcc fails with an ASSERT error.
Fix:
Instead of checking the delay with ASSERT(), just change it so that it
is within the expected range.
Files changed:
src/tet3/tcc/scenario.c 1.8
------------------------------------------------------------------------
Enhancement:
Added user-contributed defines.mk files for DYNIX/ptx, Solaris 2.7, BSDI.
Enhanced configure and GuessOS to recognise these systems and choose the
appropriate defines.mk file.
Originally these files were written by their contributors for use with
the TETware 3.2 makefile scheme.
The makefile scheme changed between release 3.2 and release 3.3.
The contributed files have been modified for use with the 3.3 makefile
scheme but haven't been tested yet.
Files changed:
configure 1.9
src/helpers/GuessOS 1.3
New files:
src/defines/UNTESTED/bsdi.mk 1.1
src/defines/UNTESTED/dynix.mk 1.1
src/defines/UNTESTED/solaris7.mk 1.1
Problem:
There is no makefile target to remove the compatibility links that are
installed below {inc|lib}/{dtet2|posix_c} by 'make compat'.
Fix:
Added new target: compat_clean
The following commands can now be used to remove the compatibility links
that are installed by 'make compat':
cd $TET_ROOT/src
make compat_clean
Note:
As with make compat, make compat_clean is not supported on Win32 systems.
Files changed:
src/makefile 1.7
------------------------------------------------------------------------
Problem:
'tcc -i results-dir' can overwrite an existing journal file in
results-dir.
Fixed.
Files changed:
src/tet3/tcc/journal.c 1.12
------------------------------------------------------------------------
Problem:
tcm/ictp.c needs <string.h> when building TETware-Lite.
Fixed.
Files changed:
src/tet3/tcm/ictp.c 1.22
------------------------------------------------------------------------
Problem:
In TETware-Lite, expanded configuration variables are not visible to
test cases.
The Lite version of tcc passes the master configs to a test case.
Since configuration variable expansion is performed on the per-system
configurations, the test case only sees the unexpanded variables.
Fix:
Write the per-system configurations for the local system to the
TET_CONFIG file(s) instead of the master configurations.
Files changed:
src/tet3/tcc/config.c 1.12
------------------------------------------------------------------------
Problem:
Korn Shell API fails with EBADF error when used with ksh 93.
This is due to a bug in ksh 93.
When a numbered file descriptor is closed in a subshell (i.e., a
sequence of commands enclosed in parentheses) this has the effect of
closing the file descriptor in the parent shell as well.
Previous versions of ksh did not contain this bug.
The TCM main loop reads IC numbers from fd 3.
Each test purpose defined in the IC list is executed in a subshell.
If the test purpose also manipulates fd 3 (as does the SHELL-API demo),
it upsets the execution of the main loop when ksh93 is used.
Workaround:
The main IC loop has been recoded to eliminate the use of numbered file
descriptors in the parent shell.
Files changed:
src/ksh/api/tcm.ksh 1.6
------------------------------------------------------------------------
Enhancement:
Added support for FreeBSD.
Note:
This enhancement based on information kindly supplied by someone at
freebsd.org.
It has not been tested by the TETware development team at this time.
Files changed:
configure 1.8
src/defines/UNTESTED/freebsd.mk 1.1
src/tet3/inc/tetdir.h 1.3
src/tet3/tcclib/lsdir.c 1.3
--- NEW FILE: Artistic ---
The "Artistic License"
Preamble
The intent of this document is to state the conditions under which a
Package may be copied, such that the Copyright Holder maintains some
semblance of artistic control over the development of the package,
while giving the users of the package the right to use and distribute
the Package in a more-or-less customary fashion, plus the right to
make reasonable modifications.
Definitions:
* "Package" refers to the collection of files distributed by the
Copyright Holder, and derivatives of that collection of files
created through textual modification.
* "Standard Version" refers to such a Package if it has not been
modified, or has been modified in accordance with the wishes of
the Copyright Holder.
* "Copyright Holder" is whoever is named in the copyright or
copyrights for the package.
* "You" is you, if you're thinking about copying or distributing
this Package.
* "Reasonable copying fee" is whatever you can justify on the
basis of media cost, duplication charges, time of people
involved, and so on. (You will not be required to justify it to
the Copyright Holder, but only to the computing community at
large as a market that must bear the fee.)
* "Freely Available" means that no fee is charged for the item
itself, though there may be fees involved in handling the item.
It also means that recipients of the item may redistribute it
under the same conditions they received it.
1. You may make and give away verbatim copies of the source form of
the Standard Version of this Package without restriction, provided
that you duplicate all of the original copyright notices and
associated disclaimers.
2. You may apply bug fixes, portability fixes and other modifications
derived from the Public Domain or from the Copyright Holder. A
Package modified in such a way shall still be considered the Standard
Version.
3. You may otherwise modify your copy of this Package in any way,
provided that you insert a prominent notice in each changed file
stating how and when you changed that file, and provided that you do
at least ONE of the following:
a) place your modifications in the Public Domain or
otherwise make them Freely Available, such as by posting
said modifications to Usenet or an equivalent medium, or
placing the modifications on a major archive site such as
ftp.uu.net, or by allowing the Copyright Holder to include
your modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or
organization.
c) rename any non-standard executables so the names do not
conflict with standard executables, which must also be
provided, and provide a separate manual page for each
non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright
Holder.
4. You may distribute the programs of this Package in object code or
executable form, provided that you do at least ONE of the following:
a) distribute a Standard Version of the executables and
library files, together with instructions (in the manual
page or equivalent) on where to get the Standard Version.
b) accompany the distribution with the machine-readable
source of the Package with your modifications.
c) accompany any non-standard executables with their
corresponding Standard Version executables, giving the
non-standard executables non-standard names, and clearly
documenting the differences in manual pages (or
equivalent), together with instructions on where to get the
Standard Version.
d) make other distribution arrangements with the Copyright
Holder.
5. You may charge a reasonable copying fee for any distribution of
this Package. You may charge any fee you choose for support of this
Package. You may not charge a fee for this Package itself. However,
you may distribute this Package in aggregate with other (possibly
commercial) programs as part of a larger (possibly commercial)
software distribution provided that you do not advertise this Package
as a product of your own.
6. The scripts and library files supplied as input to or produced as
output from the programs of this Package do not automatically fall
under the copyright of this Package, but belong to whomever generated
them, and may be sold commercially, and may be aggregated with this
Package.
7. C or perl subroutines supplied by you and linked into this Package
shall not be considered part of this Package.
8. The name of the Copyright Holder may not be used to endorse or
promote products derived from this software without specific prior
written permission.
9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The End
--- NEW FILE: Licence ---
SCCS: @(#)Licence 1.5 (99/09/07) TET Release 3.3
+++++++++++++TET END USER LICENCE+++++++++++
BY RETRIEVING THIS DISTRIBUTION OF TET, YOU ARE CONSENTING TO BE BOUND BY
THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT,
DO NOT INSTALL THE PRODUCT, AND DESTROY YOUR COPY.
TET RELEASE 3.3 END USER LICENCE
_________________________________
Copyright (c) 1996, 1997, 1998, 1999, 2000 X/Open Company Ltd.
All rights reserved.
This program is free software; you can redistribute it and/or modify
it under the terms of the "Artistic License" which comes with this
Kit.
X/OPEN DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL X/OPEN BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
You should have received a copy of the Artistic License with this
Kit, in the file named "Artistic". If not, we'll be glad to provide one.
Portions of this work contain code derived from other versions
of the Test Environment Toolkit, which contain the following
copyrights:
Copyright 1990,1992 Open Software Foundation
Copyright 1990,1992 Unix International
Copyright 1990,1992 X/Open Company Ltd.
Copyright 1991 Hewlett-Packard Co.
Copyright 1993 Information-Technology Promotion Agency, Japan
Copyright 1993 Sunsoft, Inc.
Copyright 1993 UNIX System Laboratories, Inc., a subsidiary of Novell Inc.
Copyright 1994,1995 UniSoft Ltd.
The unmodified source code of those works is freely available from
ftp.xopen.org. The modified code contained in this work
restricts the usage of that code as per this licence.
The contrib distribution is now bundled within the "contrib" directory.
This is subject to the individual copyrights contained within
those files.
--- NEW FILE: RELEASE ---
TET Release 3.3h
--- NEW FILE: CHANGES ---
Changes
3.3h Fix for TET_SAVE_FILES
When TET_SAVE_FILES is set in the execute mode configuration
and one of the directories visited during tcc's Saved Files
processing is empty, tcc prints an error message which says that
the Saved Files operation failed when in fact it was successful.
/src/tet3/tcclib/lsdir.c
Updated perl API, for perl5 and adjustments for signal handling
/src/perl/template.pl
/src/perl/api.pl
Update make compat target
/src/makefile
If a test case makes use of SIGPIPE, this can conflict with use of
SIGPIPE in the API. This problem affects Distributed TET on
Solaris systems, and other systems where the default is for
signal() to have SYSV behaviour.
/src/tet3/inetlib/rdwr.c
3.3g Fix for linker problem when tet_invoketp() etc. are in a library
/src/tet3/tcm/shared.mk
/src/tet3/tcm/makefile
/src/tet3/tcmshlib/makefile
/src/tet3/tcmthr/makefile
3.3f Fix to src/tet3/tcm/tcmchild.c for latest version of g++
also add support for Solaris 8
3.3e Fix to src/tet3/tcm/tcm.c for latest version of g++
also inclusion of bundled contrib distribution
3.3d Additional APIs tet_pthread_join, and tet_pthread_detach added
3.3c minor fix to the perl api
3.3b update list handling in function ttadd() in file
src/tet3/apithr/thr_create.c
More information about the xorg-test-commit
mailing list